Frequently Asked Questions

On-chain assets are recorded by the relevant blockchain network. A wallet primarily manages the keys used to control addresses and reads balances, transactions and contract state from that network.

Both can relate to account control. Derivation details can differ by wallet, but the core rule is the same: never send them to anyone or enter them into an unfamiliar web page.

Screenshots and cloud sync increase the number of digital copies that can be exposed. Prefer an offline backup with controlled access and a durable format you can read when recovery is needed.

Confirm that the wallet environment is trustworthy and understand that importing brings existing recovery material into that environment. Do not submit recovery material to a web page or alleged support agent for “verification.”

Compatible networks can use the same address format, and sometimes the same derived address, while maintaining separate ledgers. Balances, histories and token contracts must therefore be interpreted with network context.

Gas measures computational resources used by on-chain execution. The actual fee also depends on network pricing rules and congestion, and different networks may use different gas assets and mechanisms.

A transaction hash is a public identifier for locating an on-chain transaction. On the correct block explorer it can show status, block height, sender, recipient and confirmation information.

First verify the network and transaction hash, then inspect the corresponding block explorer. Pending status can relate to congestion, fee settings or node synchronization and should not be judged from the wallet display alone.

A wallet generally cannot unilaterally reverse a transaction after it has been broadcast and confirmed. Verify the address, network, asset and amount before sending. Network-specific replacement mechanisms for pending transactions are not a general recovery method.

A basic connection typically exposes the selected account or network context and is not itself a transfer. Later signatures, transactions or approvals can have consequences and should be reviewed individually.

No. Message signatures are often used for login or proof of account control, while transaction signatures submit on-chain actions. Even a message signature should be reviewed for domain, content and authorization meaning.

An allowance defines how much of a token a specified contract can use. Review the spender, token, network and amount, and avoid granting broad long-lived permissions when the purpose is unclear.

Periodically review existing permissions and consider revoking those that are no longer needed. Revocation is normally an on-chain transaction and can require a network fee.

NFT names and images can be copied. On-chain identity normally depends on the network, contract address and token ID. Claiming or trading an NFT can also trigger signatures and contract interactions.

No. imtoken official personnel will not request a seed phrase, private key or verification code. Stop any request that asks for them under the pretext of troubleshooting, unlocking, an airdrop or recovery.

Do not rely only on logos or page appearance. Verify the domain source, navigation path and the request shown by the wallet. Be cautious with pressure tactics, unusual return promises or requests for recovery material.

No return is guaranteed. Protocol rewards can change with network conditions, exits may involve waiting, and validator penalties, smart-contract risk, third-party service risk and asset-price volatility remain relevant.

Validators are expected to perform network duties according to protocol rules. Extended downtime, operational problems or rule violations can reduce rewards, and some behavior can lead to more serious network penalties.