Frequently Asked Questions

A wallet manages account credentials and helps construct on-chain actions. Asset state is recorded on the relevant blockchain network; the interface reads that state rather than storing the assets inside a web page or app.

No. Seed phrases and private keys should remain under your control and should never be sent to anyone. imtoken personnel will not ask for them or for verification codes.

A private key controls a specific account, while a seed phrase is commonly used to derive one or more accounts. Both are highly sensitive credentials.

Similar address formats can exist on different networks. The asset network, recipient-supported network and the network selected in your wallet need to match.

Gas measures the network resources needed for on-chain execution. The resulting fee depends on network rules, transaction complexity and congestion rather than being a fixed wallet service charge.

A transaction hash is a key reference for checking broadcast, inclusion, confirmations and execution results on the correct block explorer.

First verify the correct network and account, then compare the token contract and explorer balance. An interface display issue should be separated from the actual on-chain state.

A connection generally establishes account access rather than an automatic transfer. However, every later signature, approval or transaction request must still be reviewed independently.

Not exactly. A message signature may confirm identity or intent, while a transaction signature usually authorizes an on-chain state change. Both deserve careful review.

Approvals can remain active and may allow a specified contract to spend tokens within an allowance. Permissions that are no longer needed can be removed to reduce exposure.

No. EVM networks may use the same address format and even the same account address, but each network has independent state and contracts.

Layer 2 systems typically execute some activity away from mainnet and then settle or publish data through a defined mechanism. Bridging can involve separate waiting and confirmation rules.

Check the domain, source and requested action. Stop if someone asks for a seed phrase, private key, verification code, remote access, or an urgent transfer.

No. Rewards can change, exits can involve waiting, validators can face protocol penalties, and smart contracts or third-party services may add risk.

Validators participate in consensus, which can include proposing blocks and submitting attestations. Duties, rewards, penalties and exits are defined by the protocol.

Start with public, verifiable details such as a transaction hash, network name and the sequence of steps. Never share a seed phrase, private key or verification code.