Before you start
Before acting, make sure you understand the difference between receiving address and sending network and are ready to verify gas. Do not continue with any webpage that asks you to enter a seed phrase, private key or verification code.
- Confirm the network matches the intended receiving address
- Be ready to verify sending network and gas
- Never provide a seed phrase, private key or verification code to a website or another person
- Stop when a transaction hash request cannot be explained
Understand the boundary of receiving address
Send and Receive: Address, Network, Gas and Confirmation is easier to use correctly when receiving address is treated as a verifiable part of an on-chain workflow rather than a label in the interface. Use a verifiable process for receiving addresses, sending networks, amounts, gas, transaction hashes and on-chain confirmations to reduce preventable transfer errors. The key distinction is between what a wallet displays for convenience and what the target blockchain records as state. A balance, network name, contract reference or transaction status should therefore be checked in the context of the network where the action actually occurs.
Looking at receiving address together with sending network prevents many avoidable mistakes. Similar address formats can appear on different networks, familiar token names can refer to different contracts, and a request can look routine while asking for broader permissions than expected. Before acting on gas, confirm the source of the request, the selected network, the destination or contract and the exact action being authorized.
A robust routine keeps enough information to review the action later. Save a transaction hash when relevant, use an appropriate block explorer to check on-chain status, read signature or approval details before confirming and stop when a request cannot be explained. Familiar names, icons or balances are not substitutes for verification, and confirmed on-chain actions are generally not reversible by a wallet on its own.
- Confirm that you are evaluating receiving address, not a similar-looking concept.
- Tie sending network to the intended network, address or contract.
- Keep at least one verifiable reference before proceeding with gas.
How sending network changes the workflow
Send and Receive: Address, Network, Gas and Confirmation is easier to use correctly when sending network is treated as a verifiable part of an on-chain workflow rather than a label in the interface. Use a verifiable process for receiving addresses, sending networks, amounts, gas, transaction hashes and on-chain confirmations to reduce preventable transfer errors. The key distinction is between what a wallet displays for convenience and what the target blockchain records as state. A balance, network name, contract reference or transaction status should therefore be checked in the context of the network where the action actually occurs.
Looking at sending network together with gas prevents many avoidable mistakes. Similar address formats can appear on different networks, familiar token names can refer to different contracts, and a request can look routine while asking for broader permissions than expected. Before acting on transaction hash, confirm the source of the request, the selected network, the destination or contract and the exact action being authorized.
A robust routine keeps enough information to review the action later. Save a transaction hash when relevant, use an appropriate block explorer to check on-chain status, read signature or approval details before confirming and stop when a request cannot be explained. Familiar names, icons or balances are not substitutes for verification, and confirmed on-chain actions are generally not reversible by a wallet on its own.
- Confirm that you are evaluating sending network, not a similar-looking concept.
- Tie gas to the intended network, address or contract.
- Keep at least one verifiable reference before proceeding with transaction hash.
What to verify around gas
Send and Receive: Address, Network, Gas and Confirmation is easier to use correctly when gas is treated as a verifiable part of an on-chain workflow rather than a label in the interface. Use a verifiable process for receiving addresses, sending networks, amounts, gas, transaction hashes and on-chain confirmations to reduce preventable transfer errors. The key distinction is between what a wallet displays for convenience and what the target blockchain records as state. A balance, network name, contract reference or transaction status should therefore be checked in the context of the network where the action actually occurs.
Looking at gas together with transaction hash prevents many avoidable mistakes. Similar address formats can appear on different networks, familiar token names can refer to different contracts, and a request can look routine while asking for broader permissions than expected. Before acting on confirmation status, confirm the source of the request, the selected network, the destination or contract and the exact action being authorized.
A robust routine keeps enough information to review the action later. Save a transaction hash when relevant, use an appropriate block explorer to check on-chain status, read signature or approval details before confirming and stop when a request cannot be explained. Familiar names, icons or balances are not substitutes for verification, and confirmed on-chain actions are generally not reversible by a wallet on its own.
- Confirm that you are evaluating gas, not a similar-looking concept.
- Tie transaction hash to the intended network, address or contract.
- Keep at least one verifiable reference before proceeding with confirmation status.
How transaction hash relates to confirmation status
Send and Receive: Address, Network, Gas and Confirmation is easier to use correctly when transaction hash is treated as a verifiable part of an on-chain workflow rather than a label in the interface. Use a verifiable process for receiving addresses, sending networks, amounts, gas, transaction hashes and on-chain confirmations to reduce preventable transfer errors. The key distinction is between what a wallet displays for convenience and what the target blockchain records as state. A balance, network name, contract reference or transaction status should therefore be checked in the context of the network where the action actually occurs.
Looking at transaction hash together with confirmation status prevents many avoidable mistakes. Similar address formats can appear on different networks, familiar token names can refer to different contracts, and a request can look routine while asking for broader permissions than expected. Before acting on receiving address, confirm the source of the request, the selected network, the destination or contract and the exact action being authorized.
A robust routine keeps enough information to review the action later. Save a transaction hash when relevant, use an appropriate block explorer to check on-chain status, read signature or approval details before confirming and stop when a request cannot be explained. Familiar names, icons or balances are not substitutes for verification, and confirmed on-chain actions are generally not reversible by a wallet on its own.
- Confirm that you are evaluating transaction hash, not a similar-looking concept.
- Tie confirmation status to the intended network, address or contract.
- Keep at least one verifiable reference before proceeding with receiving address.
Common mistakes and safer habits
Send and Receive: Address, Network, Gas and Confirmation is easier to use correctly when confirmation status is treated as a verifiable part of an on-chain workflow rather than a label in the interface. Use a verifiable process for receiving addresses, sending networks, amounts, gas, transaction hashes and on-chain confirmations to reduce preventable transfer errors. The key distinction is between what a wallet displays for convenience and what the target blockchain records as state. A balance, network name, contract reference or transaction status should therefore be checked in the context of the network where the action actually occurs.
Looking at confirmation status together with receiving address prevents many avoidable mistakes. Similar address formats can appear on different networks, familiar token names can refer to different contracts, and a request can look routine while asking for broader permissions than expected. Before acting on sending network, confirm the source of the request, the selected network, the destination or contract and the exact action being authorized.
A robust routine keeps enough information to review the action later. Save a transaction hash when relevant, use an appropriate block explorer to check on-chain status, read signature or approval details before confirming and stop when a request cannot be explained. Familiar names, icons or balances are not substitutes for verification, and confirmed on-chain actions are generally not reversible by a wallet on its own.
- Confirm that you are evaluating confirmation status, not a similar-looking concept.
- Tie receiving address to the intended network, address or contract.
- Keep at least one verifiable reference before proceeding with sending network.
Action checklist
- Verify receiving address
- Confirm sending network
- Review gas
- Understand the consequence of transaction hash
- Review confirmation status after completion