Appendix A: Glossary of Blockchain and Cryptocurrency Terms

This glossary provides concise definitions of key terms used throughout the textbook. Each entry includes a cross-reference to the chapter where the term is first introduced or most thoroughly discussed. Terms in bold within a definition indicate other glossary entries.

A

51% Attack — An attack in which a single entity or colluding group controls more than half of a blockchain network's mining or staking power, enabling them to double-spend coins, reverse transactions, or prevent new transactions from confirming. The economic cost of sustaining such an attack on major networks makes it impractical but not impossible. (Ch. 5)

ABI (Application Binary Interface) — A JSON specification that describes the functions, events, and data structures of a smart contract, enabling external applications to encode function calls and decode return values. The ABI acts as the contract's public interface and is required for any off-chain code interacting with deployed contracts. (Ch. 13)

Account Abstraction — A design paradigm that replaces the rigid externally owned account (EOA) model with programmable smart contract wallets, enabling features like social recovery, gas sponsorship, and batched transactions. ERC-4337 is the most widely adopted standard for account abstraction on Ethereum. (Ch. 37)

Address — A unique identifier derived from a public key (or contract deployment) that serves as a destination for cryptocurrency transactions. Bitcoin addresses are Base58Check or Bech32 encoded, while Ethereum addresses are 20-byte hex strings prefixed with 0x. (Ch. 3)

Airdrop — A distribution of tokens to wallet addresses, typically used for community building, protocol governance distribution, or marketing. Airdrops may be unconditional or require users to have met certain on-chain activity criteria (retroactive airdrops). (Ch. 24)

AMM (Automated Market Maker) — A decentralized exchange mechanism that uses mathematical formulas (most commonly the constant product formula x * y = k) to price assets in liquidity pools, replacing the traditional order book model. Uniswap, Curve, and Balancer are prominent AMM implementations. (Ch. 19)

Atomic Swap — A cryptographic technique enabling the trustless exchange of one cryptocurrency for another across different blockchains without an intermediary, typically using Hash Time-Locked Contracts (HTLCs). If either party fails to complete their side, the swap expires and funds are returned. (Ch. 17)

Attestation — In Proof of Stake systems, a validator's signed vote affirming a specific block as valid and canonical. In Ethereum's Beacon Chain, attestations are aggregated into committees to finalize blocks efficiently. (Ch. 10)

B

Base Fee — In Ethereum's EIP-1559 fee model, the algorithmically determined minimum gas price that adjusts up or down based on network congestion. The base fee is burned (destroyed) rather than paid to validators, creating a deflationary mechanism for ETH. (Ch. 11)

Beacon Chain — The Proof of Stake coordination layer of Ethereum, launched in December 2020 and merged with the execution layer in September 2022 (The Merge). The Beacon Chain manages the validator registry, assigns attestation duties, and finalizes blocks. (Ch. 10)

BIP (Bitcoin Improvement Proposal) — A formal design document for proposing changes to the Bitcoin protocol, analogous to Python's PEPs or Internet RFCs. BIPs follow a numbered system and progress through Draft, Proposed, and Final stages. (Ch. 8)

Block — A data structure containing a batch of validated transactions, a reference (hash) to the previous block, a timestamp, and consensus metadata. Blocks are the fundamental unit of a blockchain's append-only ledger. (Ch. 2)

Block Explorer — A web application that provides a searchable interface into blockchain data, allowing users to look up transactions, addresses, blocks, and contract interactions. Etherscan (Ethereum) and Mempool.space (Bitcoin) are widely used explorers. (Ch. 6)

Block Height — The sequential number of a block in the chain, with the genesis block at height 0. Block height is used to reference specific points in the blockchain's history and to calculate confirmation depth. (Ch. 2)

Block Reward — The newly minted cryptocurrency awarded to the miner or validator who successfully proposes a new block. Bitcoin's block reward halves approximately every four years (the halving); Ethereum eliminated block rewards for miners at The Merge. (Ch. 5)

Blockchain — A distributed, append-only data structure in which blocks of transactions are cryptographically linked in sequence, creating a tamper-evident ledger maintained by a decentralized network of nodes. The term encompasses both the data structure and the peer-to-peer network that maintains it. (Ch. 1)

