Core principles
A signature is created with your private key to approve specific data. A normal wallet keeps the private key local instead of sending it to the website. To understand Signature Requests, place the concept inside a real on-chain workflow: where the information comes from, what the user confirms, how the network records the result, and which outcomes cannot normally be reversed by a wallet provider. This makes inconsistencies easier to spot across different apps and networks.
Common risk scenarios
A message signature may not spend gas, but some signed messages can still authorize meaningful actions in a protocol. “No gas” does not mean “no risk.” In practice, start with the intended outcome and then verify the relevant fields. If an address, network, contract or permission connected to Signature Requests cannot be explained, stop rather than accepting the default button. Public blockchain data can often be used as a second source of verification.
A practical way to check
Separate what you can verify publicly from what must remain secret. Network names, public addresses, transaction hashes and contract addresses can be checked against public blockchain data. Seed phrases and private keys should never be disclosed for this purpose.
How to identify and respond
A transaction signature can include a destination, calldata, value and gas. Stop when the contract or request cannot be identified. Security is not a single “perfect protection” switch. It comes from repeatable habits: trusted entry points, independent checks, least-necessary permissions, offline protection of secret credentials, and a willingness to reject abnormal requests.
imtoken staff will not ask for your seed phrase or private key. Review the address, network and request before any transfer, signature or approval.
Everyday checklist
Do not sign prompts presented as support verification, account unlocking, urgent airdrops or security checks from unknown sources. After an action, verify that the result matches the intention. Save non-secret references such as the transaction hash, network and public address for troubleshooting, while keeping seed phrases, private keys and verification codes private.