Digital Wallet FAQ

A wallet address is a public identifier used to receive on-chain assets. Before sending, verify the network, asset and full address rather than relying only on a few visible characters.

Both can represent control over wallet accounts. A seed phrase commonly derives or restores accounts, while a private key usually signs for a specific account. Neither should be sent to another person.

It is safer not to. Screenshots, photo sync and cloud storage increase exposure. Prefer an offline backup that is stored securely and separately from everyday connected devices.

Many EVM-compatible networks use the same address format, but their assets and network states are separate. Always verify the network, chain parameters and token contract.

Gas measures the computational resources needed for an on-chain operation. Fees depend on network rules and congestion, so wallet estimates can change as network conditions change.

A transaction hash is a unique identifier that can be checked on a suitable block explorer to review status, block inclusion, confirmations and interaction details.

Once an on-chain transaction is confirmed, a wallet generally cannot reverse it unilaterally. Recovery options depend on the recipient, network and asset, making pre-transfer checks essential.

No. A wallet connection normally establishes account access. Signatures, token approvals and transactions are separate requests and should each be reviewed independently.

A message signature does not always transfer assets directly, but some signatures can be used for login, authorization or protocol actions. Review the origin, content and purpose before signing.

A token approval grants a contract permission to use a token allowance. Check the spender, amount and purpose, and consider revoking permissions that are no longer required.

Verify the domain source, contract address, network, requested permissions and redirect path. Be cautious of urgency, seed phrase requests, remote-control requests or unknown links.

No. EVM compatibility describes execution and tooling compatibility, not identical gas assets, chain parameters, bridge mechanisms, risk or ecosystem behavior.

Some Layer 2 systems use bridges or cross-layer mechanisms to move assets between layers. Timing, confirmation rules, fees and risk depend on the specific network and bridge design.

No. Rewards can change, exits can involve waiting periods, validators can face protocol penalties, smart contracts have technical risks and digital asset prices can fluctuate.

A validator participates in protocol duties such as proposing or attesting to blocks, depending on the network. Status, rewards and penalties are defined by the protocol.

Do not provide it. imtoken official staff will not ask for a seed phrase, private key or verification code. Stop the interaction and return to a trusted official entry point.

Use caution. Public networks and shared computers increase exposure to interception, hijacking and malware. Sensitive operations are better performed on a trusted device and network.

Use a trusted approval-management method for the relevant network, check spenders and allowances, and revoke permissions that are no longer needed or are broader than necessary.