On this page
Core concepts
From a risk perspective, gas and smart contracts 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 EVM, first define its role in the current task, then check whether addresses and gas are consistent. When smart contracts is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For token approvals, 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: EVM
- Cross-check: addresses and gas
- Review carefully: smart contracts
- Verify afterward: token approvals
Checks before you act
After a EVM Networks task is completed, review token approvals and EVM 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 addresses, first define its role in the current task, then check whether gas and smart contracts are consistent. When token approvals is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For EVM, 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: addresses
- Cross-check: gas and smart contracts
- Review carefully: token approvals
- Verify afterward: EVM
How to evaluate a live request
To understand EVM Networks, treat gas and smart contracts 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 gas, first define its role in the current task, then check whether smart contracts and token approvals are consistent. When EVM is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For addresses, 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: gas
- Cross-check: smart contracts and token approvals
- Review carefully: EVM
- Verify afterward: addresses
Risks and boundaries
smart contracts rarely appears in isolation. It often intersects with token approvals and EVM. 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 smart contracts, first define its role in the current task, then check whether token approvals and EVM are consistent. When addresses is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For gas, 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: smart contracts
- Cross-check: token approvals and EVM
- Review carefully: addresses
- Verify afterward: gas
How to verify the outcome
When using imtoken for EVM Networks, 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 token approvals, first define its role in the current task, then check whether EVM and addresses are consistent. When gas is involved, do not rely only on a default option; understand which account, asset or permission it may affect. For smart contracts, 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: token approvals
- Cross-check: EVM and addresses
- Review carefully: gas
- Verify afterward: smart contracts
Practical checklist
- 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.