Create & Backup

What to confirm before you begin

Verification focus

When working with Create & Backup, start by keeping creating a new wallet, importing an existing wallet, and seed phrase generation in the same context. Establish a complete create-and-backup sequence while keeping seed phrases and private keys under the user’s control. 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 Create & Backup workflow can follow a consistent sequence: confirm the source and destination, review seed phrase generation, then verify offline transcription in the correct network context, and finally inspect backup verification 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 Create & Backup is that Screenshots, cloud sync, chat forwarding and entering recovery data into unknown websites all increase exposure risk. 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”, importing an existing wallet establishes the starting point, seed phrase generation helps explain whether the process is progressing as expected, and offline transcription 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. offline transcription may describe the intent of an action and backup verification may provide useful status context, but important decisions should still be checked against storage of recovery material 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 Create & Backup, start by keeping storage of recovery material, creating a new wallet, and importing an existing wallet in the same context. Establish a complete create-and-backup sequence while keeping seed phrases and private keys under the user’s control. 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 Create & Backup workflow can follow a consistent sequence: confirm the source and destination, review seed phrase generation, then verify offline transcription in the correct network context, and finally inspect backup verification 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 Create & Backup is that Screenshots, cloud sync, chat forwarding and entering recovery data into unknown websites all increase exposure risk. 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”, creating a new wallet establishes the starting point, importing an existing wallet helps explain whether the process is progressing as expected, and seed phrase generation 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 creating a new wallet in the correct network context.
• Review importing an existing wallet in the correct network context.
• Review seed phrase generation in the correct network context.
• Review offline transcription in the correct network context.
• Review backup verification 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. offline transcription may describe the intent of an action and backup verification may provide useful status context, but important decisions should still be checked against storage of recovery material 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 Create & Backup, start by keeping storage of recovery material, creating a new wallet, and importing an existing wallet in the same context. Establish a complete create-and-backup sequence while keeping seed phrases and private keys under the user’s control. 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 Create & Backup workflow can follow a consistent sequence: confirm the source and destination, review importing an existing wallet, then verify seed phrase generation in the correct network context, and finally inspect offline transcription 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 Create & Backup is that Screenshots, cloud sync, chat forwarding and entering recovery data into unknown websites all increase exposure risk. 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”, creating a new wallet establishes the starting point, importing an existing wallet helps explain whether the process is progressing as expected, and seed phrase generation 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 phrase generation may describe the intent of an action and offline transcription may provide useful status context, but important decisions should still be checked against backup verification 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.