FAQ

A wallet manages signing keys and shows the account addresses controlled by those keys. An address can be shared for receiving assets, but seed phrases and private keys should never be sent to anyone.

It is safer not to. Screenshots can be synchronised to cloud storage, device backups, or read by malware. Prefer an offline record stored securely.

A private key typically controls signing for a specific account, while a seed phrase can restore a group of derived accounts. Both are highly sensitive.

Many EVM-compatible networks use similar address formats, but each network has its own chain ID, balances, gas asset, and contract state. Always confirm the network.

Usually no. Gas is the network fee required to execute an on-chain transaction. The wallet helps construct and broadcast the transaction.

A transaction hash identifies an on-chain transaction and can be used in a block explorer to review status, fees, inclusion, and confirmations.

Check the on-chain state using the transaction hash. Congestion and fee settings can affect timing; avoid duplicating the same action simply because an interface is still waiting.

A connection alone normally does not equal an asset transfer, but later signatures, transactions, or approvals can have financial effects. Review each request separately.

No. Some signatures can be used for authentication, permissions, or later actions. Do not sign requests you cannot explain.

A token approval allows a specified contract or address to act on a token up to an allowed amount. Check the spender and limit, and remove permissions that are no longer needed.

It usually grants a very large or effectively uncapped allowance. This can be convenient for repeated use but increases the potential impact if the approved target is compromised.

Not exactly. A Layer 2 has a relationship with its base layer, but network state, fees, bridges, and arrival mechanics can differ.

Check the full domain, source, request details, and contract addresses. Search ranking, advertisements, private messages, and urgency are not proof of legitimacy.

Use caution. Public networks add uncertainty. Important signing and asset operations are better performed on a trusted device and network.

A confirmed on-chain transfer generally cannot be reversed by a wallet provider. Check the address, network, and amount before confirming.

No. Rewards can change, exits can involve waiting periods, validators can face penalties, and contract, service, and asset-price risks remain.

A validator follows protocol rules and participates in block proposals, attestations, or related consensus duties, with rewards and potential penalties tied to network state.

Stop signing further requests, review the spender and allowance, revoke permissions that are no longer needed when possible, and inspect the device, domain, and account activity. Never share your seed phrase or private key.