Frequently Asked Questions

A digital wallet manages access to blockchain accounts controlled by keys and helps users view addresses, assets, transactions, and signing requests. The blockchain network remains the source of record for on-chain state.

A seed phrase can usually restore a group of derived accounts, while a private key directly controls a specific account. Both are highly sensitive and should remain under the user’s custody.

The same asset name can exist on multiple networks, and some networks use similar address formats. Checking the address together with the network reduces the chance of sending into the wrong chain context.

Gas measures the network resources used by a transaction or smart-contract execution. Fees vary with network conditions and the complexity of the requested action.

A transaction hash is the on-chain reference for a transaction. It can be used in a block explorer to check block inclusion, execution status, gas use, and confirmation progress.

A connection normally establishes an account context, but later signatures, transactions, or approvals can request more authority. Every later request should be reviewed independently.

No. A message signature can authenticate an account or prove agreement to a statement even when it does not cost gas. Unexpected signature requests should be verified before approval.

A token approval lets a specified spender contract act on tokens within an allowance. The spender, token, allowance, and purpose should all be checked before approval.

Many EVM-compatible networks use similar address formats while maintaining separate chain state. The same address does not make assets automatically shared between those networks.

Layer 2 systems increase scalability by handling parts of execution or data flow away from the base layer while retaining a settlement or security relationship. Bridge and exit mechanics vary by system.

Keep it offline where possible and control who can physically access the backup. Avoid screenshots, chat messages, routine cloud sync, and any website or support conversation that asks you to type it in.

Do not send a seed phrase, private key, or verification code and do not install remote-control software for a stranger. Preserve the suspicious account or domain and then review device and approval security.

Ethereum uses Proof of Stake consensus in which validators perform protocol duties. Rewards depend on protocol parameters, network conditions, and validator performance and are not fixed guarantees.

Validators are expected to perform protocol duties correctly. Downtime, misconfiguration, or certain conflicting behavior can reduce rewards or trigger protocol penalties.

Not necessarily. Exit and withdrawal timing can be affected by protocol queues, validator state, and service workflow, so waiting periods should be understood in advance.

A block explorer can usually show addresses, transaction hashes, blocks, contracts, and events, making it useful for comparing a wallet interface with public on-chain state.

No. imtoken will never ask for a seed phrase, private key, or verification code. Requests for those secrets as part of account verification or recovery should be treated as dangerous.

A wallet generally cannot unilaterally reverse a confirmed on-chain transaction. That is why reviewing the address, network, amount, and action before sending is so important.