FAQ

A digital wallet manages addresses, signing capability associated with private keys, and views of on-chain assets. The assets themselves are recorded on blockchain networks; the wallet helps you view them and submit signed actions.

A seed phrase can typically restore control of a wallet. Anyone who obtains it may gain control over the related assets, so it should be stored offline and never uploaded to an unfamiliar site or sent to another person.

No. imtoken staff will never ask for a private key, seed phrase or verification code. Stop immediately if anyone requests these details and verify the source independently.

Before sending or receiving, compare the network supported by the asset, the network specified by the counterparty, and the network currently selected in the wallet. Similar-looking addresses can exist on separate networks.

Check the destination address, network, asset, amount and estimated network fee. For a large transfer, a smaller test transaction can reduce the impact of an input mistake.

Gas measures the computation and storage resources required for on-chain execution. The fee can vary with network congestion, transaction complexity and the fee model used by the network.

A transaction hash is a unique identifier for an on-chain transaction. It can be used in a block explorer for the relevant network to review status, block height, addresses, amounts and execution results.

Not necessarily. A wallet connection generally creates an account session. Signatures, token approvals and on-chain transactions are separate requests and should be reviewed independently.

Verify the domain, purpose, active account and network, then read the visible request details. Reject requests that are unclear or come from a source you cannot verify.

Some contracts request permission to use a specific amount of a token. Broader and longer-lived permissions can create a larger potential impact, so approvals should match the actual need and be reviewed later.

EVM networks can share a similar smart-contract execution model and address experience, while maintaining separate chain state, gas assets and network parameters. The network must be checked explicitly.

Layer 2 systems process some activity outside the base chain and maintain a defined relationship with it. Cross-layer transfers may involve bridges, waiting periods and different confirmation logic.

Use trusted entry points, check domain spelling, reject unsolicited remote-control requests, never enter a seed phrase or private key, and review signatures, approvals and transfers as separate actions.

No. Rewards can change with network rules, validator status and participation method. Asset-price volatility, network penalties, exit queues and smart-contract risk can also affect outcomes.

Validators participate in consensus activities such as proposing or attesting to blocks. They must operate correctly and follow protocol rules; prolonged downtime or improper behavior can have network-level consequences.

Usually not. Once a transaction is confirmed by the network, the wallet cannot unilaterally reverse it. That is why verifying the address, network and amount before sending is critical.