FAQ
Frequently Asked Questions
Wallet, network, transaction, DApp, security, Ethereum and validator questions answered with practical checks.
No. Seed phrases and private keys remain under user control. Official support should not request them through webpages, chat, email or remote-control sessions.
A seed phrase can commonly derive one or more private keys, while a private key directly signs for a specific account. Both are highly sensitive.
No. The network should be specified as well, because similar address formats can exist across independent networks.
Check the transaction hash on the correct network explorer, then verify confirmation depth and whether the receiving service supports that network.
Gas fees depend on network congestion, fee rules, priority settings and transaction complexity. Different networks use different fee mechanisms.
It is a unique transaction reference that can be used to inspect block inclusion, sender, recipient, fees and execution result.
A normal connection does not require recovery secrets. Stop if a site asks for a seed phrase, private key or verification code.
No. A message may be used for login or may carry broader meaning. Read the wallet-displayed content and verify the source before signing.
It gives a specified contract permission to use a token under certain conditions. Review the spender, allowance and network.
Revocation normally requires a new on-chain transaction on the relevant network. Disconnecting a DApp session does not automatically revoke an on-chain allowance.
Many EVM-compatible chains use the same address format, but their state is separate. The same address string does not make assets cross-chain.
Layer 2 systems execute or aggregate activity outside the base layer and settle or prove results using specific mechanisms. Deposits and withdrawals can require bridges and waiting.
Verify domains, avoid unsolicited support links, resist time pressure, review wallet requests and reject any request for seed phrases or private keys.
Public information can be viewed, but sensitive actions deserve extra caution because hostile or deceptive network conditions can increase risk.
No. Rewards can change, validators can be penalized, exits can take time, and smart contracts or third-party services add risk.
A validator performs consensus duties defined by the protocol, such as attestations or block proposal. Rewards and penalties are protocol-dependent.
Check the network, address, asset, amount and fee. Consider a small test first and confirm the result in an explorer.
Network name, transaction hash, error messages and non-sensitive steps already tried are useful. Do not share seed phrases, private keys or verification codes.