FAQ

A wallet manages accounts and signing requests, while the blockchain network records and validates on-chain state. One wallet can connect to several networks, but each network keeps its own assets, gas model, and transaction history.

A seed phrase commonly restores a set of derived accounts, while a private key directly enables signing for one account. Both are secret recovery material and should remain under the user’s control.

Normal product support and chain troubleshooting can use public information such as an address, network, and transaction hash. They do not require control of the account. Stop any request for a seed phrase, private key, or verification code.

Similar address formats can exist on several networks, but balances and fee rules belong to a specific chain. Sender and recipient should agree on a supported network before transferring.

Gas measures execution resources on many blockchains. The final fee depends on network rules, transaction complexity, and current demand; a fee estimate is not a promise of fixed confirmation time.

A transaction hash is the public identifier of a submitted transaction. A block explorer for the correct network can show sender, recipient, block position, status, and parts of a contract interaction.

Verify the active network and transaction hash, then check whether it is still pending, confirmed, or failed. Avoid blind resubmission because a new submission can become a separate transaction.

No. Connection normally establishes an account session. Message signatures, transaction signatures, and token approvals are separate requests that need their own review.

A message signature can support login or prove account control without immediately changing on-chain state. A transaction signature authorizes a specific on-chain action. Both still require source and content checks.

An approval records an allowance for a spender and may remain active over time. Verify network, token, spender, and allowance before approving, and consider reducing or revoking permissions that are no longer needed.

Many EVM-compatible networks use similar address formats and execution models, but their chain IDs, gas assets, contract deployments, and account state remain independent.

Layer 2 systems increase transaction capacity while maintaining a defined data or settlement relationship with a base layer. Moving assets between layers commonly uses a bridge and can involve different deposit or withdrawal waiting periods.

Use a trusted entry point, verify the full domain, and do not let countdowns, airdrops, or unsolicited support messages shorten your review. Leave any site that asks for a seed phrase or private key.

Public networks and shared devices increase environmental risk. Sensitive actions are better performed on a device and network you control, with current software and no unfamiliar remote-control tools or extensions.

No. Protocol rewards change, exits can wait, validators can face penalties, smart contracts and third-party services add risk, and the market value of digital assets can fluctuate.

Protocols manage validator activation and exit under network rules to preserve consensus stability. The wait depends on current queue conditions and protocol state rather than a fixed timetable.