Frequently Asked Questions
Answers about wallets, seed phrases, networks, gas, transaction hashes, DApps, approvals, EVM, Layer 2, Ethereum, PoS and validators.
imtoken helps users organize multi-chain accounts and assets, prepare transfers, review transaction history and connect to DApps after explicit user confirmation. Final transaction state is determined by the relevant blockchain network.
A seed phrase can commonly restore a set of wallet accounts, while a private key provides signing control for a specific account. Both are highly sensitive and should stay offline and undisclosed.
Many EVM-compatible networks use the same address format, but their assets and transaction histories are separate. An address check is incomplete without a network check.
Gas is the network accounting mechanism for the computational resources used by a transaction or contract call. The cost can change with network conditions and the complexity of the action.
A transaction hash is a primary reference for looking up an on-chain transaction on the correct network explorer, including status, block data, fees and failure information.
Once a transaction is confirmed by the network, a wallet generally cannot reverse it unilaterally. Verify address, network and amount before sending.
No. A connection normally creates an interaction session. Token approvals, signatures and transactions are separate requests that should each be reviewed.
A signature may prove a message, authorize an action or be associated with a transaction. Unknown domains, unreadable intent or unusual permissions should not be approved blindly.
A token approval allows a specified contract to use a token within a defined allowance. Verify the target contract and scope, then revisit approvals that are no longer needed.
They share a similar execution and account model, so addresses and tools may look familiar. Assets, fees and transaction records still belong to their individual networks.
Layer 2 systems extend transaction processing while relying on a mainnet relationship for settlement or security assumptions. Moving assets across layers can involve bridges and waiting periods.
Use trusted entry points, verify domains, avoid sensitive links from unsolicited messages, and never provide a seed phrase, private key, verification code or remote-control access to claimed support staff.
Public networks increase uncertainty. Avoid sensitive actions where possible, reject suspicious certificate or remote-control prompts, and wait for a trusted device and network environment for important transfers.
No. Rewards can change with protocol and network conditions, exits can involve waiting, validators can face penalties, and the market value of digital assets can fluctuate.
A validator participates in protocol-defined consensus duties such as proposing or attesting to blocks, subject to uptime requirements and network rules that may include penalties.
Stop repeating the action, save the transaction hash and verify the network, address, amount and contract details. If an approval or device issue is suspected, disconnect unnecessary sessions and review permissions.
Seed phrases and private keys should remain under the user’s control. A request to disclose, upload or hand them to another party should be treated as a serious warning sign. Review the address, network, amount and requested permission before confirming. On-chain actions are generally not reversible by a wallet provider once the network has accepted them.