Verify contract addresses
When thinking about verify contract addresses, separate the network, address, signature and transaction state. A wallet interface helps organize information, but the authoritative asset state is recorded by the relevant blockchain. Before acting, confirm that the selected network matches the asset and destination, and do not rely on names or icons alone to identify a token.
Security principle
In real use, verify contract addresses often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
Unexpected request
When thinking about unexpected request, separate the network, address, signature and transaction state. A wallet interface helps organize information, but the authoritative asset state is recorded by the relevant blockchain. Before acting, confirm that the selected network matches the asset and destination, and do not rely on names or icons alone to identify a token.
Permission mismatch
When thinking about permission mismatch, separate the network, address, signature and transaction state. A wallet interface helps organize information, but the authoritative asset state is recorded by the relevant blockchain. Before acting, confirm that the selected network matches the asset and destination, and do not rely on names or icons alone to identify a token.
Untrusted environment
When thinking about untrusted environment, separate the network, address, signature and transaction state. A wallet interface helps organize information, but the authoritative asset state is recorded by the relevant blockchain. Before acting, confirm that the selected network matches the asset and destination, and do not rely on names or icons alone to identify a token.
Method calls and transaction requests
In real use, method calls and transaction requests often appears together with gas, confirmations, transaction hashes or contract permissions. A safer sequence is to identify the target first, read the request second, and only then sign or broadcast. A website that asks for a seed phrase, private key or verification code should not be trusted as part of a normal wallet action.
Security principle
If the result does not match your expectation, avoid repeating the same action immediately. Save the transaction hash and inspect it on a block explorer for the correct network to see whether it was broadcast, succeeded and reached confirmation. On-chain transactions are usually not something a wallet can unilaterally reverse, so checks before action matter more than recovery promises after the fact.
Signatures versus approvals
If the result does not match your expectation, avoid repeating the same action immediately. Save the transaction hash and inspect it on a block explorer for the correct network to see whether it was broadcast, succeeded and reached confirmation. On-chain transactions are usually not something a wallet can unilaterally reverse, so checks before action matter more than recovery promises after the fact.
Security principle
For Smart Contract Interaction, it is useful to distinguish the wallet, the blockchain network and any third-party DApp. A contract can introduce code, permission and operational risks. imtoken staff will never ask for a seed phrase or private key and should not be treated as an entity that can recover those credentials for the user.
Unexpected request
If the result does not match your expectation, avoid repeating the same action immediately. Save the transaction hash and inspect it on a block explorer for the correct network to see whether it was broadcast, succeeded and reached confirmation. On-chain transactions are usually not something a wallet can unilaterally reverse, so checks before action matter more than recovery promises after the fact.
Permission mismatch
If the result does not match your expectation, avoid repeating the same action immediately. Save the transaction hash and inspect it on a block explorer for the correct network to see whether it was broadcast, succeeded and reached confirmation. On-chain transactions are usually not something a wallet can unilaterally reverse, so checks before action matter more than recovery promises after the fact.
Untrusted environment
If the result does not match your expectation, avoid repeating the same action immediately. Save the transaction hash and inspect it on a block explorer for the correct network to see whether it was broadcast, succeeded and reached confirmation. On-chain transactions are usually not something a wallet can unilaterally reverse, so checks before action matter more than recovery promises after the fact.
Gas and failure risk
For Smart Contract Interaction, it is useful to distinguish the wallet, the blockchain network and any third-party DApp. A contract can introduce code, permission and operational risks. imtoken staff will never ask for a seed phrase or private key and should not be treated as an entity that can recover those credentials for the user.
Security principle
Long-term habits are more useful than memorizing a button. For gas and failure risk, consistently review the address, network, amount or requested permission, and check whether old connections or approvals are still needed. Shared computers, remote-control sessions and untrusted network environments deserve extra caution.
Principles for spotting suspicious contracts
Long-term habits are more useful than memorizing a button. For principles for spotting suspicious contracts, consistently review the address, network, amount or requested permission, and check whether old connections or approvals are still needed. Shared computers, remote-control sessions and untrusted network environments deserve extra caution.
Security principle
The purpose of this material is not to promise returns or absolute safety. It is to make each on-chain action easier to reason about. Signing, approving, bridging or using validator-related services can involve network conditions, contract risk, waiting periods and market volatility, so participation should always be an independent decision.
Unexpected request
Long-term habits are more useful than memorizing a button. For unexpected request, consistently review the address, network, amount or requested permission, and check whether old connections or approvals are still needed. Shared computers, remote-control sessions and untrusted network environments deserve extra caution.
Permission mismatch
Long-term habits are more useful than memorizing a button. For permission mismatch, consistently review the address, network, amount or requested permission, and check whether old connections or approvals are still needed. Shared computers, remote-control sessions and untrusted network environments deserve extra caution.
Untrusted environment
Long-term habits are more useful than memorizing a button. For untrusted environment, consistently review the address, network, amount or requested permission, and check whether old connections or approvals are still needed. Shared computers, remote-control sessions and untrusted network environments deserve extra caution.
Permission review after interaction
The purpose of this material is not to promise returns or absolute safety. It is to make each on-chain action easier to reason about. Signing, approving, bridging or using validator-related services can involve network conditions, contract risk, waiting periods and market volatility, so participation should always be an independent decision.
Security principle
When thinking about permission review after interaction, separate the network, address, signature and transaction state. A wallet interface helps organize information, but the authoritative asset state is recorded by the relevant blockchain. Before acting, confirm that the selected network matches the asset and destination, and do not rely on names or icons alone to identify a token.
Keep your seed phrase and private keys offline where practical, never send them to another person, check address/network/amount before transfer, and inspect each signature or approval request independently.