FAQ

A wallet primarily manages keys, account information and transaction requests. Asset state is recorded by the relevant blockchain network and can be verified with addresses, transaction hashes and block explorers.

A seed phrase commonly derives a set of keys, while a private key directly provides signing control for a specific account. Both are highly sensitive and should never be sent to another person.

Anyone with valid recovery material may be able to control the related account. A request for a seed phrase, private key or verification code is therefore a strong reason to stop immediately.

Similar address formats can exist on different networks while assets, gas and chain state remain independent. A network mismatch can prevent funds from arriving as expected and make recovery difficult.

Gas measures execution resources on many blockchain networks and is used to calculate transaction fees. Estimates change with network conditions and are not guarantees of final cost or timing.

A transaction hash is an identifier that lets you locate a submitted transaction on its network and inspect pending, successful or failed status together with block confirmations.

Not necessarily. Confirmation may still be pending, the wallet may be showing another network, the token may not yet be displayed, or the interface may not have refreshed. Verify with the transaction hash first.

No. Connection, message signing, transaction signing and token approvals are separate actions. Review the origin, target contract and permission scope for each one.

No. A message signature can still express important permissions or attestations. Gas cost alone does not measure risk; read the request and verify its origin.

Approvals can remain active after an interaction ends. If a DApp or contract no longer needs access, consider revoking the permission and avoid unnecessarily broad allowances.

No. EVM compatibility makes execution models and tooling similar, but chain IDs, fee assets, block state and contract deployments are independent.

Cross-layer movement can involve a source-chain transaction, bridge messaging, destination confirmation or an exit process. Timing depends on the specific network and bridge design.

Check the domain, source, exact request and whether urgency is being manufactured. Fake support, fake airdrops, remote-control requests and requests for recovery secrets are major warning signs.

Risk is higher because shared devices may contain unknown software or residual data, and public networks add exposure. Important wallet actions are better performed on a controlled device and trusted network.

No. Rewards can change with protocol and network conditions, exits may wait, validators can face penalties, and smart contracts, third-party services and asset prices all introduce risk.

A validator follows protocol rules to participate in duties such as attestations and block proposals. Rewards depend on network participation and behavior, and penalties may apply.

Symptoms, network name, public addresses, transaction hashes and contract addresses are normally sufficient starting points. Do not provide a seed phrase, private key or verification code.

Generally no. Recheck the address, network, amount and request before submitting, and use the transaction hash and chain state to decide what to do afterward.