Frequently Asked Questions

A digital wallet helps manage blockchain accounts and signing actions. Assets are recorded on the relevant blockchain; the wallet helps you view addresses, create transactions and review requests before signing.

Both are highly sensitive recovery information. A seed phrase can derive multiple accounts, while a private key controls a specific account. Anyone who obtains them may be able to control associated assets, so keep them offline and private.

Many EVM networks use compatible address formats, but balances and transactions remain separate on each network. A matching address does not make networks interchangeable.

Gas measures blockchain computation and resource use. The final fee can vary with network conditions, transaction complexity and fee settings. A higher fee is not a guarantee of safety.

A transaction hash is a public identifier for a broadcast transaction. Use it with a block explorer to check inclusion, status, block height and other on-chain details.

Network congestion, fee settings, propagation or chain conditions can affect confirmation. Check the transaction hash first and avoid blindly sending the same transaction again.

Not necessarily. Account connection, message signing, transaction signing and token approvals are different actions. Review each request separately.

A token approval allows a specified contract or address to spend within a defined allowance. Review the spender, contract and amount, and consider revoking approvals you no longer need.

No. A signature may prove account control, confirm a message or participate in a more complex transaction. Check the origin, domain, content and expected outcome first.

Layer 2 systems generally expand transaction processing above a base network and use specific mechanisms to settle or synchronize state. Cross-layer transfers can require additional waiting.

Different Layer 2 designs use different settlement, batching and exit mechanics. The required waiting period depends on the actual network rules.

Use trusted entry points, check the full domain and avoid connecting a wallet from unsolicited messages. Stop immediately if a site asks for a seed phrase, private key or verification code.

Public networks add risks such as rogue hotspots and device exposure. For important transfers or signatures, prefer a device and network you control.

Most confirmed blockchain transactions cannot be reversed unilaterally by a wallet. Check the address, network and amount before sending, and consider a small test transfer when appropriate.

No. Rewards can change with protocol and network conditions, validators can be penalized, exits may require waiting, and digital asset prices can fluctuate.

Validators can experience downtime, configuration problems or network penalties. Depending on the setup, smart contract and third-party service risks may also apply.

Shareable information can include the network name, public address, transaction hash, approximate time and visible error message. Never provide a seed phrase, private key, recovery phrase or verification code.

No. Seed phrases and private keys should remain under the user’s control. Treat any request claiming to be support and asking for them as high risk.