Signature Requests

Message signatures versus transaction signatures

For message signatures versus transaction signatures, the goal is not to memorize labels but to build a repeatable decision sequence: confirm the current network and account context, understand what the requested action changes, and then verify the resulting state on-chain. Security is about reducing unnecessary exposure and single points of failure rather than promising absolute protection. Seed phrases and private keys are controlled by the user. Official personnel should never ask for them, and they should not be shared through chat, email, web forms, screenshots or cloud documents. Message signatures versus transaction signatures also connects to other wallet tasks. Network choice affects fees and transaction visibility, contract interaction can affect approvals and asset state, and security habits apply across creation, backup, transfers and Web3 use. This page focuses specifically on signature requests so the guidance can be applied to a real task rather than treated as a generic feature list. The key is to verify network context, understand what the requested action changes, and keep sensitive credentials outside webpages and support conversations.

Read the request before signing

For read the request before signing, the goal is not to memorize labels but to build a repeatable decision sequence: confirm the current network and account context, understand what the requested action changes, and then verify the resulting state on-chain. High-risk situations often use urgency, familiar branding or a routine-looking signing flow. For airdrops, support claims, verification, refunds or recovery promises, independently check the domain, contract address, network and exact request. Unknown links, QR codes, browser extensions and remote-control tools can all increase risk. When something looks wrong, break read the request before signing into four questions: what address or contract is involved, which network is active, what action is being requested, and what result should be visible on-chain. This is usually more reliable than repeating the same click. This page focuses specifically on signature requests so the guidance can be applied to a real task rather than treated as a generic feature list. The key is to verify network context, understand what the requested action changes, and keep sensitive credentials outside webpages and support conversations.

A practical review sequence

1. Confirm the active network and the intended account
2. Verify the address, contract or DApp source
3. Read the exact action, amount and permission scope
4. Verify the public on-chain result after completion

Why unknown signatures are risky

For why unknown signatures are risky, the goal is not to memorize labels but to build a repeatable decision sequence: confirm the current network and account context, understand what the requested action changes, and then verify the resulting state on-chain. On-chain transactions and approvals have real consequences. Verify the address, network and amount before sending; identify whether a prompt is a message signature or a transaction; and check the spender and allowance before approving a token. Revoke permissions you no longer need and treat third-party DApps and contracts as independent risk sources. For an unfamiliar why unknown signatures are risky issue, keep verifiable non-sensitive evidence such as a public address, network name, transaction hash and visible error text. Sensitive credentials are not troubleshooting material and should not be given to support staff. This page focuses specifically on signature requests so the guidance can be applied to a real task rather than treated as a generic feature list. The key is to verify network context, understand what the requested action changes, and keep sensitive credentials outside webpages and support conversations.

What to do with an unusual request

For what to do with an unusual request, the goal is not to memorize labels but to build a repeatable decision sequence: confirm the current network and account context, understand what the requested action changes, and then verify the resulting state on-chain. Security is about reducing unnecessary exposure and single points of failure rather than promising absolute protection. Seed phrases and private keys are controlled by the user. Official personnel should never ask for them, and they should not be shared through chat, email, web forms, screenshots or cloud documents. What to do with an unusual request also connects to other wallet tasks. Network choice affects fees and transaction visibility, contract interaction can affect approvals and asset state, and security habits apply across creation, backup, transfers and Web3 use. This page focuses specifically on signature requests so the guidance can be applied to a real task rather than treated as a generic feature list. The key is to verify network context, understand what the requested action changes, and keep sensitive credentials outside webpages and support conversations.