Learn seven core concepts
When working through “Learn seven core concepts”, separate what the interface displays from what the blockchain records. A wallet can organize information, prepare a request and show the result, but the selected network ultimately determines transaction and contract state. For Getting Started, confirm the network, account and destination rather than relying only on familiar buttons or visual cues.
A practical review sequence is source, target, permission and outcome. Identify where the request came from, what address or contract it affects, what authority it is asking for, and what may happen after approval. This turns a vague sense that a request “looks normal” into a set of facts that can be checked before acting.
If the interface does not match expectations, avoid immediately repeating the action. Check the selected network, whether a transaction hash exists, whether an explorer shows the record, and whether the token or contract address matches the intended asset. Confirmation can take time, especially when a network is congested.
Security boundaries remain important throughout Getting Started. imtoken will never ask for a seed phrase, private key or verification code. Do not send those secrets to anyone or enter them into an unfamiliar website. Before a transfer, signature or approval, review the address, network, amount, spender and permission scope. Third-party DApps and smart contracts can introduce risks outside a wallet’s control.
After completing the step, verify the observable result rather than assuming success from a button state. A transaction hash, explorer record, updated network state or changed permission can provide a more reliable confirmation.
Key point
New users do not need to master every blockchain term at once. Begin with wallet, address, seed phrase, private key, network, gas and transaction hash, then practice with small, verifiable steps.
Create and back up offline
A practical review sequence is source, target, permission and outcome. Identify where the request came from, what address or contract it affects, what authority it is asking for, and what may happen after approval. This turns a vague sense that a request “looks normal” into a set of facts that can be checked before acting.
If the interface does not match expectations, avoid immediately repeating the action. Check the selected network, whether a transaction hash exists, whether an explorer shows the record, and whether the token or contract address matches the intended asset. Confirmation can take time, especially when a network is congested.
Security boundaries remain important throughout Getting Started. imtoken will never ask for a seed phrase, private key or verification code. Do not send those secrets to anyone or enter them into an unfamiliar website. Before a transfer, signature or approval, review the address, network, amount, spender and permission scope. Third-party DApps and smart contracts can introduce risks outside a wallet’s control.
When working through “Create and back up offline”, separate what the interface displays from what the blockchain records. A wallet can organize information, prepare a request and show the result, but the selected network ultimately determines transaction and contract state. For Getting Started, confirm the network, account and destination rather than relying only on familiar buttons or visual cues.
After completing the step, verify the observable result rather than assuming success from a button state. A transaction hash, explorer record, updated network state or changed permission can provide a more reliable confirmation.
Key point
New users do not need to master every blockchain term at once. Begin with wallet, address, seed phrase, private key, network, gas and transaction hash, then practice with small, verifiable steps.
Receive and send for the first time
If the interface does not match expectations, avoid immediately repeating the action. Check the selected network, whether a transaction hash exists, whether an explorer shows the record, and whether the token or contract address matches the intended asset. Confirmation can take time, especially when a network is congested.
Security boundaries remain important throughout Getting Started. imtoken will never ask for a seed phrase, private key or verification code. Do not send those secrets to anyone or enter them into an unfamiliar website. Before a transfer, signature or approval, review the address, network, amount, spender and permission scope. Third-party DApps and smart contracts can introduce risks outside a wallet’s control.
When working through “Receive and send for the first time”, separate what the interface displays from what the blockchain records. A wallet can organize information, prepare a request and show the result, but the selected network ultimately determines transaction and contract state. For Getting Started, confirm the network, account and destination rather than relying only on familiar buttons or visual cues.
A practical review sequence is source, target, permission and outcome. Identify where the request came from, what address or contract it affects, what authority it is asking for, and what may happen after approval. This turns a vague sense that a request “looks normal” into a set of facts that can be checked before acting.
After completing the step, verify the observable result rather than assuming success from a button state. A transaction hash, explorer record, updated network state or changed permission can provide a more reliable confirmation.
Key point
New users do not need to master every blockchain term at once. Begin with wallet, address, seed phrase, private key, network, gas and transaction hash, then practice with small, verifiable steps.
Connect to a DApp for the first time
Security boundaries remain important throughout Getting Started. imtoken will never ask for a seed phrase, private key or verification code. Do not send those secrets to anyone or enter them into an unfamiliar website. Before a transfer, signature or approval, review the address, network, amount, spender and permission scope. Third-party DApps and smart contracts can introduce risks outside a wallet’s control.
When working through “Connect to a DApp for the first time”, separate what the interface displays from what the blockchain records. A wallet can organize information, prepare a request and show the result, but the selected network ultimately determines transaction and contract state. For Getting Started, confirm the network, account and destination rather than relying only on familiar buttons or visual cues.
A practical review sequence is source, target, permission and outcome. Identify where the request came from, what address or contract it affects, what authority it is asking for, and what may happen after approval. This turns a vague sense that a request “looks normal” into a set of facts that can be checked before acting.
If the interface does not match expectations, avoid immediately repeating the action. Check the selected network, whether a transaction hash exists, whether an explorer shows the record, and whether the token or contract address matches the intended asset. Confirmation can take time, especially when a network is congested.
After completing the step, verify the observable result rather than assuming success from a button state. A transaction hash, explorer record, updated network state or changed permission can provide a more reliable confirmation.
Key point
New users do not need to master every blockchain term at once. Begin with wallet, address, seed phrase, private key, network, gas and transaction hash, then practice with small, verifiable steps.
Practical checklist
- Verify the domain or source before connecting.
- Confirm the intended network and account.
- Never share a seed phrase, private key or verification code.
- Review amount, gas, signer, spender and permission scope when relevant.
- Use a transaction hash or block explorer to verify on-chain state.