Still unsure about a transaction?
Prepare the transaction hash, network name and relevant address, then verify them on the correct block explorer. Never send a seed phrase or private key.
Go to Support →Help Center
FAQ
Answers to common questions about wallets, networks, gas, DApps, approvals, security, Ethereum, PoS and validators.
Wallets and keys
Start by understanding the boundary around sensitive wallet information.
A seed phrase is commonly used to restore wallet control. Keep it under your own custody, preferably offline, and never enter it into an unfamiliar website or send it to another person.
A private key typically controls a specific account, while a seed phrase can derive multiple accounts. Both are highly sensitive and can grant control over assets.
The same asset name can exist on different networks. Sender and recipient should agree on the same network before a transfer.
Gas is the network-fee mechanism for consuming blockchain resources. Fee models, fee assets and congestion differ by network.
Networks and transactions
Investigate transaction issues through network, gas, transaction hashes and block explorers.
A transaction hash is a unique identifier that can be checked on the correct block explorer for status, blocks, addresses and contract calls.
Confirm the network and transaction hash, then check the relevant block explorer. Congestion, fee settings or node synchronization may affect how quickly an interface updates.
No. A connection usually creates an account interaction channel. Signatures, transactions and token approvals still require separate review.
No. Some signatures are simple login proofs, while others can authorize actions or affect assets. Review the source, content and request type.
Web3, signatures and approvals
A connection is not an approval; review each signature, transaction and allowance independently.
A token approval lets a contract use an asset within a specified allowance. Verify the spender, amount and purpose before approving.
Review permissions using a trusted approval-management interface or explorer and consider revoking unnecessary allowances on the correct network.
Many EVM networks use the same address format, but assets and contracts are deployed independently. Matching addresses do not mean matching networks.
Layer 2 systems usually depend on a base layer for part of their security or settlement while processing more activity elsewhere. Cross-layer transfers can have separate steps and waiting periods.
Security, Ethereum and PoS
Security habits and PoS risk awareness require ongoing attention rather than guarantees.
Use trusted entry points, verify domains, avoid entering sensitive information through unknown links, reject suspicious remote-control requests and review every signature or approval.
Ethereum uses proof of stake, with validators participating in block proposals and attestations. Participation, rewards and penalties follow network rules.
No. Rewards can change, exits may take time, validators can face penalties and digital-asset prices can fluctuate.
Risks include reduced rewards from downtime, protocol penalties, service-provider or smart-contract risk, and market-price volatility.
Continue learning
The Academy covers wallets, networks, DApps, approvals and security in separate learning paths.
Open Academy →