Wallet Guides

Establish the right context: create

When using Wallet Guides, first identify whether the current object is an account, asset, network, transaction or permission. Then relate create to back up instead of reading either label alone.

For Wallet Guides, a repeatable verification habit is more durable than memorizing where a button appears. Check create, then back up, and finally receive. Interfaces can change and network conditions can move, while the reasoning behind those checks remains useful.

If a result differs from expectations, record create, back up, and other non-secret evidence, then reconstruct the sequence of actions. Never send recovery secrets to someone offering to “restore” or “verify” an account, and avoid untrusted remote-control software.

Understand how it works in practice: back up

How back up, receive, and send relate in practice

When a request involves back up, slow the decision down enough to identify what it changes, which network it relies on, and whether receive can be independently verified.

A useful review order is source, object, request, and result. The source establishes where the action came from, back up identifies the object, and receive clarifies the scope. After submission, keep a transaction hash or other public record so that changing status can be checked again without relying on one interface message.

Verification continues after submission. Keep public evidence related to back up and use receive to review status when necessary. On-chain transactions generally cannot be reversed by a wallet provider alone, and third-party DApps or contracts can carry their own risks, so blind resubmission is a poor troubleshooting method.

• Confirm the real object behind back up
• Check the network or permission scope for receive
• Use send or another public record to verify the result
• Never share a seed phrase, private key or verification code

Review the action step by step: receive

A practical way to approach receive is to place it inside a real task and start with send.

Do not treat “already connected,” “used before,” or “looks familiar” as sufficient evidence. Review receive for the actual object, send for the transaction or permission boundary, and transaction history for the resulting state. If one step remains unclear, declining is a valid outcome.

The purpose of learning Wallet Guides is to understand the action rather than mechanically complete it. Whenever receive, send, or the expected result cannot be explained, preserve the option to decline, exit, or verify again later.

Recognize common mistakes and risks: send

How send, transaction history, and create relate in practice

send is easy to misunderstand when context is missing. The account, transaction history, and the intended action should agree before a familiar interface is treated as meaningful evidence.

The same term can behave differently across networks or DApps, so send should always be interpreted in context. transaction history provides a second verification angle, while create helps confirm what actually happened afterward. Network-specific rules should be checked against trustworthy information for that network.

Over time, revisit send and transaction history, remove connections or permissions that are no longer needed, and keep the device and browser environment trustworthy. Security is not an absolute promise; it is a process of reducing secret exposure, mistaken approvals, and avoidable uncertainty.

• Confirm the real object behind send
• Check the network or permission scope for transaction history
• Use create or another public record to verify the result
• Never share a seed phrase, private key or verification code

Build a repeatable verification habit: transaction history

Within Wallet Guides, transaction history is not an isolated term; it affects create and the on-chain result a user eventually sees.

If an interface mixes several layers of information, check transaction history, create, and back up separately. Names, icons, and familiar layouts are presentation details, not substitutes for the actual network, address, contract, or on-chain state. When the evidence conflicts, fewer new actions usually make troubleshooting easier.

Keep the security boundary explicit: the user controls the seed phrase and private keys, and imtoken will never ask for them. If a third party links transaction history to a request for recovery secrets or verification codes, stop. When create is involved, also verify the address, network, amount or permission scope.