Blockchain in Government: Use Cases, Limits, and Adoption

Blockchain in government is being tested for identity credentials, property records, supply chain tracking, procurement, and grant payments, but a Government Accountability Office review found most efforts have not moved past the pilot stage.¹ The appeal is clear: a distributed ledger spreads a shared record across many computers so no single party can quietly alter it, which suits situations where multiple organizations that don’t fully trust each other need to share data. The obstacles are equally clear. Agencies have run into privacy conflicts, weak interoperability with legacy systems, unsettled regulation, and a shortage of staff who can build on the technology.

When Blockchain Actually Fits a Government Problem

Not every government workflow benefits from a distributed ledger. The National Institute of Standards and Technology recommends that agencies ask whether blockchain genuinely fits the problem rather than forcing existing systems onto it.² NIST’s conditions for a good fit: many distributed participants, no trusted central authority, a transactional workflow, and a real need for a cryptographically secure ownership record or transaction history shared among the participants.

When only a handful of trusted agencies share data, a conventional database is simpler and cheaper. The GAO reached the same conclusion, saying blockchain “may be overly complex for a few trusted users, where traditional spreadsheets and databases may be more helpful.”¹ Federal projects that have advanced furthest tend to involve supply chains, trade verification, and multi-party record-keeping where the trust gap is genuine.

NIST also emphasizes that federal blockchain use must comply with existing law. Federal records remain subject to records-management rules, and personally identifiable information generally should not be written directly to a blockchain, even a permissioned one.² That single constraint shapes almost every project and explains why agencies default to permissioned networks with restricted access rather than open public chains.

Digital Identity and Verifiable Credentials

Digital identity is one of the most active research areas. The concept relies on decentralized identifiers, which the World Wide Web Consortium defines as identifiers that enable verifiable, decentralized digital identity without depending on a centralized registry or certificate authority.³ Each identifier links to a document with cryptographic public keys that let the holder prove control of the identity without needing permission from an intermediary.

The practical form is a verifiable credential: a digital version of a driver’s license or a diploma carrying a cryptographic signature from the issuer. The W3C framework expresses these in a way that is “cryptographically secure, privacy respecting, and machine-verifiable.”⁴ The holder presents the credential to a verifier, who checks the signature against the issuer’s public key. Raw personal data stays with the holder instead of sitting in a government database that fields every verification request.

More than 20 states now issue or accept mobile driver’s licenses, formatted and authenticated under the ISO 18013-5 standard so a credential issued in one state can be verified at an airport, bank, or government office elsewhere. A boundary worth flagging: not every mobile credential runs on blockchain. The verifiable credential model was designed to work with distributed ledgers and is often adopted alongside them, but the two are not the same thing.

Property and Title Records

Land registries fit the criteria well. Property transfers involve multiple parties, happen infrequently, and depend on a clear chain of ownership. Recording deeds or interests as tokens on a blockchain means each transfer becomes a transaction requiring cryptographic signatures from both buyer and seller, producing a tamper-resistant history.

County pilots have produced modest but useful findings. They showed that blockchain can combine the transfer of property and the recording of that transfer into a single event, and that cryptographic signatures make unauthorized transfers substantially harder. They also showed that proof-of-work blockchains consume too much energy for real estate recording, and that permissioned distributed ledgers are more practical.

The legal foundation is already in place. Under the federal Electronic Signatures in Global and National Commerce Act, a contract or record cannot be denied legal effect solely because it is in electronic form.⁵ The Uniform Electronic Transactions Act, adopted in most states, gives electronic signatures and records the same weight as paper. Several states have gone further, passing laws that explicitly recognize blockchain records and treat signatures secured through blockchain as valid electronic signatures.

The practical hurdle is integration. County clerks still supervise document submission, and any blockchain system has to work with recording software that has been in place for decades. Filing fees vary widely by jurisdiction and document type, and those fee structures generally were not designed for blockchain submissions.

Procurement and Supply Chain Tracking

This is where the more concrete federal results have appeared. Treasury launched a proof of concept tracking government-issued mobile phones on a blockchain-based inventory system and reported that it improved operational efficiency by automating manual processes.⁶ The General Services Administration piloted a blockchain solution to automate contract review, aiming to reduce staff time on proposal documents.

U.S. Customs and Border Protection has been among the most active. CBP completed a proof of concept using blockchain to protect intellectual property rights on American imports, connecting product data to licenses on a single platform. The agency reported the system reduced physical examinations and contributed to global standardization work at the W3C.⁷

Smart contracts do much of the work in these applications. They are self-executing programs stored on the blockchain that trigger actions when conditions are met. A smart contract can release payment when proof of delivery is uploaded, or apply a penalty when a milestone deadline passes.

The military has moved further than most civilian agencies. The Department of the Air Force funded blockchain smart contract integration for multi-service supply chain data, and in 2024 Army Materiel Command used blockchain tags to track equipment and give real-time visibility into mission-critical items. These match the NIST criteria closely: many participants, distributed geography, transactional workflows, and a real need for shared provenance.

Grants, Tax Reporting, and the Halted Digital Dollar

Treasury’s 2019 grant payment project tested whether an interagency blockchain could increase transparency in grants and allow digital redemption and transfer of payments.⁶ Federal grants pass through multiple agencies, universities, and contractors, all of whom must verify that funds are spent according to the terms. A smart contract that releases the next installment only after a grantee uploads required documentation can replace weeks of manual review.

