Address
A public identifier used to receive assets and reference an account on-chain.
Blockchain Glossary
Learn common wallet, network, transaction and Web3 terminology with practical security checks and on-chain verification guidance.
Core terms
Seed phrase
Highly sensitive recovery material for a set of wallet keys.
Private key
Secret data used to sign blockchain operations and prove account control.
Gas
A measure of resources consumed by on-chain execution.
Transaction hash
The primary identifier used to look up a transaction on-chain.
Block height
The sequential position of a block in a blockchain.
DApp
An application that interacts with blockchain accounts, contracts or on-chain data.
Approval
Permission for a contract to spend a token within a defined scope.
EVM
The Ethereum Virtual Machine smart-contract execution environment.
Layer 2
A scaling system that processes more activity outside mainnet and settles key data back to it.
Validator
A PoS participant that proposes or attests to blocks.
Bridge
A mechanism for moving assets or messages between networks or layers.
Common mistakes and verification
Common mistakes include using the wrong network, copying a bad address, ignoring token contracts, treating pending transactions as failures, or accepting an unclear approval. Troubleshoot common wallet, network, transaction and Web3 terminology with verifiable data such as transaction hashes, block heights, address history and contract addresses instead of relying only on interface messages.
Common mistakes include using the wrong network, copying a bad address, ignoring token contracts, treating pending transactions as failures, or accepting an unclear approval. Troubleshoot common wallet, network, transaction and Web3 terminology with verifiable data such as transaction hashes, block heights, address history and contract addresses instead of relying only on interface messages.
Security and risk boundary
Seed phrases and private keys should remain under the user’s control. Official support should not request them, and verification codes should never be shared. Third-party DApps, smart contracts and network services can introduce risk. Because confirmed transactions are usually not reversible by the wallet alone, pre-signing checks are essential.
Seed phrases and private keys should remain under the user’s control. Official support should not request them, and verification codes should never be shared. Third-party DApps, smart contracts and network services can introduce risk. Because confirmed transactions are usually not reversible by the wallet alone, pre-signing checks are essential.