Blockchain Trilemma — The observation, attributed to Vitalik Buterin, that blockchain systems face inherent trade-offs among three properties: decentralization, security, and scalability. Most designs optimize for two at the expense of the third. (Ch. 16)

Bridge — A protocol enabling the transfer of assets or data between two separate blockchain networks. Bridges may be trusted (relying on a multisig or centralized custodian), trustless (using cryptographic proofs), or optimistic (using fraud proofs with a challenge period). (Ch. 17)

Burn — The permanent removal of tokens from circulation, typically by sending them to an address with no known private key or by executing a contract function that decrements supply. Token burns create deflationary pressure. (Ch. 24)

Byzantine Fault Tolerance (BFT) — The property of a distributed system that can continue to operate correctly even when some participants (up to one-third in classical BFT) behave maliciously or fail arbitrarily. BFT is the theoretical foundation for blockchain consensus mechanisms. (Ch. 4)

Bytecode — The low-level machine-readable instruction set that a smart contract compiles to and that the EVM executes. Solidity and Vyper source code compile to EVM bytecode before deployment. (Ch. 12)

C

Cold Storage — The practice of keeping private keys entirely offline (on hardware wallets, paper, or air-gapped computers) to minimize exposure to network-based attacks. Cold storage is recommended for long-term holdings that do not require frequent transactions. (Ch. 7)

Composability — The ability of smart contracts and protocols to interact with and build upon each other without permission, often described as "money Legos" in DeFi. Composability enables complex financial products to be assembled from simpler building blocks. (Ch. 19)

Confirmation — The number of blocks that have been added to the chain after the block containing a specific transaction. More confirmations provide higher assurance that a transaction is irreversible; Bitcoin convention typically requires 6 confirmations for high-value transfers. (Ch. 6)

Consensus Mechanism — The algorithm by which a decentralized network agrees on the current state of the ledger and the validity of new blocks. Major mechanisms include Proof of Work, Proof of Stake, Delegated Proof of Stake, and Practical Byzantine Fault Tolerance. (Ch. 4)

Custodial — A service model in which a third party (exchange, bank, institution) holds and manages private keys on behalf of the user. Custodial solutions sacrifice self-sovereignty for convenience and regulatory compliance. Contrasted with non-custodial or self-custodial. (Ch. 7)

D

DAO (Decentralized Autonomous Organization) — An organization governed by smart contract rules and token-holder votes rather than centralized management. DAOs manage treasuries, protocol parameters, and strategic decisions through on-chain governance proposals. (Ch. 25)

dApp (Decentralized Application) — An application with its backend logic implemented as smart contracts on a blockchain, typically paired with a traditional web frontend. dApps interact with the blockchain through RPC calls and wallet connections. (Ch. 13)

DeFi (Decentralized Finance) — The ecosystem of financial services (lending, borrowing, trading, insurance, derivatives) built on public blockchains using smart contracts, operating without traditional intermediaries like banks or brokerages. (Ch. 19)

Deterministic Wallet — A wallet that derives all key pairs from a single master seed using a hierarchical derivation scheme (typically BIP-32/BIP-44). This enables backup of an unlimited number of addresses with a single mnemonic phrase. (Ch. 7)

Difficulty — In Proof of Work systems, a network-wide parameter that determines how computationally hard it is to find a valid block hash. Bitcoin adjusts difficulty every 2,016 blocks (approximately two weeks) to maintain a target block time of 10 minutes. (Ch. 5)

Double Spend — The attempted use of the same digital funds in two or more transactions. Blockchain consensus mechanisms exist primarily to solve the double-spend problem without requiring a trusted central authority. (Ch. 1)

E

EIP (Ethereum Improvement Proposal) — A formal document proposing changes to the Ethereum protocol, standards, or conventions. EIPs are categorized as Standards Track (Core, Networking, Interface, ERC), Meta, or Informational. (Ch. 11)

Elliptic Curve Cryptography (ECC) — A family of public-key cryptographic algorithms based on the algebraic structure of elliptic curves over finite fields. Bitcoin and Ethereum both use the secp256k1 curve for key generation and digital signatures. (Ch. 3)

ENS (Ethereum Name Service) — A decentralized naming system on Ethereum that maps human-readable names (e.g., vitalik.eth) to machine-readable addresses, content hashes, and metadata. ENS names are NFTs that can be transferred and traded. (Ch. 23)

