FAQ

A digital wallet manages blockchain accounts, addresses and signing authority. Assets are recorded on their respective networks; the wallet helps you view state and prepare signatures or transactions.

A seed phrase can restore a wallet's account structure, while a private key controls signing for a specific account. Both are highly sensitive and should remain offline and private.

If you have no other valid backup, a wallet generally cannot recreate your seed phrase or private key for you. A tested offline backup should be created when the wallet is set up.

Similar address formats can exist across multiple networks, but the asset network and the recipient's supported network must match. A network mismatch can make recovery difficult or impossible.

Gas is the network fee mechanism used to execute transactions and smart contract operations. Cost varies with network rules, transaction complexity and congestion.

A transaction hash is an identifier that can be used in a blockchain explorer to inspect status, block inclusion, sender, recipient and related contract information.

Check the active network, save the transaction hash and inspect the explorer status before submitting the same action again. Handling differs by network and by the current on-chain state.

A connection commonly lets a DApp identify an account address, but it is not blanket approval for later signatures, transfers or token permissions. Review each request independently.

No. Message signatures may be used for login or address ownership proofs, while transaction signatures can change on-chain state. Some signatures can also be tied to permissions, so inspect the request carefully.

A token approval grants a specified contract permission to use tokens within a defined allowance. Verify the spender, scope and whether the permission is actually necessary.

Old permissions expand the attack surface. Revoking an unnecessary approval can remove a contract's continued ability to use tokens under that allowance.

An EVM network uses an Ethereum Virtual Machine compatible execution environment. Networks may share account and contract concepts while maintaining separate assets, fees and security states.

Layer 2 systems process some activity outside the base layer and settle or synchronize through a specific mechanism. Moving assets across layers can require extra steps and waiting periods.

Check the exact domain, spelling, page behavior and whether it asks for a seed phrase or private key. Be cautious with countdowns, impersonated support and reward claims that push immediate action.

Public networks can increase exposure to malicious hotspots and interception attempts. Prefer trusted networks for sensitive actions and verify that the device and browser environment are secure.

No. Rewards can change with network conditions and protocol rules, validators can face penalties, exits can involve waiting, and smart-contract and asset-price risks remain.

Validators participate in consensus activities such as block proposals and attestations according to protocol rules. Availability and correct operation matter, and penalties can apply.

Stop making further signatures, approvals or transfers, preserve transaction hashes and relevant on-chain information, and inspect permissions and device security. Never send recovery secrets to someone claiming to be support.