FAQ

A wallet manages keys and signing capability associated with addresses. The interface can display assets, while the authoritative state is recorded on the relevant blockchain network.

A private key is used for signing. A seed phrase can be used to recover one or more keys. Both are highly sensitive and should remain offline and under your control.

No. Stop any flow that asks for a seed phrase, private key, recovery phrase or verification code and verify the source again.

Confirm the receiving address, asset and network, and make sure the sender uses the same network. Assets with similar names can exist on different networks.

Review the address, network, amount, gas and purpose. A smaller test can help validate an unfamiliar route.

Gas is a way to price computation and storage resources on-chain. Fee models and market conditions differ by network.

A transaction hash identifies an on-chain transaction and can be used with a block explorer to verify broadcast, inclusion and confirmation status.

Network congestion, fee settings, transaction ordering or network-specific mechanics can all contribute. Check the hash and network state before retrying.

A connection only opens an interaction channel. You still need to review the domain, account request, signatures, approvals and transactions.

A message signature can authenticate identity or grant permission. Even when no gas is required, the request can still carry security consequences.

It gives a contract defined permission to use a token. Review the target, allowance and purpose, and consider revoking access that is no longer needed.

Many EVM networks use the same account-address format, but chain IDs, gas, assets and transaction histories remain separate.

Layer 2 systems extend mainnet using different technologies. Moving assets can involve bridges, confirmations and exits with different waiting periods.

No. Security depends on key custody, device state, network choices, signing decisions and third-party contracts, among other factors.

No. Rewards can change with validator state, protocol rules and market conditions.

Yes. Validators that fail to follow protocol rules may face network penalties, depending on the protocol.

Not necessarily. Exits and withdrawals can involve queues or waiting periods depending on network state and the service path.

Stop signing and approving, do not enter a seed phrase or private key, verify the domain and download source, and review existing approvals for possible revocation.