ERC (Ethereum Request for Comments) — A category of EIP that defines application-level standards and conventions. Notable ERCs include ERC-20 (fungible tokens), ERC-721 (NFTs), ERC-1155 (multi-token), and ERC-4626 (tokenized vaults). (Ch. 22)

ERC-20 — The standard interface for fungible tokens on Ethereum, defining functions for transfer, approval, balance queries, and total supply. ERC-20 compatibility is required for tokens to be listed on decentralized exchanges and used in DeFi protocols. (Ch. 22)

ERC-721 — The standard interface for non-fungible tokens (NFTs) on Ethereum, where each token has a unique ID and distinct ownership. ERC-721 defines functions for transfer, approval, and metadata URI retrieval. (Ch. 23)

EVM (Ethereum Virtual Machine) — The stack-based, quasi-Turing-complete virtual machine that executes smart contract bytecode on every Ethereum node. The EVM's deterministic execution model ensures all nodes reach identical state after processing the same transactions. (Ch. 11)

F

Faucet — A web service that distributes small amounts of testnet cryptocurrency for free, enabling developers to test smart contracts and transactions without spending real funds. Sepolia and Holesky are the primary Ethereum testnets with active faucets. (Ch. 13)

Finality — The guarantee that a confirmed transaction cannot be reversed, altered, or removed from the blockchain. Probabilistic finality (Bitcoin) increases with each confirmation; absolute finality (Casper FFG) is achieved when two-thirds of validators attest. (Ch. 4)

Flash Loan — An uncollateralized loan that must be borrowed and repaid within a single atomic transaction. If the borrower cannot repay, the entire transaction reverts as if it never occurred. Flash loans enable arbitrage, liquidations, and collateral swaps. (Ch. 20)

Fork — A divergence in the blockchain, which may be temporary (two miners finding blocks simultaneously) or intentional. Hard forks introduce backward-incompatible rule changes (e.g., Ethereum Classic split); soft forks tighten existing rules in a backward-compatible way (e.g., SegWit). (Ch. 8)

Frontrunning — The practice of observing a pending transaction in the mempool and submitting a competing transaction with a higher gas price to be executed first, profiting from the price impact of the victim's trade. Frontrunning is a key component of MEV. (Ch. 21)

Full Node — A network participant that downloads, validates, and stores the complete blockchain, independently verifying every block and transaction against consensus rules. Full nodes provide the strongest security guarantees and contribute to network decentralization. (Ch. 6)

G

Gas — The unit measuring computational effort required to execute operations on Ethereum. Each EVM opcode has a fixed gas cost; users set a gas limit and gas price for transactions. Gas prevents infinite loops and allocates scarce computational resources. (Ch. 11)

Gas Limit — The maximum amount of gas a user is willing to spend on a transaction. If execution exceeds the gas limit, the transaction reverts but the gas is still consumed. Block gas limits cap the total computation per block. (Ch. 11)

Genesis Block — The first block in a blockchain (block height 0), which is hardcoded into the protocol software rather than mined or validated through normal consensus. Bitcoin's genesis block, mined on January 3, 2009, contains a famous newspaper headline. (Ch. 2)

Governance Token — A token that grants holders the right to vote on protocol decisions, parameter changes, and treasury allocation. Governance tokens (e.g., UNI, AAVE, COMP) are the primary coordination mechanism for DAOs. (Ch. 25)

H

Halving — The periodic reduction (by half) of Bitcoin's block reward, occurring every 210,000 blocks (approximately four years). Halvings enforce Bitcoin's fixed supply schedule of 21 million coins and are significant events in market cycles. (Ch. 8)

Hard Fork — A protocol upgrade that introduces backward-incompatible changes, requiring all nodes to upgrade. Nodes that do not upgrade will follow the old chain, potentially creating a permanent chain split (as occurred with Ethereum/Ethereum Classic in 2016). (Ch. 8)

Hash Function — A deterministic mathematical function that maps input data of arbitrary size to a fixed-size output (digest), designed to be fast to compute, infeasible to reverse, and collision-resistant. SHA-256 (Bitcoin) and Keccak-256 (Ethereum) are the primary hash functions in blockchain. (Ch. 3)

