Step-by-step Guide
Getting Started
A practical imtoken guide to getting started, 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
When using imtoken for Getting Started, 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 understanding wallets, first define its role in the current task, then check whether creating a wallet and backing up a seed phrase are consistent. When receiving assets is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For connecting to DApps, 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: understanding wallets
- Cross-check: creating a wallet and backing up a seed phrase
- Review carefully: receiving assets
- Verify afterward: connecting to DApps
- 02
Checks before you act
From a risk perspective, receiving assets and connecting to DApps 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 backing up a seed phrase and receiving assets are consistent. When connecting to DApps is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For understanding wallets, 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: backing up a seed phrase and receiving assets
- Review carefully: connecting to DApps
- Verify afterward: understanding wallets
- 03
How to evaluate a live request
After a Getting Started task is completed, review understanding wallets 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 backing up a seed phrase, first define its role in the current task, then check whether receiving assets and connecting to DApps are consistent. When understanding wallets 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: backing up a seed phrase
- Cross-check: receiving assets and connecting to DApps
- Review carefully: understanding wallets
- Verify afterward: creating a wallet
- 04
Risks and boundaries
To understand Getting Started, treat receiving assets and connecting to DApps 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 receiving assets, first define its role in the current task, then check whether connecting to DApps and understanding wallets 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 backing up a 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: receiving assets
- Cross-check: connecting to DApps and understanding wallets
- Review carefully: creating a wallet
- Verify afterward: backing up a seed phrase
- 05
How to verify the outcome
connecting to DApps rarely appears in isolation. It often intersects with understanding wallets 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 connecting to DApps, first define its role in the current task, then check whether understanding wallets and creating a wallet are consistent. When backing up a seed phrase is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For receiving assets, 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: connecting to DApps
- Cross-check: understanding wallets and creating a wallet
- Review carefully: backing up a seed phrase
- Verify afterward: receiving assets
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.