Signature Requests

What a signature means

Signature Requests is best understood as a sequence of decisions rather than a single wallet feature. When reviewing what a signature means, first identify the active network, account and asset, then compare what the interface shows with what the chain can actually confirm. A wallet helps organize and submit actions, while final transaction state is determined by the network.

If what a signature means involves signing, approvals or moving value, treat every request as a fresh decision. A previous connection to a DApp does not make later requests automatically trustworthy, and a contract used before may request a broader permission next time. Stop when the domain, network, requested permission or transaction details differ from your expectation.

Confirm that the active network matches the context for what a signature means
Use public addresses or transaction hashes for troubleshooting; never disclose a seed phrase or private key
Stop when a signature, approval or fee differs from what you expected

Message signing

In practice, mistakes around message signing often come from missing context rather than from the button being pressed. Similar address formats can exist across networks, and tokens with the same symbol can be issued by different contracts. Treat network, address, contract, amount and transaction status as one verification set instead of checking them in isolation.

The review should also reflect the fact that confirmed blockchain transactions are generally not something a wallet can unilaterally reverse. Cross-network, Layer 2 and contract interactions may have different fee, waiting and settlement behavior from a straightforward transfer, so allow enough time to verify the final state.

Confirm that the active network matches the context for message signing
Use public addresses or transaction hashes for troubleshooting; never disclose a seed phrase or private key
Stop when a signature, approval or fee differs from what you expected

Transaction signing

If transaction signing involves signing, approvals or moving value, treat every request as a fresh decision. A previous connection to a DApp does not make later requests automatically trustworthy, and a contract used before may request a broader permission next time. Stop when the domain, network, requested permission or transaction details differ from your expectation.

Security is strengthened by reducing single points of failure. Seed phrases and private keys remain under the user's control; support staff should never ask for them, and they should not be pasted into chat, websites or remote-control sessions. Public addresses, transaction hashes and explorer data are normally sufficient for troubleshooting a transaction.

Confirm that the active network matches the context for transaction signing
Use public addresses or transaction hashes for troubleshooting; never disclose a seed phrase or private key
Stop when a signature, approval or fee differs from what you expected

Contract calls

After working with contract calls, keep the transaction hash and verify the result on an appropriate explorer. If a third-party DApp was involved, review sessions and approvals that are no longer needed. A repeatable cycle of checking before an action, reading during signing and reviewing afterward is more dependable than relying on a one-time warning.

Confirm that the active network matches the context for contract calls
Use public addresses or transaction hashes for troubleshooting; never disclose a seed phrase or private key
Stop when a signature, approval or fee differs from what you expected

Suspicious requests

Signature Requests is best understood as a sequence of decisions rather than a single wallet feature. When reviewing suspicious requests, first identify the active network, account and asset, then compare what the interface shows with what the chain can actually confirm. A wallet helps organize and submit actions, while final transaction state is determined by the network.

Confirm that the active network matches the context for suspicious requests
Use public addresses or transaction hashes for troubleshooting; never disclose a seed phrase or private key
Stop when a signature, approval or fee differs from what you expected

Reject and exit

After working with reject and exit, keep the transaction hash and verify the result on an appropriate explorer. If a third-party DApp was involved, review sessions and approvals that are no longer needed. A repeatable cycle of checking before an action, reading during signing and reviewing afterward is more dependable than relying on a one-time warning.

In practice, mistakes around reject and exit often come from missing context rather than from the button being pressed. Similar address formats can exist across networks, and tokens with the same symbol can be issued by different contracts. Treat network, address, contract, amount and transaction status as one verification set instead of checking them in isolation.

Confirm that the active network matches the context for reject and exit
Use public addresses or transaction hashes for troubleshooting; never disclose a seed phrase or private key
Stop when a signature, approval or fee differs from what you expected

A final review before you act

On-chain actions should be reviewable. Verify address, network and amount before transfers; read each signing request; check the target and scope of approvals; then keep the transaction hash and review connections or permissions that are no longer needed.

Keep seed phrases and private keys offline and never send them to anyone
Verify address, network, amount and fees before transferring
Review each DApp signature or approval independently
Re-check and remove sessions or approvals that are no longer needed