Hash Rate — The total computational power devoted to mining on a Proof of Work network, measured in hashes per second. Bitcoin's hash rate is typically measured in exahashes per second (EH/s). Higher hash rate generally indicates greater network security. (Ch. 5)

HTLC (Hash Time-Locked Contract) — A conditional payment that requires the recipient to provide a cryptographic proof (preimage) before a deadline, or the funds return to the sender. HTLCs are the foundation of the Lightning Network and atomic swaps. (Ch. 9)

Hot Wallet — A cryptocurrency wallet connected to the internet, offering convenience for frequent transactions at the cost of increased attack surface. Exchange wallets and mobile wallets are common hot wallet examples. (Ch. 7)

I

Immutability — The property that data, once written to the blockchain and sufficiently confirmed, cannot be altered or deleted. Immutability derives from cryptographic linking of blocks and the economic cost of rewriting chain history. (Ch. 2)

Impermanent Loss — The difference in value between providing liquidity to an AMM pool and simply holding the same assets. Impermanent loss occurs when the price ratio of pooled tokens changes from the ratio at deposit; it becomes permanent if the provider withdraws at the altered ratio. (Ch. 19)

Interoperability — The ability of different blockchain networks to communicate, share data, and transfer assets between each other. Interoperability solutions include bridges, relay chains (Polkadot), IBC protocol (Cosmos), and cross-chain messaging layers. (Ch. 17)

IPFS (InterPlanetary File System) — A distributed, peer-to-peer file storage network that addresses content by its cryptographic hash rather than by server location. IPFS is widely used to store NFT metadata and other data too large for on-chain storage. (Ch. 23)

K

KYC (Know Your Customer) — Regulatory requirements that financial institutions verify the identity of their customers. Centralized cryptocurrency exchanges must implement KYC procedures, while DeFi protocols generally operate without KYC, creating regulatory tension. (Ch. 29)

L

Layer 1 (L1) — The base blockchain network (e.g., Bitcoin, Ethereum, Solana) that provides consensus, security, and data availability. Layer 1 scalability improvements involve changes to the base protocol itself (larger blocks, shorter block times, sharding). (Ch. 16)

Layer 2 (L2) — A scaling solution built on top of a Layer 1 blockchain that processes transactions off-chain while inheriting the security guarantees of the underlying chain. Major L2 categories include rollups (optimistic and zk), state channels, and plasma. (Ch. 16)

Light Client — A network node that downloads only block headers rather than full blocks, verifying transactions using Merkle proofs provided by full nodes. Light clients sacrifice independent verification for dramatically lower storage and bandwidth requirements. (Ch. 6)

Lightning Network — A Layer 2 payment channel network for Bitcoin that enables near-instant, low-fee transactions by conducting most activity off-chain and only settling to the Bitcoin blockchain when channels are opened or closed. (Ch. 9)

Liquidity Mining — The practice of incentivizing users to provide liquidity to DeFi protocols by distributing governance or reward tokens. Liquidity mining (also called yield farming) was pioneered by Compound's COMP distribution in 2020. (Ch. 20)

Liquidity Pool — A smart contract holding reserves of two or more tokens that enables decentralized trading through an AMM formula. Liquidity providers deposit tokens in balanced ratios and earn a share of trading fees. (Ch. 19)

M

Mainnet — The primary, production blockchain network where real economic value is transacted. Deploying to mainnet (as opposed to a testnet) involves real cryptocurrency and carries genuine financial risk. (Ch. 13)

Maximal Extractable Value (MEV) — The profit a block producer can extract by including, excluding, or reordering transactions within a block. MEV encompasses frontrunning, sandwich attacks, liquidation capture, and arbitrage. Flashbots and PBS (proposer-builder separation) aim to mitigate MEV's harmful effects. (Ch. 21)

Mempool — The set of valid, unconfirmed transactions waiting to be included in a block. Each node maintains its own mempool; miners/validators select transactions from the mempool, typically prioritizing those with higher fees. (Ch. 6)

Merkle Root — The single hash at the top of a Merkle tree that cryptographically summarizes all transactions in a block. Changing any transaction would change the Merkle root, making tampering detectable. (Ch. 2)

Merkle Tree — A binary tree data structure where each leaf node is the hash of a data block (transaction) and each non-leaf node is the hash of its children. Merkle trees enable efficient and secure verification of large data sets, providing O(log n) inclusion proofs. (Ch. 2)

