Signature Requests

What a Signature Means

A practical approach to what a signature means

“What a Signature Means” deserves its own check because it can change the object, network, permission or final state involved in Signature Requests. A signature is cryptographic confirmation of a message, structured payload or transaction. The consequences vary by request type: some signatures prove address control, while others can authorize a transaction or permission change, so “sign” should never be treated as a generic login button.

On this page, the broader goal is to distinguish message, structured-data and transaction signatures and require a fresh review for each request. “What a Signature Means” therefore needs to connect the concept to its surrounding steps, the information that can be verified publicly, and the information that must remain under the user’s control. Review the domain, network, destination, amount, contract method and permission scope before signing. If the request is unrelated to the task or is not understandable, reject it and return through a trusted entry point rather than clicking through repeated prompts.

A repeatable sequence makes the process portable across different interfaces because the user can return to addresses, networks, contracts and public records. In Signature Requests, apply this principle together with the checks described under What a Signature Means.

Message Signatures

A practical approach to message signatures

Within a real Signature Requests workflow, “Message Signatures” is a decision point where interface familiarity should not replace independent verification. A signature is cryptographic confirmation of a message, structured payload or transaction. The consequences vary by request type: some signatures prove address control, while others can authorize a transaction or permission change, so “sign” should never be treated as a generic login button.

On this page, the broader goal is to distinguish message, structured-data and transaction signatures and require a fresh review for each request. “Message Signatures” therefore needs to connect the concept to its surrounding steps, the information that can be verified publicly, and the information that must remain under the user’s control. Review the domain, network, destination, amount, contract method and permission scope before signing. If the request is unrelated to the task or is not understandable, reject it and return through a trusted entry point rather than clicking through repeated prompts.

The goal is to separate verifiable evidence from interface wording so familiar buttons do not become a substitute for review. In Signature Requests, apply this principle together with the checks described under Message Signatures.

Confirm the current network, intended target and purpose
Never enter or send a seed phrase, private key or verification code
Verify the result with an independent record after submission

Structured Signatures

A practical approach to structured signatures

“Structured Signatures” deserves its own check because it can change the object, network, permission or final state involved in Signature Requests. A signature is cryptographic confirmation of a message, structured payload or transaction. The consequences vary by request type: some signatures prove address control, while others can authorize a transaction or permission change, so “sign” should never be treated as a generic login button.

On this page, the broader goal is to distinguish message, structured-data and transaction signatures and require a fresh review for each request. “Structured Signatures” therefore needs to connect the concept to its surrounding steps, the information that can be verified publicly, and the information that must remain under the user’s control. Review the domain, network, destination, amount, contract method and permission scope before signing. If the request is unrelated to the task or is not understandable, reject it and return through a trusted entry point rather than clicking through repeated prompts.

If a critical detail cannot be independently confirmed, stopping to gather more information is usually safer than repeatedly submitting the same action. In Signature Requests, apply this principle together with the checks described under Structured Signatures.

Transaction Signatures

A practical approach to transaction signatures

Within a real Signature Requests workflow, “Transaction Signatures” is a decision point where interface familiarity should not replace independent verification. A signature is cryptographic confirmation of a message, structured payload or transaction. The consequences vary by request type: some signatures prove address control, while others can authorize a transaction or permission change, so “sign” should never be treated as a generic login button.

On this page, the broader goal is to distinguish message, structured-data and transaction signatures and require a fresh review for each request. “Transaction Signatures” therefore needs to connect the concept to its surrounding steps, the information that can be verified publicly, and the information that must remain under the user’s control. Review the domain, network, destination, amount, contract method and permission scope before signing. If the request is unrelated to the task or is not understandable, reject it and return through a trusted entry point rather than clicking through repeated prompts.

Confirm the current network, intended target and purpose
Never enter or send a seed phrase, private key or verification code
Verify the result with an independent record after submission

Reject Unknown Requests

A practical approach to reject unknown requests

Within a real Signature Requests workflow, “Reject Unknown Requests” is a decision point where interface familiarity should not replace independent verification. This topic should be understood in the context of how to distinguish message, structured-data and transaction signatures and require a fresh review for each request, with the object, network and evidence source verified before the next action.

On this page, the broader goal is to distinguish message, structured-data and transaction signatures and require a fresh review for each request. “Reject Unknown Requests” therefore needs to connect the concept to its surrounding steps, the information that can be verified publicly, and the information that must remain under the user’s control. Use public, verifiable information first and compare the wallet view with on-chain records. Secret credentials, unexplained signatures and expanded permissions are not suitable areas for trial-and-error clicking.