Check network and address before receiving
Step 1: Check before you continue
When thinking about check network and address before receiving, separate the network, address, signature and transaction state. A wallet interface helps organize information, but the authoritative asset state is recorded by the relevant blockchain. Before acting, confirm that the selected network matches the asset and destination, and do not rely on names or icons alone to identify a token.
Step 2: Check before you continue
In real use, check network and address before receiving often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
Review amount and gas before sending
Step 3: Check before you continue
In real use, review amount and gas before sending often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
Step 4: Check before you continue
If the result does not match your expectation, avoid repeating the same action immediately. Save the transaction hash and inspect it on a block explorer for the correct network to see whether it was broadcast, succeeded and reached confirmation. On-chain transactions are usually not something a wallet can unilaterally reverse, so checks before action matter more than recovery promises after the fact.
When a small test transfer can help
Step 5: Check before you continue
If the result does not match your expectation, avoid repeating the same action immediately. Save the transaction hash and inspect it on a block explorer for the correct network to see whether it was broadcast, succeeded and reached confirmation. On-chain transactions are usually not something a wallet can unilaterally reverse, so checks before action matter more than recovery promises after the fact.
Step 6: Check before you continue
For Send & Receive, it is useful to distinguish the wallet, the blockchain network and any third-party DApp. A contract can introduce code, permission and operational risks. imtoken staff will never ask for a seed phrase or private key and should not be treated as an entity that can recover those credentials for the user.
Broadcast and confirmation
Step 7: Check before you continue
For Send & Receive, it is useful to distinguish the wallet, the blockchain network and any third-party DApp. A contract can introduce code, permission and operational risks. imtoken staff will never ask for a seed phrase or private key and should not be treated as an entity that can recover those credentials for the user.
Step 8: Check before you continue
Long-term habits are more useful than memorizing a button. For broadcast and confirmation, consistently review the address, network, amount or requested permission, and check whether old connections or approvals are still needed. Shared computers, remote-control sessions and untrusted network environments deserve extra caution.
Why transaction hashes matter
Step 9: Check before you continue
Long-term habits are more useful than memorizing a button. For why transaction hashes matter, consistently review the address, network, amount or requested permission, and check whether old connections or approvals are still needed. Shared computers, remote-control sessions and untrusted network environments deserve extra caution.
Step 10: Check before you continue
The purpose of this material is not to promise returns or absolute safety. It is to make each on-chain action easier to reason about. Signing, approving, bridging or using validator-related services can involve network conditions, contract risk, waiting periods and market volatility, so participation should always be an independent decision.
Common transfer mistakes
Step 11: Check before you continue
The purpose of this material is not to promise returns or absolute safety. It is to make each on-chain action easier to reason about. Signing, approving, bridging or using validator-related services can involve network conditions, contract risk, waiting periods and market volatility, so participation should always be an independent decision.
Step 12: Check before you continue
When thinking about common transfer mistakes, separate the network, address, signature and transaction state. A wallet interface helps organize information, but the authoritative asset state is recorded by the relevant blockchain. Before acting, confirm that the selected network matches the asset and destination, and do not rely on names or icons alone to identify a token.
Keep your seed phrase and private keys offline where practical, never send them to another person, check address/network/amount before transfer, and inspect each signature or approval request independently.