Send & Receive｜imtoken

Follow a verifiable send-and-receive workflow from address checks to confirmations.

On this page

Confirm the network before receiving

To understand Send & Receive, place confirm the network before receiving inside the full on-chain workflow instead of treating it as an isolated label. Gas pays for network processing or contract execution. Fee estimates and confirmation times change with network conditions. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. A transaction hash is the best starting point for checking status. Failed or pending transactions should be distinguished before retrying. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach confirm the network before receiving is to use a consistent review sequence. First, gas pays for network processing or contract execution. Next, fee estimates and confirmation times change with network conditions. After a transaction, signature or approval is submitted, a transaction hash is the best starting point for checking status. Finally, failed or pending transactions should be distinguished before retrying. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

Gas pays for network processing or contract execution
Fee estimates and confirmation times change with network conditions
A transaction hash is the best starting point for checking status
Failed or pending transactions should be distinguished before retrying

Three checks before sending

To understand Send & Receive, place three checks before sending inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify three checks before sending in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach three checks before sending is to use a consistent review sequence. First, the practical point is to verify three checks before sending in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

The practical point is to verify three checks before sending in the context of the selected blockchain network
The user should compare the request with the intended address, asset, account or contract before confirming
On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
Third-party DApps, services and smart contracts can introduce risks that need separate review

What happens after submission

To understand Send & Receive, place what happens after submission inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify what happens after submission in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach what happens after submission is to use a consistent review sequence. First, the practical point is to verify what happens after submission in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

The practical point is to verify what happens after submission in the context of the selected blockchain network
The user should compare the request with the intended address, asset, account or contract before confirming
On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
Third-party DApps, services and smart contracts can introduce risks that need separate review

Troubleshooting transfers

To understand Send & Receive, place troubleshooting transfers inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify troubleshooting transfers in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach troubleshooting transfers is to use a consistent review sequence. First, the practical point is to verify troubleshooting transfers in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

The practical point is to verify troubleshooting transfers in the context of the selected blockchain network
The user should compare the request with the intended address, asset, account or contract before confirming
On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
Third-party DApps, services and smart contracts can introduce risks that need separate review

Download imtoken Read FAQ →