Glossary

Common blockchain and distributed ledger terms, written for public-sector leaders, program managers, and policy staff. Where relevant, notes highlight government-specific considerations.

Core Concepts

Blockchain: An append-only data structure in which records ("blocks") are cryptographically chained together. Once written, data is extremely difficult to alter, providing a tamper-evident audit trail.; Gov consideration: Immutability can conflict with data-correction mandates (e.g., Privacy Act amendments). Agencies should evaluate whether corrective mechanisms exist in a given implementation.
Distributed Ledger Technology (DLT): A broader category of databases replicated across multiple nodes without a single administrator. Blockchains are one type of DLT, but not all DLTs use blocks or chains.
Node: A computer that maintains a copy of the ledger and participates in validating transactions. More nodes generally means greater resilience and decentralization.
Consensus Mechanism: The protocol by which nodes agree on the current state of the ledger. Common mechanisms include Proof of Work, Proof of Stake, and Byzantine Fault Tolerance variants.; Gov consideration: Energy-intensive mechanisms (e.g., Proof of Work) may conflict with federal sustainability goals. Agencies often favor lower-energy alternatives.
Smart Contract: Self-executing code stored on a blockchain that runs automatically when predefined conditions are met. Despite the name, smart contracts are neither "smart" nor legal contracts—they are deterministic programs.; Gov consideration: Federal acquisition rules (FAR/DFARS) still govern procurement even when a smart contract automates payment logic. Legal review is essential.
Hash: A fixed-length digital fingerprint produced by a cryptographic function. Any change to the input—even a single character—produces a completely different hash, making tampering detectable.
Immutability: The property that once data is recorded on the chain it cannot be altered or deleted. In practice, "practical immutability" is a more accurate term—data can theoretically be changed if a majority of nodes collude.

Network Types

Public (Permissionless) Network: A blockchain anyone can join, read, and write to without approval (e.g., Bitcoin, Ethereum). Offers maximum transparency but limited control over participants.; Gov consideration: Public networks raise questions about data sovereignty, FISMA compliance, and the ability to meet FedRAMP requirements for the underlying infrastructure.
Private (Permissioned) Network: A blockchain where participation is restricted to approved entities. An operating authority controls who can join, read, or validate transactions (e.g., Hyperledger Fabric).; Gov consideration: More compatible with existing compliance frameworks (FedRAMP, FISMA) because the operating environment can be controlled and audited.
Consortium Network: A permissioned network governed by a group of organizations rather than a single entity. Common in cross-agency or public-private partnerships where shared governance is needed.

Identity & Credentials

Decentralized Identifier (DID): A globally unique identifier that the subject (person, organization, or device) creates and controls, independent of any central registry. Defined by W3C standards.
Verifiable Credential (VC): A tamper-evident digital credential (e.g., license, clearance, certification) that can be cryptographically verified without contacting the issuer in real time.; Gov consideration: VCs are being explored for cross-border identity, workforce credentialing, and benefit delivery where real-time issuer availability cannot be guaranteed.
Self-Sovereign Identity (SSI): A model where individuals hold and control their own identity data rather than relying on a central authority. DIDs and VCs are the technical building blocks of SSI.
Zero-Knowledge Proof (ZKP): A cryptographic method that lets one party prove a statement is true (e.g., "I am over 21") without revealing the underlying data (e.g., date of birth).; Gov consideration: ZKPs support privacy-preserving compliance checks—verifying eligibility without collecting or storing sensitive PII.

Tokens & Digital Assets

Token: A digital unit recorded on a blockchain that can represent value, access rights, or ownership. Tokens are either fungible (interchangeable, like currency) or non-fungible (unique, like a deed).
Non-Fungible Token (NFT): A token that represents a unique asset or record. Beyond art and collectibles, NFTs can represent government-issued documents, permits, or serialized equipment records.
Stablecoin: A cryptocurrency designed to maintain a stable value, usually pegged to a fiat currency like the U.S. dollar. Used to reduce volatility in blockchain-based payment flows.
Central Bank Digital Currency (CBDC): A digital form of a country's sovereign currency issued and backed by its central bank. Unlike cryptocurrencies, CBDCs carry the full faith and credit of the issuing government.
Tokenization: The process of representing a real-world asset (property, bond, permit) as a digital token on a blockchain, enabling programmable transfer and fractional ownership.

Security & Compliance

Public Key / Private Key: A cryptographic key pair used to sign and verify transactions. The private key must remain secret; the public key can be shared freely. Losing a private key means losing access to associated assets.; Gov consideration: Key management must align with NIST SP 800-57 guidelines. Hardware security modules (HSMs) are typically required for production deployments.
Wallet: Software or hardware that stores private keys and lets users sign transactions. Wallets do not store tokens themselves—tokens remain on the blockchain.
51% Attack: A scenario where a single entity controls more than half of a network's validating power, enabling it to manipulate transaction history. More relevant to smaller public networks than large or permissioned ones.
NIST SP 800-53: The catalog of security and privacy controls for federal information systems. Blockchain deployments must map to applicable 800-53 controls just like any other system.; Gov consideration: Blockchain's immutable audit logs can directly satisfy controls in the AU (Audit and Accountability) family. However, public blockchains may introduce challenges for AC (Access Control) and SC (System and Communications Protection) families where the operating environment is not agency-controlled.
FedRAMP / FISMA: Federal frameworks for authorizing and monitoring the security of information systems. Any blockchain service handling federal data must meet applicable FedRAMP or FISMA requirements.
Authority to Operate (ATO): A formal authorization from an agency official that a system meets security requirements and can process federal data. Blockchain deployments require an ATO like any other federal system.

Interoperability & Standards

Interoperability: The ability of different blockchain networks or systems to exchange and use data across boundaries. Critical for cross-agency and cross-border scenarios.
Oracle: A service that feeds external, real-world data (e.g., weather, market prices, identity checks) into a smart contract. Oracles are a trust boundary—the blockchain is only as reliable as its data sources.
On-Chain vs. Off-Chain: On-chain data is stored directly on the blockchain; off-chain data is stored externally with only a hash or reference on-chain. Large or sensitive datasets are typically kept off-chain.; Gov consideration: Storing PII on-chain is generally inadvisable due to immutability and FOIA/Privacy Act implications. Hash-on-chain, data-off-chain is a common federal pattern.
API / Gateway: An interface that lets traditional applications interact with a blockchain without directly managing keys or consensus. Gateways simplify integration with existing agency systems.

Governance

Governance Framework: The rules, roles, and decision-making processes that control how a blockchain network operates, upgrades, and resolves disputes. Technology alone does not replace the need for governance.
Decentralized Autonomous Organization (DAO): An organization whose rules and treasury are managed through smart contracts, with decisions made by token-holder votes rather than traditional management structures.; Gov consideration: DAOs raise open questions about legal standing, accountability, and compliance with the Federal Advisory Committee Act (FACA) when advising agencies.
Fork: A divergence in a blockchain's protocol or transaction history. A "hard fork" creates two incompatible chains; a "soft fork" is backward-compatible. Forks can result from governance disagreements or planned upgrades.