A digital wallet manages account credentials, builds transactions and reads blockchain data. Assets remain recorded on the relevant blockchain rather than inside this website.
Help & Knowledge
Frequently Asked Questions
From key custody and network selection to DApp approvals and PoS risk, these answers focus on verifiable, practical decisions.
Wallets & Keys
A private key directly controls an account, while a seed phrase can often derive one or more account keys. Both are highly sensitive.
That increases exposure. Prefer an offline backup that is protected from loss, photography, fire, water and unauthorized access.
Compatible networks can use the same address format while keeping separate chain state, gas assets, token contracts and transaction history.
Networks & Transactions
Check the network, recipient, token contract and amount, then review gas and the exact signing request.
Gas depends on network fee mechanics, execution resources and congestion, so different actions and times can have different costs.
It is a public identifier used to verify status, block information, gas, sender, recipient and event logs on a block explorer.
Usually not by a wallet provider. Review recipient, network, asset and amount before broadcast.
DApps & Approvals
A normal connection does not need a seed phrase and usually exposes only a public address. Stop if a site asks for private credentials.
No. Message signatures can support login or declarations; transaction signatures can authorize on-chain transactions. Both require context review.
A token approval gives a designated contract permission to spend up to an allowance. It can create risk even if assets do not move immediately.
Not automatically. Session state and on-chain permissions are different; approvals must be reviewed and changed separately.
Layer 2 refers to scaling systems with a defined relationship to mainnet. Cross-layer transfers may involve bridges, confirmations and waiting periods.
Ethereum, PoS & Security
The EVM is a smart-contract execution environment. Compatible networks can share similar patterns while maintaining independent chain state.
No. Rewards change with network conditions, validator performance and protocol rules, and exits may involve waiting.
Validators can face penalties for downtime or protocol violations, in addition to operational, contract and asset-price risk.
Stop further signing, verify the domain and approvals, secure controllable assets if necessary, and preserve transaction evidence.
A public address, transaction hash, network name and error message can help. Never share seed phrases, private keys, verification codes or remote-control access.