imtoken
Seed Phrase & Private Keys
Seed phrases and private keys are core account credentials and should remain under the user’s control, preferably offline.
Role of credentials
Role of credentials is a practical part of understanding Seed Phrase & Private Keys. Seed phrases and private keys are core account credentials and should remain under the user’s control, preferably offline. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.
A seed phrase commonly derives account keys, while a private key directly controls a specific account. Anyone who obtains these credentials may be able to control the corresponding assets.
For Role of credentials, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.
Practical checks
- Verify the network and account before working with role of credentials
- Double-check important addresses, contracts, amounts or permissions
- Never send a seed phrase, private key or verification code to anyone
Offline backup
Offline backup is a practical part of understanding Seed Phrase & Private Keys. Seed phrases and private keys are core account credentials and should remain under the user’s control, preferably offline. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.
A safer backup approach is to record credentials offline and keep them in a controlled environment rather than sending them through chat, email, cloud clipboards or screenshots. Backups should also account for physical loss and unauthorized access.
For Offline backup, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.
Practical checks
- Verify the network and account before working with offline backup
- Double-check important addresses, contracts, amounts or permissions
- Never send a seed phrase, private key or verification code to anyone
Common leak paths
Common leak paths is a practical part of understanding Seed Phrase & Private Keys. Seed phrases and private keys are core account credentials and should remain under the user’s control, preferably offline. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.
Official personnel will not ask for your seed phrase or private key. Treat any page that asks you to paste, upload or send them for “verification,” “airdrops” or “recovery” as high risk.
For Common leak paths, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.
Practical checks
- Verify the network and account before working with common leak paths
- Double-check important addresses, contracts, amounts or permissions
- Never send a seed phrase, private key or verification code to anyone
Recovery & custody
Recovery & custody is a practical part of understanding Seed Phrase & Private Keys. Seed phrases and private keys are core account credentials and should remain under the user’s control, preferably offline. Before acting, confirm that the active account, target network and intended outcome all match, then review the parameters shown in the request.
A seed phrase commonly derives account keys, while a private key directly controls a specific account. Anyone who obtains these credentials may be able to control the corresponding assets.
For Recovery & custody, a repeatable sequence is useful: verify the source and network, check the address or contract, review the amount, permission or fee, and keep a transaction hash when one is created. This does not remove every risk, but it makes decisions easier to explain and problems easier to trace.
Practical checks
- Verify the network and account before working with recovery & custody
- Double-check important addresses, contracts, amounts or permissions
- Never send a seed phrase, private key or verification code to anyone
Security statement
Seed phrases and private keys remain under the user’s control. Official personnel will not ask for them or for verification codes; on-chain transactions generally cannot be reversed by a wallet alone; third-party DApps and smart contracts may carry risk.
imtoken
Ready to get started?
The download entry always goes through the dedicated download page. Keep verifying networks, addresses and request details before acting.