Crypto terms describe different parts of a system, and their meanings can depend on the protocol, document, or jurisdiction. Treat a technical definition as an explanation of system behavior—not as proof of legal status, financial value, safety, or a guaranteed result. When a term matters to a decision, check the specific network documentation and the context in which it appears.

How to read crypto terminology in context

A glossary gives a starting point, not a universal ruling. Protocol documentation may define a term for a particular network or software design; another project can use the same word for a different mechanism. A legal or financial document may also use familiar words in a specialized way. Check the source’s stated scope, version, and definitions before carrying a meaning from one context into another.

Keep three questions separate: What does the software do? What does a contract or service promise? What legal or financial consequences follow? A technical description alone cannot answer the latter questions. The terms below focus on general technical usage and state limits where the available definition is specific.

Core crypto lingo for networks and protocols

Protocol: The rules that specify how participating software handles network activity. The word can refer to a broad system’s rules or to a narrower set of rules within it, so use the surrounding documentation to identify which.

Network: The connected participants and software operating under a protocol. In Ethereum, nodes use a consensus mechanism to agree on new blocks and the continuing chain. This is an Ethereum-specific description, not a universal account of every network’s design. source

Node: A running instance of protocol client software connected to peers. What a node does depends on its client and configured mode; the word alone does not specify the amount of data it stores or the tasks it performs. source

Consensus: The mechanism a network uses to coordinate agreement on its history or state. The term does not mean that every system uses the same rules, participants, or approach. For Ethereum, consensus is used to agree on new blocks and the continuing chain. source

Blockchain: In everyday technical writing, this generally refers to an ordered record of blocks. The label does not by itself tell you who can participate, how agreement is reached, what data is available, or what governance applies. Those properties must be checked for the specific system.

Layer 1 (L1) and Layer 2 (L2): These labels describe relationships between a base network and systems that build on it, but their use is not fully uniform. In one established rollup terminology, a rollup uses a base layer for consensus and data availability, while systems that publish data elsewhere add external data-availability assumptions and are classified differently. Check the architecture rather than relying on an L1 or L2 label alone. source

Terms for transactions, blocks, and fees

Transaction: A signed instruction submitted to a network. What it can do and which fields it contains depend on the network and transaction type. The word does not mean the instruction has already been accepted or completed.

Block: A unit of network history containing or organizing activity according to that protocol’s rules. The term’s precise structure and role are network-specific.

Confirmation: A common informal label for a transaction’s inclusion in a block or for subsequent network progress that provides additional evidence of inclusion. Its exact meaning and any application’s acceptance threshold depend on the network and service. Do not treat the word alone as a guarantee of irreversibility or fulfillment.

Transaction fee: A charge associated with submitting or processing a transaction under a particular network or service’s rules. Fee names and calculations vary. For example, an ordinary Ethereum-family token transfer requires the sender to use the recipient’s network and hold enough native ETH to cover the transaction fee, unless a supported sponsored-fee mechanism applies. That is an Ethereum-family example, not a rule for all networks. source

A fee estimate, quoted charge, or label in a wallet is not a universal price. Check the network and transaction details shown by the relevant application. This glossary does not establish a fee amount, processing time, or completion outcome.

Wallet, key, and custody vocabulary

Wallet: In technical usage, software or a device that helps manage the keys used to access or authorize activity associated with blockchain addresses. The word can also refer to a product that bundles other functions, so check what a particular wallet application actually does.

Address: An identifier used by a network or application for directing activity. An address is not the same thing as a person’s identity, and its format and role vary across systems.

Public key and private key: A public key can be shared for cryptographic operations; a private key is secret material used for authorization in systems that rely on key pairs. Do not assume that seeing an address or public key reveals who controls it.

Custody: A description of who controls or safeguards access to keys or assets in a particular arrangement. The term does not, by itself, establish the user’s legal rights, recovery options, or protections. Those depend on the actual service, agreement, and applicable context.

These words describe different things: an address identifies a destination or account in a system; a key supports cryptographic control; and a wallet is a tool or service that interacts with keys. Their use does not establish a security guarantee or a recovery method.

Tokens, smart contracts, and protocol-specific terms

Token: A digital unit represented or managed under a network’s rules or an application’s code. The term is broad; it does not alone establish a token’s rights, backing, value, or legal classification. Specific token standards and categories require their own definitions, so this glossary does not treat them as interchangeable.

Smart contract: Software deployed to a blockchain address that executes according to its code and network rules. What a contract can do depends on its implementation and the inputs or transactions it receives. Calling something a smart contract does not prove that its code is correct or that a related product promise is enforceable.

ERC: A label associated with Ethereum standards and proposals. Its presence signals a standards-related context, but it does not describe a token’s rights or capabilities on its own. For a particular ERC number, consult the standard and the contract’s implementation rather than inferring details from the acronym.

Rollup: A system that separates transaction execution from a base layer while posting data to Ethereum, where base-layer consensus establishes the published record. Rollups differ in proof system, data format, sequencing, upgrade, and bridge design; the label is not a complete description of those choices. source

When a crypto term needs more than a glossary definition

Legal, tax, regulatory, and compliance terms depend on jurisdiction and circumstances. A technical label does not settle those questions. If a document uses one of these terms to describe obligations or rights, identify the jurisdiction and the specific authoritative source before drawing a conclusion. A glossary should not substitute for qualified advice on an individual matter.

The same caution applies to claims about security, recovery, availability, fees, and yields. These are not merely vocabulary questions: each needs current evidence tied to the relevant system, product, version, and operating conditions. A term such as “secure,” “recoverable,” or “available” is not a guarantee by itself.

For practical interpretation, record the exact term, where it appears, and which network or product it concerns. Then check that system’s documentation for its definition and limitations. If the term is being used to support a legal, financial, or operational decision, seek the applicable primary source or an appropriately qualified adviser rather than treating a general glossary entry as a conclusion.

Sources and references