FAQ
Frequently Asked Questions
Answers to common questions about wallets, networks, gas, transaction hashes, DApps, approvals, Layer 2, Ethereum, PoS and validators.
A wallet manages key material and uses network rules to derive or work with addresses. An address identifies an on-chain account; control comes from the corresponding private-key capability.
No. Seed phrases and private keys should remain under your control. imtoken will never ask for a seed phrase, private key or verification code.
Many EVM networks use the same address format, but each network maintains separate state. The same address does not make balances, gas or contracts portable between chains.
Gas represents the computational and block-space cost of executing an on-chain action. Fee assets and pricing rules vary by network, and congestion can change the cost.
A transaction hash identifies a specific on-chain transaction and lets you inspect status, block placement, sender, recipient, value and fees in an explorer.
Check the network and transaction hash first. Confirm whether the transaction succeeded and whether the destination address and token were correct before submitting another transfer.
A connection usually establishes account communication rather than moving assets on its own. Any signature, approval or transaction requested afterward still needs separate review.
Message signatures may prove login or express agreement, while transaction signatures usually authorize an on-chain state change. Both can carry real implications, so read the request details.
The allowance defines how much a contract may use. Broad, long-lived approvals increase exposure, so verify the spender and amount and revisit old permissions.
The EVM is an execution environment for smart contracts. Many chains support it, which creates familiar address and contract patterns, but chain IDs, fee assets and deployments remain separate.
Layer 2 systems extend capacity above a base chain. Moving assets between layers can involve bridges, confirmation windows or exit procedures that depend on the specific system.
Match the receiving platform’s supported network with the wallet’s selected network, destination address and token. Do not rely on similar abbreviations alone.
Do not visit attached websites or approve requests just because an unknown asset appears. Verify the contract and source independently before interacting.
No. Rewards can change, validators can face penalties, exits can involve waiting, and smart contracts and digital-asset prices carry risk.
A validator follows network rules to participate in block proposal, attestation or consensus duties. Uptime, correct behavior and protocol rules affect rewards and penalties.
Use non-secret, verifiable information such as a transaction hash, network, public address, error message and reproducible steps. Never provide a seed phrase, private key or verification code.