Mining — The process of expending computational resources to find a valid Proof of Work nonce, thereby proposing a new block to the network. Miners are incentivized by block rewards and transaction fees. (Ch. 5)

Mining Pool — A group of miners who combine their hash power and share block rewards proportionally. Mining pools reduce reward variance for individual miners but introduce a degree of centralization. (Ch. 5)

Mnemonic Phrase (Seed Phrase) — A human-readable sequence of 12 or 24 words (from the BIP-39 word list) that encodes the master seed for a deterministic wallet. The mnemonic phrase is the ultimate backup for all keys derived from that wallet. (Ch. 7)

Multi-signature (Multisig) — A wallet or transaction scheme requiring M-of-N private keys to authorize a transaction (e.g., 2-of-3). Multisig provides enhanced security for treasuries, joint accounts, and organizational funds. (Ch. 7)

N

NFT (Non-Fungible Token) — A unique digital token (typically ERC-721 or ERC-1155) representing ownership of a distinct asset, whether digital art, music, virtual land, or other collectibles. Unlike fungible tokens, each NFT has unique properties and is not interchangeable. (Ch. 23)

Node — A computer running blockchain software that participates in the peer-to-peer network. Nodes may be full nodes (storing and validating the entire chain), light clients, archive nodes (storing all historical states), or validator nodes. (Ch. 6)

Nonce — In Proof of Work, the variable that miners iterate to find a block hash below the difficulty target. In Ethereum accounts, a sequential counter tracking the number of transactions sent from an address, preventing replay attacks. (Ch. 5, Ch. 11)

Non-custodial — A wallet or service model where the user retains sole control of their private keys. Non-custodial wallets embody the principle of self-sovereignty but place full responsibility on the user for key management. (Ch. 7)

O

Opcode — A single instruction in the EVM instruction set (e.g., ADD, SSTORE, CALL). Each opcode has an associated gas cost reflecting its computational or storage expense. The EVM has approximately 140 opcodes. (Ch. 11)

Oracle — A service that provides external (off-chain) data to smart contracts, which cannot natively access information outside the blockchain. Chainlink is the dominant decentralized oracle network; the oracle problem (ensuring data integrity) remains a core challenge. (Ch. 20)

Optimistic Rollup — A Layer 2 scaling solution that executes transactions off-chain and posts transaction data to Layer 1, assuming all transactions are valid unless challenged. A challenge period (typically 7 days) allows anyone to submit a fraud proof to dispute invalid state transitions. Arbitrum and Optimism (OP Mainnet) are major optimistic rollups. (Ch. 16)

P

Peer-to-Peer (P2P) Network — A distributed network architecture where participants communicate directly with each other without a central server. Blockchain nodes form P2P networks to propagate transactions and blocks. (Ch. 6)

Plasma — An early Layer 2 framework proposed by Vitalik Buterin and Joseph Poon that uses child chains anchored to the main chain via periodic commitments. Plasma has largely been superseded by rollups due to data availability challenges. (Ch. 16)

Private Key — A secret 256-bit number that proves ownership of a blockchain address and authorizes transactions. The private key must never be shared; anyone who possesses it has full control over the associated funds. (Ch. 3)

Proof of Stake (PoS) — A consensus mechanism in which validators lock (stake) cryptocurrency as collateral and are selected to propose blocks proportionally to their stake. Validators who behave dishonestly risk having their stake slashed. Ethereum transitioned to PoS in September 2022. (Ch. 10)

Proof of Work (PoW) — A consensus mechanism requiring miners to solve a computationally intensive puzzle (finding a hash below a target value) to propose blocks. PoW provides Sybil resistance at the cost of significant energy consumption. Bitcoin uses PoW. (Ch. 5)

Protocol — The set of rules governing how a blockchain network operates, including consensus rules, transaction formats, networking protocols, and economic parameters. Protocol changes require community consensus and are implemented through forks or upgrades. (Ch. 4)

Proxy Pattern — A smart contract architecture where a lightweight proxy contract delegates all function calls to an implementation contract, enabling upgradability while preserving the contract's address and storage. The Transparent Proxy and UUPS patterns are most common. (Ch. 14)

Public Key — A point on an elliptic curve derived from the private key through one-way multiplication. The public key is used to verify digital signatures and (after hashing) to derive the blockchain address. (Ch. 3)

