Control & accounts

Addresses are public, while seed phrases and private keys are control credentials. Start by separating information that can be public from secrets that must never be shared.

AddressPublic information used to identify an on-chain account and receive assets; it is not a private key.
Seed phraseSensitive recovery information that can restore wallet control and should be kept offline.
Private keyA secret credential used to authorize signatures for a specific account.
GasThe fee mechanism that pays for network execution of transactions or contract calls.
Transaction hashThe public identifier used to locate a specific on-chain transaction.
BlockA unit that groups transactions and state updates in a blockchain.
ConfirmationProgress recorded after a transaction enters a block and the network continues advancing.
EVMA smart-contract execution environment used by many compatible networks.
Smart contractOn-chain code that executes predefined logic when called by transactions.
TokenA transferable digital asset represented by a blockchain or smart contract.
ApprovalAn on-chain permission allowing a spender to use a token within an allowance.
DAppAn application that uses blockchain networks and smart contracts for functionality.
Layer 2A scaling system that processes activity away from mainnet while maintaining a design-specific settlement or security relationship.
BridgeA protocol or contract system used to move assets or messages across networks or layers.
PoSA consensus approach where staked value and validators participate in securing the network.
ValidatorA node role that performs consensus duties in a proof-of-stake network.

How to use terms in real decisions

For a transaction issue, work through the network, address, gas, transaction hash, block and confirmations. For a DApp request, add signatures, contracts and approvals. The point of terminology is to describe what is happening accurately.

Protocol details can differ

The same term can have implementation differences across networks and protocols, including confirmation speed, bridge exits, PoS penalties and approval interfaces. Review the specific network or protocol rules before important actions.

Security boundaries remain consistent

Regardless of network or protocol, never share seed phrases, private keys or verification codes. Check address, network and amount before sending, and review origin, contract and permission scope before signing or approving.