Verify the network before sending
Similar address formats do not prove that two assets are on the same chain. Match the sender, receiver, token and target network before signing.
Home / Updates
UpdatesProduct, network and security updates
Product, network, security and service notices from the imtoken knowledge center.
Keep the transaction hash after a transfer
The transaction hash is the most useful public reference for checking whether a transaction is pending, confirmed or failed on the intended network.
Review approvals you no longer need
A past token approval can remain valid after a DApp session ends. Check the spender and scope, and remove permissions that no longer serve a purpose.
Treat Layer 2 withdrawals as a dedicated flow
Cross-layer movement can involve bridges, proof periods, queues or separate confirmation stages. Do not evaluate it like a normal same-chain transfer.
Understand staking conditions before participating
Rewards may change, exits can take time, validators can be penalized and smart contracts can introduce technical risk. Participation should fit your own circumstances.
Content first, without invented dates or claims
Notices focus on verifiable product behavior, network concepts, security checks and service limitations. They do not invent partnerships, financing, licenses, user counts, trading volume or market rankings.
Keep checking the source
A notice can explain what to check, but the final network or transaction state should still be verified against the relevant on-chain information.
imtoken
Download imtoken