Transaction Checks

Address checks

For address checks, start by identifying the account, network and intended action. Before sending assets, confirm the address, network, amount and gas requirement. After broadcast, use the transaction hash to review on-chain status. Keep verifiable information available—such as the address, network name, transaction hash and approval target—instead of relying on vague interface messages.

Practical checks

After an on-chain transaction is broadcast, a wallet provider generally cannot reverse it unilaterally. Confirmation should be checked against the relevant network. Congestion or inadequate fees can extend waiting times, so repeated duplicate actions should be avoided while a transaction is still pending.

Security is part of every step, not only incident response. For each transfer, signature or approval, identify the target, network, amount or permission scope. Treat unfamiliar domains, links and unexpected requests with caution, even when they appear inside a familiar workflow.

Network checks

For network checks, start by identifying the account, network and intended action. Before sending assets, confirm the address, network, amount and gas requirement. After broadcast, use the transaction hash to review on-chain status. Keep verifiable information available—such as the address, network name, transaction hash and approval target—instead of relying on vague interface messages.

Practical checks

On-chain activity is easier to understand when the wallet interface is separated from the underlying network state. A wallet organizes accounts, networks and transaction data, while the blockchain ultimately determines confirmation. If a balance, status or approval looks unusual, first verify the selected network, then review the address, transaction hash or contract information.

Seed phrases and private keys are credentials that remain under the user’s custody. imtoken staff will not ask for them, and they should never be sent to another person together with verification codes. Public devices, unknown networks and remote-control software introduce additional risk.

Amount and fees

For amount and fees, start by identifying the account, network and intended action. Before sending assets, confirm the address, network, amount and gas requirement. After broadcast, use the transaction hash to review on-chain status. Keep verifiable information available—such as the address, network name, transaction hash and approval target—instead of relying on vague interface messages.

Practical checks

Security is part of every step, not only incident response. For each transfer, signature or approval, identify the target, network, amount or permission scope. Treat unfamiliar domains, links and unexpected requests with caution, even when they appear inside a familiar workflow.

Networks can differ in fees, confirmation behavior, block explorers and asset rules. Similar-looking addresses do not prove that two networks are interchangeable. Before sending, verify the address, network and amount together and make sure the account has enough of the required gas asset.

Post-broadcast confirmation

For post-broadcast confirmation, start by identifying the account, network and intended action. Before sending assets, confirm the address, network, amount and gas requirement. After broadcast, use the transaction hash to review on-chain status. Keep verifiable information available—such as the address, network name, transaction hash and approval target—instead of relying on vague interface messages.

Practical checks

Seed phrases and private keys are credentials that remain under the user’s custody. imtoken staff will not ask for them, and they should never be sent to another person together with verification codes. Public devices, unknown networks and remote-control software introduce additional risk.

Third-party DApps and smart contracts can contain technical risks, malicious logic or misleading permission requests. Connecting a wallet does not mean every later prompt should be accepted. Each signature and approval should be reviewed on its own, and unused permissions should be revoked when appropriate.

Action checklist