On the revenue side, blockchain intersects with tax reporting through the IRS Form 1099-DA. Starting January 1, 2026, brokers must report gross proceeds for digital asset transactions on this form, with cost basis reporting required for covered securities acquired after 2025.⁸

Federal Reserve research on a central bank digital currency, essentially a government-issued digital dollar on a distributed ledger, hit a wall in January 2025.⁹ A presidential executive order prohibited federal agencies from taking any action to establish, issue, or promote a CBDC and ordered existing plans terminated. The order characterized CBDCs as threats to financial stability, individual privacy, and U.S. sovereignty, and took a favorable stance toward private-sector blockchain development, including stablecoins and open public networks.¹⁰ The United States remains the only major economy to have explicitly halted retail CBDC work.

Voting: A Case Where It Hasn’t Worked

Blockchain voting has drawn attention and equally sharp criticism. The concept treats each ballot as an encrypted transaction distributed to network nodes for validation, with a cryptographic hash preventing double-counting while preserving voter anonymity.

Security researchers have not been persuaded. An MIT analysis of one blockchain voting application found that an attacker with remote access to a voter’s device could alter or discover the vote, that a compromised server could change votes, and that a passive network observer such as an internet service provider could detect which way someone voted in certain configurations. The researchers concluded that “the consensus of security experts is that running a secure election over the internet is not possible today.”¹¹ Vulnerabilities went beyond the blockchain layer: reliance on a third-party vendor for voter identification created additional privacy risks.

The Election Assistance Commission’s Voluntary Voting System Guidelines 2.0, adopted in 2021 and ready for testing as of late 2022, contain no requirements specific to blockchain-based systems.¹² Compliance is voluntary at the federal level, though some states require it by statute. No blockchain voting system has been certified under these guidelines, and no state uses blockchain as the primary mechanism for recording votes in general elections.

Privacy vs. Immutability

The feature that makes blockchain attractive for records, immutability, collides directly with privacy laws that give people the right to have their data erased. Once personal information is written to a blockchain, deleting it the way you would delete a database entry is not straightforward, because the network maintains copies.

Agencies have developed several workarounds:

Off-chain storage with on-chain references. Personal data lives in a traditional, deletable database. The blockchain stores only a cryptographic hash or pointer. When someone requests deletion, the underlying data is removed and the hash becomes meaningless.
Encryption key destruction. Personal data is encrypted before being written to the ledger, with keys held separately. Destroying the key renders the on-chain data permanently unreadable.
Zero-knowledge proofs. Cryptographic techniques that let one party verify a fact about another party’s data without the data itself being exposed or stored on the ledger.

NIST warns that personally identifiable information and data governed by privacy regulations “may or may not be appropriate to store even within a permissioned blockchain network.”² That is why nearly every government project handling citizen data uses an off-chain model. The ledger verifies and timestamps; the personal information stays in systems designed to be edited and purged.

What’s Holding Adoption Back

Any federal agency deploying blockchain must use cryptographic modules that meet FIPS 140-3, the standard covering cryptographic security in federal systems that handle sensitive information. The standard defines four increasing security levels, and agencies must match the level to their risk profile.¹³ Private keys that sign transactions must be generated and held in hardware security modules that have passed certification.

Beyond certification, several constraints have slowed adoption:

Scalability. Most platforms struggle to optimize cost, speed, node count, and security at once. Transaction throughput remains well below what large government systems require.
Energy consumption. Proof-of-work consensus consumes enormous amounts of electricity, and pilots have consistently concluded that permissioned networks with lighter consensus are the only viable option.
Interoperability. Most blockchain networks cannot communicate with each other or with the legacy systems agencies already run. The GAO identified this as a primary challenge and noted that organizations wanting to adopt blockchain “have found it difficult to find skilled workers to implement blockchain.”¹
Legacy integration. Connecting new ledgers to decades-old databases is consistently cited as the largest technical hurdle. The data feeding a blockchain is only as trustworthy as the system it came from.

The GAO recommended that policymakers unify standards, clarify oversight, and support work that determines whether blockchain is genuinely appropriate for a given mission rather than treating it as a universal solution.¹ That captures where things stand: useful in specific, well-defined cases, still years from the broad institutional adoption early advocates predicted.

1
U.S. Government Accountability Office. Blockchain: Emerging Technology Offers Benefits for Some Applications but Not a Cure-All
2
National Institute of Standards and Technology. NISTIR 8202 – Blockchain Technology Overview
3
World Wide Web Consortium. Decentralized Identifiers (DIDs) v1.1
4
World Wide Web Consortium. Verifiable Credentials Overview
5
Office of the Law Revision Counsel. 15 USC 7001 – General Rule of Validity
6
U.S. Government Accountability Office. Small Business Administration: Exploring Potential Use of Blockchain
7
U.S. Customs and Border Protection. CBP Leverages Blockchain Innovation to Protect American Business
8
Internal Revenue Service. Instructions for Form 1099-DA (2026)
9
Board of Governors of the Federal Reserve System. Central Bank Digital Currency (CBDC)
10
The White House. Strengthening American Leadership in Digital Financial Technology
11
Massachusetts Institute of Technology. MIT Researchers Identify Security Vulnerabilities in Voting App
12
U.S. Election Assistance Commission. Voluntary Voting System Guidelines
13
National Institute of Standards and Technology. FIPS 140-3 – Security Requirements for Cryptographic Modules