FAQ

A digital wallet manages blockchain addresses, keys and signing operations. Assets are recorded on their respective networks rather than stored inside a phone application.

A seed phrase commonly derives and restores a group of wallet keys, while a private key directly controls signing for a specific address. Both must remain private.

No. imtoken will not ask for a seed phrase, private key or verification code, and support should not use remote control to obtain them.

Some EVM-compatible networks use the same address format, but they remain separate chains with their own gas, contracts and transaction state.

At minimum, verify the destination address, network, asset or token contract, amount and required gas. Some services may also require a memo or tag.

A transaction hash is a key identifier for locating an on-chain transaction in the appropriate block explorer and checking its status and confirmations.

Gas cost depends on network rules, transaction complexity and current demand, so the effective fee can vary by action and by time.

Rules vary by network. On many networks, a failed transaction can still consume fees for computation that was attempted, so review the transaction details.

A connection usually allows the DApp to request account and network information. It does not make later requests trustworthy and does not automatically move assets.

Not exactly. A message signature may not create an on-chain transaction but can still prove identity or grant authority; a transaction signature submits a state change.

A token approval gives a specified spender permission to use a token up to an allowance. Review the spender, amount and intended purpose before approving.

Review existing permissions through a trusted method and consider revoking those you no longer need. Revocation itself may require an on-chain transaction.

EVM refers to the Ethereum Virtual Machine execution model. Many compatible networks share address and contract conventions while still having distinct network parameters and assets.

Layer 2 is a separate execution or scaling environment. Wallets generally switch to it explicitly, and cross-layer transfers can involve bridges and distinct confirmation paths.

No. Rewards can change with protocol and network conditions, exits can involve waiting, validators can be penalized, and asset prices can fluctuate.

Validators must meet protocol requirements. Downtime or improper behavior can reduce rewards or trigger penalties, while services and smart contracts add technical risk.

Stop signing or approving, do not enter a seed phrase or private key, close the page, and return through a known trusted entry point. Review permissions if you already approved something.

Interface caching, node delays or viewing the wrong network can cause differences. The correct network’s on-chain record should be the primary reference.