imtoken Knowledge Center
Create & Backup｜imtoken
Create or import a wallet while keeping recovery secrets offline and private.
On this page
Understand keys first
To understand Create & Backup, place understand keys first inside the full on-chain workflow instead of treating it as an isolated label. Seed phrases and private keys should remain under the user's control. Recovery secrets should be backed up offline and never sent to support. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. Screenshots, cloud notes and remote-control sessions increase exposure. A recovery check should happen only in a trusted environment. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach understand keys first is to use a consistent review sequence. First, seed phrases and private keys should remain under the user's control. Next, recovery secrets should be backed up offline and never sent to support. After a transaction, signature or approval is submitted, screenshots, cloud notes and remote-control sessions increase exposure. Finally, a recovery check should happen only in a trusted environment. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- Seed phrases and private keys should remain under the user's control
- Recovery secrets should be backed up offline and never sent to support
- Screenshots, cloud notes and remote-control sessions increase exposure
- A recovery check should happen only in a trusted environment
Offline backup practices
To understand Create & Backup, place offline backup practices inside the full on-chain workflow instead of treating it as an isolated label. Seed phrases and private keys should remain under the user's control. Recovery secrets should be backed up offline and never sent to support. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. Screenshots, cloud notes and remote-control sessions increase exposure. A recovery check should happen only in a trusted environment. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach offline backup practices is to use a consistent review sequence. First, seed phrases and private keys should remain under the user's control. Next, recovery secrets should be backed up offline and never sent to support. After a transaction, signature or approval is submitted, screenshots, cloud notes and remote-control sessions increase exposure. Finally, a recovery check should happen only in a trusted environment. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- Seed phrases and private keys should remain under the user's control
- Recovery secrets should be backed up offline and never sent to support
- Screenshots, cloud notes and remote-control sessions increase exposure
- A recovery check should happen only in a trusted environment
Verify your backup
To understand Create & Backup, place verify your backup inside the full on-chain workflow instead of treating it as an isolated label. Seed phrases and private keys should remain under the user's control. Recovery secrets should be backed up offline and never sent to support. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. Screenshots, cloud notes and remote-control sessions increase exposure. A recovery check should happen only in a trusted environment. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach verify your backup is to use a consistent review sequence. First, seed phrases and private keys should remain under the user's control. Next, recovery secrets should be backed up offline and never sent to support. After a transaction, signature or approval is submitted, screenshots, cloud notes and remote-control sessions increase exposure. Finally, a recovery check should happen only in a trusted environment. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- Seed phrases and private keys should remain under the user's control
- Recovery secrets should be backed up offline and never sent to support
- Screenshots, cloud notes and remote-control sessions increase exposure
- A recovery check should happen only in a trusted environment
Risks when importing
To understand Create & Backup, place risks when importing inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify risks when importing in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.
A practical way to approach risks when importing is to use a consistent review sequence. First, the practical point is to verify risks when importing in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.
- The practical point is to verify risks when importing in the context of the selected blockchain network
- The user should compare the request with the intended address, asset, account or contract before confirming
- On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
- Third-party DApps, services and smart contracts can introduce risks that need separate review