Getting Started

What to confirm before you begin

Verification focus

When working with Getting Started, start by keeping what a wallet is, what an address is, and seed phrases and private keys in the same context. Give first-time wallet users the smallest complete set of concepts needed before creating, backing up, sending, receiving or connecting to DApps. A familiar label or icon is not enough on its own; the active network, account, address, contract or transaction record should agree with the action you intend to take. For consequential actions, understanding exactly what is being requested matters more than moving quickly through a confirmation screen.

A practical Getting Started workflow can follow a consistent sequence: confirm the source and destination, review seed phrases and private keys, then verify networks and gas in the correct network context, and finally inspect transaction hashes together with the possible on-chain consequence. Only after that review should you sign or submit. Keep non-secret evidence such as a transaction hash or contract address so the result can be checked later.

The central risk around Getting Started is that Without understanding recovery material, networks and approvals, users can mistakenly treat irreversible on-chain actions like ordinary account actions. If an unexpected network switch, unfamiliar contract, excessive approval, changed address or urgency tactic appears, stop before confirming. Seed phrases, private keys and verification codes are never normal troubleshooting material; imtoken staff will not ask for them and they should not be submitted through websites, chats or remote-control tools.

Follow the main workflow in order

Key observations during the workflow

For “Follow the main workflow in order”, what an address is establishes the starting point, seed phrases and private keys helps explain whether the process is progressing as expected, and networks and gas is often the detail that can be cross-checked against wallet history or public on-chain data. If those facts conflict, stop and verify the source again. Transfers, signatures, approvals and cross-layer actions deserve a complete review even when the interface looks familiar.

It also helps to separate interface information from verifiable on-chain facts. networks and gas may describe the intent of an action and transaction hashes may provide useful status context, but important decisions should still be checked against DApps and approvals and the relevant network record. Wallet labels, token symbols, DApp copy and promotional language can all be imitated, so familiarity is not proof of authenticity.

When working with Getting Started, start by keeping DApps and approvals, what a wallet is, and what an address is in the same context. Give first-time wallet users the smallest complete set of concepts needed before creating, backing up, sending, receiving or connecting to DApps. A familiar label or icon is not enough on its own; the active network, account, address, contract or transaction record should agree with the action you intend to take. For consequential actions, understanding exactly what is being requested matters more than moving quickly through a confirmation screen.

The final review before signing or submitting

Verification focus

A practical Getting Started workflow can follow a consistent sequence: confirm the source and destination, review seed phrases and private keys, then verify networks and gas in the correct network context, and finally inspect transaction hashes together with the possible on-chain consequence. Only after that review should you sign or submit. Keep non-secret evidence such as a transaction hash or contract address so the result can be checked later.

The central risk around Getting Started is that Without understanding recovery material, networks and approvals, users can mistakenly treat irreversible on-chain actions like ordinary account actions. If an unexpected network switch, unfamiliar contract, excessive approval, changed address or urgency tactic appears, stop before confirming. Seed phrases, private keys and verification codes are never normal troubleshooting material; imtoken staff will not ask for them and they should not be submitted through websites, chats or remote-control tools.

For “The final review before signing or submitting”, what a wallet is establishes the starting point, what an address is helps explain whether the process is progressing as expected, and seed phrases and private keys is often the detail that can be cross-checked against wallet history or public on-chain data. If those facts conflict, stop and verify the source again. Transfers, signatures, approvals and cross-layer actions deserve a complete review even when the interface looks familiar.

• Review what a wallet is in the correct network context.
• Review what an address is in the correct network context.
• Review seed phrases and private keys in the correct network context.
• Review networks and gas in the correct network context.
• Review transaction hashes in the correct network context.

How to respond when something looks wrong

Do not let urgency replace judgment

It also helps to separate interface information from verifiable on-chain facts. networks and gas may describe the intent of an action and transaction hashes may provide useful status context, but important decisions should still be checked against DApps and approvals and the relevant network record. Wallet labels, token symbols, DApp copy and promotional language can all be imitated, so familiarity is not proof of authenticity.

When working with Getting Started, start by keeping DApps and approvals, what a wallet is, and what an address is in the same context. Give first-time wallet users the smallest complete set of concepts needed before creating, backing up, sending, receiving or connecting to DApps. A familiar label or icon is not enough on its own; the active network, account, address, contract or transaction record should agree with the action you intend to take. For consequential actions, understanding exactly what is being requested matters more than moving quickly through a confirmation screen.

A practical Getting Started workflow can follow a consistent sequence: confirm the source and destination, review what an address is, then verify seed phrases and private keys in the correct network context, and finally inspect networks and gas together with the possible on-chain consequence. Only after that review should you sign or submit. Keep non-secret evidence such as a transaction hash or contract address so the result can be checked later.

Records and follow-up checks after completion

Verification focus

The central risk around Getting Started is that Without understanding recovery material, networks and approvals, users can mistakenly treat irreversible on-chain actions like ordinary account actions. If an unexpected network switch, unfamiliar contract, excessive approval, changed address or urgency tactic appears, stop before confirming. Seed phrases, private keys and verification codes are never normal troubleshooting material; imtoken staff will not ask for them and they should not be submitted through websites, chats or remote-control tools.

For “Records and follow-up checks after completion”, what a wallet is establishes the starting point, what an address is helps explain whether the process is progressing as expected, and seed phrases and private keys is often the detail that can be cross-checked against wallet history or public on-chain data. If those facts conflict, stop and verify the source again. Transfers, signatures, approvals and cross-layer actions deserve a complete review even when the interface looks familiar.

It also helps to separate interface information from verifiable on-chain facts. seed phrases and private keys may describe the intent of an action and networks and gas may provide useful status context, but important decisions should still be checked against transaction hashes and the relevant network record. Wallet labels, token symbols, DApp copy and promotional language can all be imitated, so familiarity is not proof of authenticity.