Message signatures and transaction signatures
Message signatures and transaction signatures is easier to manage when the interface label is separated from the actual on-chain object. In the context of Signature Requests, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Message signatures and transaction signatures is to break the action into source, destination, permissions or amount, network state and final outcome. When message is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Message signatures and transaction signatures. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Message signatures and transaction signatures
- Keep verifiable public information when message is involved
- Never send a seed phrase, private key or verification code to anyone
Read before signing
Read before signing is easier to manage when the interface label is separated from the actual on-chain object. In the context of Signature Requests, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Read before signing is to break the action into source, destination, permissions or amount, network state and final outcome. When signature is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Read before signing. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Read before signing
- Keep verifiable public information when signature is involved
- Never send a seed phrase, private key or verification code to anyone
Unknown domains and unusual requests
Unknown domains and unusual requests is easier to manage when the interface label is separated from the actual on-chain object. In the context of Signature Requests, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Unknown domains and unusual requests is to break the action into source, destination, permissions or amount, network state and final outcome. When domain is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Unknown domains and unusual requests. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Unknown domains and unusual requests
- Keep verifiable public information when domain is involved
- Never send a seed phrase, private key or verification code to anyone
Potential effects after signing
Potential effects after signing is easier to manage when the interface label is separated from the actual on-chain object. In the context of Signature Requests, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Potential effects after signing is to break the action into source, destination, permissions or amount, network state and final outcome. When transaction is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Potential effects after signing. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Potential effects after signing
- Keep verifiable public information when transaction is involved
- Never send a seed phrase, private key or verification code to anyone
What to do with suspicious requests
What to do with suspicious requests is easier to manage when the interface label is separated from the actual on-chain object. In the context of Signature Requests, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with What to do with suspicious requests is to break the action into source, destination, permissions or amount, network state and final outcome. When risk is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of What to do with suspicious requests. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in What to do with suspicious requests
- Keep verifiable public information when risk is involved
- Never send a seed phrase, private key or verification code to anyone