FAQ
Answers to common questions about wallets, seed phrases, private keys, networks, gas, DApps, security, Ethereum, PoS and validators.
No. Seed phrases, private keys and recovery phrases should remain under your control and should never be sent to anyone.
A wallet address is a public identifier for an on-chain account. It can receive assets, but the network must still be verified.
Offline storage reduces exposure to screenshots, cloud syncing, malware and compromised online accounts.
Both relate to account control. The exact derivation depends on the wallet, but both should be treated as highly sensitive.
At minimum, verify the recipient address, network, amount and fee, and make sure the recipient supports that network.
Gas costs can change with network demand, transaction complexity and the chain’s fee mechanism.
A transaction hash identifies an on-chain transaction and can be used to check status in the relevant block explorer.
A connection usually exposes a selected public account address to the DApp. It does not automatically approve later transactions.
No. A message signature is not usually broadcast as a transaction, but it can still authorize login or other actions.
A token approval allows a specified spender to use a token within a defined scope or allowance.
An EVM network uses an Ethereum-compatible execution model, commonly involving gas, contract addresses and token standards.
Layer 2 systems can differ in settlement, bridging and exits, so cross-layer actions need network-specific checks.
Inspect the full domain, source, request and signature contents instead of trusting a familiar logo or urgent wording.
Public networks add risk. Important operations are better handled on a trusted device and trusted connection.
No. Rewards can vary, validators can be penalized, exits can take time and asset prices can move.
A validator participates in block proposal and verification under a proof-of-stake network’s rules.
Not necessarily. Exit and withdrawal timing can depend on queues, validator state and protocol rules.
Stop additional actions, verify the transaction hash and approvals, and do not disclose recovery secrets to anyone.
Continue troubleshooting
Start with the issue type, network and transaction state. Never send a seed phrase, private key or verification code.
