FAQ
Answers to common questions about wallets, networks, DApps, security, Ethereum and PoS.
Questions and answers
Browse answers across wallets, networks, Web3, security and PoS.
A wallet manages keys, addresses and transaction signing; the asset records themselves live on blockchain networks.
No. Legitimate support should never ask for a seed phrase, private key or verification code.
Do not rely on any provider to recover a private key. Recovery material should be backed up securely by the user.
Review the address, network, asset and amount, and understand gas and contract details.
On networks that use gas, it represents the resource cost required to execute transactions or contracts.
It can be used to inspect transaction status and confirmations in the relevant block explorer.
No. Connection only establishes a session; every signature, approval and transaction still needs review.
No. Message signatures usually do not directly submit an on-chain transaction, but they can still carry important permissions or intent.
An approval grants a contract permission to use tokens within a specified scope.
They often share similar address and contract models, while network state, gas assets and parameters can still differ.
Layer 2 systems usually depend on a base chain for part of their security or settlement, and cross-layer transfers need careful review.
Verify domains, avoid unknown links and never enter a seed phrase or private key into a website.
Use caution and prefer trusted devices and networks for sensitive or high-value actions.
No. Rewards may change and depend on protocol rules, validator status and other factors.
Yes. Depending on the PoS rules, downtime or protocol violations may lead to penalties.
Not necessarily. Exit and withdrawal timing can depend on network conditions, queues and protocol rules.