Signature Requests

On this page

message signatures versus transaction signatures

Message signatures can prove intent or support login flows, while transaction signatures authorize data that may be broadcast on-chain. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For message signatures versus transaction signatures, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.

Do not approve unreadable structured data simply to continue, especially when permit-style approvals or unfamiliar contract instructions are involved. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate message signatures versus transaction signatures workflow requires a seed phrase, private key or verification code to be sent to another person.

understand the context of a signature request

Do not approve unreadable structured data simply to continue, especially when permit-style approvals or unfamiliar contract instructions are involved. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate understand the context of a signature request workflow requires a seed phrase, private key or verification code to be sent to another person.

Legitimate support does not need a signature to “unlock” assets or validate ownership. If the action includes a signature, approval or contract call, inspect the permission scope and possible asset impact separately. Friendly labels are not a substitute for the underlying request. Check the target, asset, amount or allowance, network and final confirmation details before proceeding. This sequence reduces mistakes caused by urgency, phishing or the wrong network.

Verify the network, address and public on-chain information relevant to understand the context of a signature request.
Never send a seed phrase, private key or verification code to anyone.
For DApps or contracts, review each signature and approval scope separately.

identify higher-risk signature patterns

Message signatures can prove intent or support login flows, while transaction signatures authorize data that may be broadcast on-chain. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For identify higher-risk signature patterns, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.

how to reject and exit safely

Message signatures can prove intent or support login flows, while transaction signatures authorize data that may be broadcast on-chain. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For how to reject and exit safely, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.

Do not approve unreadable structured data simply to continue, especially when permit-style approvals or unfamiliar contract instructions are involved. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate how to reject and exit safely workflow requires a seed phrase, private key or verification code to be sent to another person.

Verify the network, address and public on-chain information relevant to how to reject and exit safely.
Never send a seed phrase, private key or verification code to anyone.
For DApps or contracts, review each signature and approval scope separately.