Message signing
Message signing is a distinct part of understanding Signature Requests. A signature proves that the controller of an address approved some data. A message signature may not immediately transfer value, but it can still be used for authentication, permissions or follow-on actions, so the content deserves careful review. A DApp may request a public address, a message signature, a transaction signature or a token approval. These requests have very different consequences. Treat every prompt as a separate decision: verify the domain and contract, understand the request, then approve or reject it.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
Transaction signing
Transaction signing is a distinct part of understanding Signature Requests. A signature proves that the controller of an address approved some data. A message signature may not immediately transfer value, but it can still be used for authentication, permissions or follow-on actions, so the content deserves careful review. A DApp may request a public address, a message signature, a transaction signature or a token approval. These requests have very different consequences. Treat every prompt as a separate decision: verify the domain and contract, understand the request, then approve or reject it.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
- Confirm the active network before sending or approving.
- Compare the full destination or contract details.
- Keep recovery material offline and private.
Typed data
Typed data is a distinct part of understanding Signature Requests. A signature proves that the controller of an address approved some data. A message signature may not immediately transfer value, but it can still be used for authentication, permissions or follow-on actions, so the content deserves careful review. A DApp may request a public address, a message signature, a transaction signature or a token approval. These requests have very different consequences. Treat every prompt as a separate decision: verify the domain and contract, understand the request, then approve or reject it.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
Reject suspicious requests
Reject suspicious requests is a distinct part of understanding Signature Requests. A signature proves that the controller of an address approved some data. A message signature may not immediately transfer value, but it can still be used for authentication, permissions or follow-on actions, so the content deserves careful review. A DApp may request a public address, a message signature, a transaction signature or a token approval. These requests have very different consequences. Treat every prompt as a separate decision: verify the domain and contract, understand the request, then approve or reject it.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
Security and risk reminder
Blockchain transactions are generally irreversible by a wallet provider. Third-party DApps and smart contracts can contain technical or business risks. Review every signature and approval independently, and consider revoking permissions you no longer use.