Frequently Asked Questions

The wallet is an interface for reading chain state and signing actions; balances are recorded by the relevant blockchain network. If the display looks wrong, verify the correct network and public on-chain data.

A seed phrase can commonly derive multiple account keys, while a private key directly controls signatures for a specific account. Both are highly sensitive and should never be shared.

No. imtoken will not request a seed phrase, private key or verification code. Troubleshooting can use public information such as the network, public address and transaction hash.

Networks maintain separate ledgers. Similar address formats do not move assets between chains, so sender and recipient must agree on a compatible network.

Gas is the mechanism used to pay for network execution. It normally uses the network’s native asset, and cost varies with demand and transaction complexity.

A transaction hash is the public identifier used to locate a transaction and inspect pending, success or failed status, block inclusion, confirmations, fees and addresses.

A confirmed on-chain transaction generally cannot be reversed unilaterally by a wallet provider. Network-specific handling of pending transactions varies, which makes pre-send checks important.

A connection usually exposes an approved public account and lets the DApp request later actions. Signatures, transactions and approvals still require review, although malicious sites can try to mislead users.

No. A message signature can prove account control or consent, while a transaction signature authorizes an on-chain action. Both require source and content review.

A token approval lets a designated spender use a token within an allowance. Review the spender, amount and purpose, and consider revoking permissions you no longer need.

Usually not. Session disconnection and on-chain token approvals are separate. Revoking an allowance requires a separate on-chain action and network gas.

Many EVM-compatible networks use similar address formats, but the networks, gas assets, contracts and transaction states remain separate.

Layer 2 systems process activity away from mainnet and settle or inherit security through design-specific mechanisms. Moving assets across layers often uses a bridge and can involve waiting periods.

Check the full domain rather than the logo, and be cautious with ads, unsolicited messages, fake support, airdrops and urgent signature prompts. Any site asking for a seed phrase is high risk.

Public networks increase environmental uncertainty. Important signing, imports and large transfers are better handled on a trusted personal device and controlled network.

No. Rewards change with protocol and network conditions, exits can take time, validators can face penalties, and contract, service and asset-price risks remain.

Validators must follow protocol rules and remain correctly available. Penalties for downtime, conflicting signatures or other behavior vary by network.

Confirm the active network, public address, transaction hash and token contract, then check the public balance and transaction result before repeating any transfer.