R

Reentrancy — A smart contract vulnerability where an external call allows the called contract to re-enter the calling function before its state is updated, potentially draining funds. The 2016 DAO hack exploited reentrancy. The Checks-Effects-Interactions pattern prevents it. (Ch. 14)

Rollup — A Layer 2 scaling technique that executes transactions off-chain, compresses the results, and posts the data back to Layer 1 for security. The two types are optimistic rollups (fraud proofs) and ZK rollups (validity proofs). (Ch. 16)

RPC (Remote Procedure Call) — The communication protocol used by applications to interact with blockchain nodes. Bitcoin Core uses JSON-RPC; Ethereum uses JSON-RPC over HTTP, WebSocket, or IPC. Providers like Infura and Alchemy offer hosted RPC endpoints. (Ch. 6)

S

Sandwich Attack — An MEV extraction technique where an attacker places a buy order before and a sell order after a victim's large swap transaction, profiting from the price impact. Sandwich attacks are a common form of frontrunning in DEXs. (Ch. 21)

Scalability — The ability of a blockchain to handle increasing transaction throughput without degrading performance, decentralization, or security. Scalability solutions span Layer 1 improvements and Layer 2 architectures. (Ch. 16)

secp256k1 — The specific elliptic curve used by both Bitcoin and Ethereum for public-key cryptography. The curve parameters were defined by the Standards for Efficient Cryptography Group (SECG). (Ch. 3)

SHA-256 — The Secure Hash Algorithm producing a 256-bit (32-byte) digest, used extensively in Bitcoin for block hashing, transaction hashing, and Merkle tree construction. SHA-256 is a member of the SHA-2 family designed by the NSA. (Ch. 3)

Sharding — A database partitioning technique adapted for blockchains, where the network is divided into subsets (shards) that process transactions in parallel. Ethereum's roadmap includes danksharding for data availability scaling. (Ch. 16)

Slashing — The penalty imposed on Proof of Stake validators who violate protocol rules (e.g., double-signing or prolonged downtime). Slashed validators lose a portion of their staked collateral, providing economic disincentive against misbehavior. (Ch. 10)

Slippage — The difference between the expected price of a trade and the price at which it actually executes, caused by low liquidity or price movement between submission and execution. AMM users set slippage tolerances to limit unfavorable execution. (Ch. 19)

Smart Contract — Self-executing code deployed on a blockchain that automatically enforces the terms of an agreement when predefined conditions are met. Smart contracts are immutable once deployed (unless using a proxy pattern) and execute deterministically across all nodes. (Ch. 12)

Soft Fork — A protocol upgrade that tightens consensus rules in a backward-compatible manner, so non-upgraded nodes still accept new blocks as valid. SegWit and Taproot were implemented as Bitcoin soft forks. (Ch. 8)

Solidity — The primary high-level programming language for writing smart contracts on Ethereum and EVM-compatible chains. Solidity is statically typed, supports inheritance, and compiles to EVM bytecode. (Ch. 12)

Stablecoin — A cryptocurrency designed to maintain a stable value relative to a reference asset (usually USD). Mechanisms include fiat-backed reserves (USDC, USDT), crypto-collateralized (DAI), and algorithmic designs. Stablecoins are foundational to DeFi. (Ch. 22)

Staking — The act of locking cryptocurrency in a smart contract to participate in Proof of Stake consensus, earning rewards for validating blocks. Staking can be direct (running a validator) or delegated (through a staking pool or liquid staking protocol). (Ch. 10)

State Channel — A Layer 2 technique where participants conduct transactions off-chain between themselves, only interacting with the base chain to open and close the channel. The Lightning Network is the most prominent state channel implementation. (Ch. 9)

T

Testnet — A separate blockchain network with identical protocol rules but no real economic value, used for testing smart contracts and applications. Ethereum's primary testnets are Sepolia (permissioned PoS) and Holesky (large validator set). (Ch. 13)

Token — A digital asset created and managed by a smart contract on an existing blockchain (as opposed to a coin, which is native to its own blockchain). Tokens follow standards like ERC-20 (fungible) and ERC-721 (non-fungible). (Ch. 22)

