Before you begin
Before receiving, confirm the exact network and then share the address intended for that network. Sender and receiver should be aligned on the chain being used. To understand Send & Receive, place the concept inside a real on-chain workflow: where the information comes from, what the user confirms, how the network records the result, and which outcomes cannot normally be reversed by a wallet provider. This makes inconsistencies easier to spot across different apps and networks.
Step-by-step workflow
Before sending, review the address, network, asset, amount and gas. A small test transfer can be useful when working with a new address or unfamiliar route. In practice, start with the intended outcome and then verify the relevant fields. If an address, network, contract or permission connected to Send & Receive cannot be explained, stop rather than accepting the default button. Public blockchain data can often be used as a second source of verification.
A practical way to check
Separate what you can verify publicly from what must remain secret. Network names, public addresses, transaction hashes and contract addresses can be checked against public blockchain data. Seed phrases and private keys should never be disclosed for this purpose.
How to verify the result
After broadcast, the transaction hash is your reference for checking on-chain status. Confirmation time depends on network activity, fee settings and the chain’s own rules. Security is not a single “perfect protection” switch. It comes from repeatable habits: trusted entry points, independent checks, least-necessary permissions, offline protection of secret credentials, and a willingness to reject abnormal requests.
imtoken staff will not ask for your seed phrase or private key. Review the address, network and request before any transfer, signature or approval.
Common risks and responses
Most confirmed blockchain transactions cannot be reversed by a wallet provider. Treat urgent requests to “send now” or “unlock funds” as a reason to verify independently. After an action, verify that the result matches the intention. Save non-secret references such as the transaction hash, network and public address for troubleshooting, while keeping seed phrases, private keys and verification codes private.