imtoken Knowledge Center
FAQ
Answers to common questions about wallets, networks, transfers, DApps, security, Ethereum, PoS and validators.
On this page
Wallets, Backups and Secret Information
A wallet helps a user control keys and submit on-chain actions, while an exchange account usually sits inside a platform-managed account system. In either case, understand who controls the keys, which network holds the asset and who signs a transfer. Avoid storing a seed phrase in screenshots that may sync to cloud services or become accessible to remote software. Keep recovery material offline and never send it to another person. No. Official staff should not ask for a seed phrase, private key, recovery phrase or verification code. Public information such as a transaction hash, public address and network name is normally enough for basic troubleshooting.
Troubleshooting should always separate public information from secret credentials. Public addresses, network names and transaction hashes can be used to inspect chain state; seed phrases, private keys, recovery phrases and verification codes should not be shared or entered into ordinary websites.
Networks, Gas and Transaction State
The same asset can exist on different networks, and address formats can look similar. Sender and recipient must use a compatible network or the transfer may not arrive as expected. Gas is a way to price the network resources required to process a transaction or contract call. The amount can change with network conditions and transaction complexity. A transaction hash is a public identifier for an on-chain transaction. It can be used in a block explorer to review status, confirmations, sender, recipient and contract interactions.
Check the network, transaction hash and block-explorer status first. Congestion, fee settings and earlier pending transactions can affect confirmation time. Never provide a private key to someone claiming they can speed it up. A confirmed on-chain transaction generally cannot be reversed by the wallet alone. Verify the address, network and amount before sending, then use the transaction hash to confirm what happened.
Web3, Signatures and Approvals
A connection by itself is usually not the same as transferring assets, but later signatures, approvals or transactions can have real effects. Review each request independently. Not exactly. A message signature can prove account control or confirm a protocol request, while a transaction signature submits an on-chain state change. Both still require domain and content checks.
Approvals give a contract permission to use tokens within a defined allowance. Old or unnecessarily broad permissions expand exposure, so unused approvals should be reviewed and revoked when appropriate. Many EVM-compatible networks use the same address format, but they are separate networks with different blocks, fees and contract states. The same-looking address does not move assets across chains automatically. Layer 2 systems usually scale activity while relying on a base chain for parts of security or settlement. Moving assets between layers can involve bridges, waiting periods and additional confirmations.
Ethereum, PoS and Validators
No. Rewards can change and depend on network rules and validator conditions. Participation also involves waiting periods, technical risk, possible penalties and digital-asset price volatility.
Proof-of-stake networks require validators to follow protocol rules. Extended downtime or rule violations can result in penalties, depending on the network. Public networks are harder to trust. For important transfers, wallet recovery, signatures or approvals, prefer a device and network environment that you control.
Security principles
Your seed phrase and private keys are controlled by you. imtoken staff will not ask for your seed phrase, private key or verification code. Review addresses, networks, amounts, signatures and approval scope before acting. Third-party DApps and smart contracts can carry risk, and confirmed on-chain transactions generally cannot be reversed by the wallet alone.