Step-by-step Guide
Create & Backup
A practical imtoken guide to create & backup, including core concepts, verification steps and risk-aware usage.
Confirm the account, network and intended destination. Keep seed phrases and private keys offline and never provide them to another person.
- 01
Core concepts
From a risk perspective, seed phrase and private keys deserve an independent review. Once a transaction is confirmed on-chain, a wallet normally cannot reverse it unilaterally. DApps and smart contracts can also introduce permission and contract risks, so every signature, approval and transfer should be understood before it is accepted.
For creating a wallet, first define its role in the current task, then check whether importing a wallet and seed phrase are consistent. When private keys is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For offline backups, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: creating a wallet
- Cross-check: importing a wallet and seed phrase
- Review carefully: private keys
- Verify afterward: offline backups
- 02
Checks before you act
After a Create & Backup task is completed, review offline backups and creating a wallet to make sure the outcome matches the intent. Long-lived approvals and persistent connections should be revisited periodically. Good wallet hygiene is a repeated process of checking critical details and retaining traceable on-chain information, not a one-time setting.
For importing a wallet, first define its role in the current task, then check whether seed phrase and private keys are consistent. When offline backups is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For creating a wallet, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: importing a wallet
- Cross-check: seed phrase and private keys
- Review carefully: offline backups
- Verify afterward: creating a wallet
- 03
How to evaluate a live request
To understand Create & Backup, treat seed phrase and private keys as parts of the same on-chain workflow. The interface is only the entry point; the selected network, current chain state and permission scope determine what actually happens. Confirm the destination, source and network before continuing so the meaning of the request stays clear.
For seed phrase, first define its role in the current task, then check whether private keys and offline backups are consistent. When creating a wallet is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For importing a wallet, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: seed phrase
- Cross-check: private keys and offline backups
- Review carefully: creating a wallet
- Verify afterward: importing a wallet
- 04
Risks and boundaries
private keys rarely appears in isolation. It often intersects with offline backups and creating a wallet. A useful pattern is to separate each action into four checks: identify the object, verify the network, review permissions, and confirm the result. If one of those checks cannot be completed, stop and verify rather than relying on an unfamiliar site or remote instructions.
For private keys, first define its role in the current task, then check whether offline backups and creating a wallet are consistent. When importing a wallet is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For seed phrase, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: private keys
- Cross-check: offline backups and creating a wallet
- Review carefully: importing a wallet
- Verify afterward: seed phrase
- 05
How to verify the outcome
When using imtoken for Create & Backup, prioritize information that can be independently verified, such as addresses, network names, contract addresses, transaction hashes and block-explorer records. Visual design, urgency messages or claims from an unknown support account are not substitutes for verifiable on-chain details.
For offline backups, first define its role in the current task, then check whether creating a wallet and importing a wallet are consistent. When seed phrase is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For private keys, use on-chain records and the actual status as the source of truth. imtoken will not ask users to enter a seed phrase, private key or wallet recovery phrase on a web page, and it will not require remote control of a device for sensitive wallet actions.
- Confirm: offline backups
- Cross-check: creating a wallet and importing a wallet
- Review carefully: seed phrase
- Verify afterward: private keys
Final checks
- Never share your seed phrase, private key or verification code.
- Verify the address, network and amount before sending.
- Review each DApp signature and token approval independently.
- Use transaction hashes and block explorers to verify on-chain status.
- Revoke approvals and disconnect sessions that are no longer needed.