Tokenomics — The economic design of a token including supply schedule, distribution, utility, governance rights, and incentive mechanisms. Sound tokenomics align participant incentives with protocol health. (Ch. 24)

Total Value Locked (TVL) — The aggregate value of crypto assets deposited in DeFi protocols, measured in USD. TVL is a widely cited metric for DeFi adoption but can be inflated by leverage, double-counting, or artificial incentives. (Ch. 19)

Transaction — A cryptographically signed instruction submitted to the blockchain, such as a value transfer, smart contract deployment, or function call. Transactions include sender, recipient, value, data payload, gas parameters, and a digital signature. (Ch. 2)

Transaction Fee — The amount paid by the transaction sender to compensate block producers for including and processing the transaction. Fee models vary: Bitcoin uses a fee market based on transaction size (vbytes); Ethereum uses gas with base fee plus priority fee. (Ch. 6)

Trustless — A property of systems that do not require participants to trust any single party, instead relying on cryptographic proofs, economic incentives, and consensus mechanisms. "Trustless" means trust is distributed, not eliminated. (Ch. 1)

U

UTXO (Unspent Transaction Output) — Bitcoin's accounting model, where each transaction consumes previous outputs and creates new ones. A user's balance is the sum of all UTXOs they can spend. Contrasted with Ethereum's account-based model. (Ch. 6)

V

Validator — A participant in a Proof of Stake network who locks collateral and is responsible for proposing blocks and attesting to their validity. Ethereum requires 32 ETH to run a solo validator. (Ch. 10)

Vault — In DeFi, a smart contract that implements automated yield strategies on deposited assets. ERC-4626 standardizes the tokenized vault interface for composability across protocols. (Ch. 20)

Vyper — A Pythonic smart contract language for the EVM, designed as a more secure alternative to Solidity with intentionally limited features (no inheritance, no operator overloading) to reduce attack surface. (Ch. 12)

W

Wallet — Software or hardware that manages private keys and enables users to sign transactions and interact with blockchain networks. Wallets may be hot (internet-connected), cold (offline), custodial, or non-custodial. (Ch. 7)

Web3 — A term describing the vision of a decentralized internet built on blockchain technology, where users own their data, identity, and digital assets. Web3 encompasses DeFi, NFTs, DAOs, and decentralized social media. (Ch. 38)

Wei — The smallest denomination of ETH, equal to 10^-18 ETH. Gas prices and smart contract calculations typically operate in wei to avoid floating-point arithmetic. 1 Gwei = 10^9 wei; 1 ETH = 10^18 wei. (Ch. 11)

Whale — A market participant holding a sufficiently large amount of a cryptocurrency to influence its price through large trades. Whale wallet tracking is a common on-chain analysis technique. (Ch. 33)

Wrapped Token — A token on one blockchain that represents an asset from another blockchain or protocol, pegged 1:1 to the underlying asset. Wrapped Bitcoin (WBTC) is an ERC-20 token backed by Bitcoin held in custody. (Ch. 22)

Y

Yield Farming — The practice of moving capital across DeFi protocols to maximize returns from interest, fees, and token rewards. Yield farmers often pursue complex, multi-protocol strategies to compound yields. See also liquidity mining. (Ch. 20)

Z

Zero-Knowledge Proof (ZKP) — A cryptographic method by which one party (the prover) can demonstrate knowledge of a secret to another party (the verifier) without revealing the secret itself. ZKPs enable privacy-preserving transactions and scalable rollups. (Ch. 18)

ZK-Rollup — A Layer 2 scaling solution that executes transactions off-chain and posts a compact validity proof (a zero-knowledge proof) to Layer 1, proving correct execution without requiring a challenge period. ZK-rollups offer faster finality than optimistic rollups but are more complex to build. zkSync and StarkNet are prominent ZK-rollups. (Ch. 16)

ZK-SNARK — Zero-Knowledge Succinct Non-Interactive Argument of Knowledge: a type of zero-knowledge proof that is small in size and quick to verify, but requires a trusted setup ceremony. Used in Zcash and some ZK-rollups. (Ch. 18)

ZK-STARK — Zero-Knowledge Scalable Transparent Argument of Knowledge: a type of zero-knowledge proof that requires no trusted setup and is resistant to quantum computing attacks, but produces larger proofs than SNARKs. Used by StarkNet and StarkEx. (Ch. 18)