The Deploying American Blockchains Act of 2025 designates the Secretary of Commerce as the principal federal advisor to the President on blockchain and distributed ledger technology (DLT). It directs Commerce to form a National Blockchain Deployment Advisory Committee, produce an ongoing compendium of best practices for deployment, and publish annual and final reports to Congress on activities, risks, and recommendations.
The bill matters because it centralizes federal coordination on an emerging cross-sector technology without creating new regulatory authority or mandatory requirements. The statute seeks to accelerate adoption—by promoting interoperability, security practices, and open-source infrastructure—while preserving voluntary private-sector participation and avoiding compelled data-sharing or mandatory adoption of guidelines.
At a Glance
What It Does
The bill makes the Secretary of Commerce the lead federal advisor on blockchain/DLT, requires establishment of a National Blockchain Deployment Advisory Committee within 180 days, and tasks Commerce with developing a public compendium of deployment best practices and annual reports to Congress. The committee is time-limited and must include federal representatives and a broad set of nongovernmental experts.
Who It Affects
Federal agencies considering blockchain adoption, technology vendors and infrastructure operators, application developers, tokenization projects (including creators and marketplaces), cybersecurity firms, and state/local governments that may align with federal guidance. It also explicitly includes small businesses, rural stakeholders, and the content creator community among potential committee members.
Why It Matters
This law would be the federal government’s highest-level effort to coordinate blockchain policy through Commerce rather than a financial regulator, emphasizing interoperability, security, and voluntary standards. For compliance officers and product teams, it signals forthcoming government-curated best practices and greater visibility into federal agency use cases and security expectations.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Act assigns the Secretary of Commerce a formal leadership role on policy questions tied to blockchain and distributed ledger technology, tokens, and tokenization. That role is advisory: the Secretary coordinates federal engagement, organizes an advisory committee, and compiles and publishes guidance—rather than issuing binding rules.
The statute defines key terms (blockchain/DLT, token, tokenization) so that subsequent work by Commerce rests on a common conceptual baseline.
Within 180 days Commerce must create the National Blockchain Deployment Advisory Committee. The committee’s membership mixes federal agency representatives with nongovernmental experts—covering infrastructure operators, application developers, cybersecurity specialists, small and large businesses, academia, nonprofit and consumer groups, rural interests, and artists/content creators.
The committee exists for seven years; Commerce will use it to collect proposals, prioritize use cases, and draft the compendium of best practices.The compendium Commerce is tasked to build is broad: it must include guidelines to support deployment and interoperability, operations (including hashing and key storage), cybersecurity risk reduction, and economic analyses that quantify potential cost savings versus competing technologies. Commerce must also promote standardized terminology, open-source infrastructure and authentication work, and coordinate across agencies—while consulting closely with private-sector stakeholders.The Act pairs these programmatic tasks with transparency and reporting obligations: Commerce must publish annual reports starting within two years describing activities, emerging risks, and legislative recommendations, and provide a final report with the committee’s findings 18 months before the committee terminates.
Importantly, the statute limits Commerce’s authority—explicitly preventing the Secretary from compelling private entities to share information, request assistance, or adopt suggested measures—leaving implementation and compliance largely voluntary.
The Five Things You Need to Know
The Secretary of Commerce becomes the principal federal advisor to the President on blockchain/DLT, tokens, and tokenization.
Commerce must establish the National Blockchain Deployment Advisory Committee within 180 days; the committee terminates 7 years after enactment.
The advisory committee’s membership must include the Secretary, selected federal agency representatives, and covered nongovernmental representatives spanning infrastructure operators, developers, cybersecurity experts, industry sectors, small businesses, academics, nonprofits, rural stakeholders, and creators.
Commerce must develop and maintain a public compendium of best practices addressing interoperability, key storage, cybersecurity, operations, and comparative economic analyses of blockchain versus competing technologies.
Commerce must publish an initial public report within 2 years and annual reports thereafter, plus a final advisory-committee report 18 months before the committee’s statutory termination; the statute explicitly forbids Commerce from compelling private-sector data sharing or mandatory adoption of recommendations.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Terminology and scope for blockchain, tokens, and tokenization
Section 2 sets the vocabulary the rest of the Act uses: a concise, operational definition of ‘‘blockchain technology or other distributed ledger technology,’’ and defined terms for ‘‘token’’ and ‘‘tokenization.’' That matters because Commerce’s compendium, outreach, and reports must operate against these definitions—reducing ambiguity about what counts as covered technology while excluding non‑digital concepts. The definition also frames the statute around ledger integrity, cryptography, and automated distribution, which channels the advisory committee’s technical focus.
Designates Commerce as federal lead and lists advisory functions
These subsections make the Secretary a principal advisor to the President on deployment, use, applications, competitiveness, tokens, and tokenization, and spell out a menu of activities: examining decentralized identity, key storage, AI interactions, fraud reduction, regulatory compliance, health care and supply chain uses, and national security. Practically, Commerce gains an explicit mandate to convene stakeholders, assess federal use cases, and prioritize security and interoperability—while the list of activities signals priority areas agencies and industry should expect to see analyzed and addressed.
Creates the National Blockchain Deployment Advisory Committee and sets membership
Commerce must create the Advisory Committee within 180 days and may appoint members at its discretion, but the statute prescribes categories to ensure broad technical and sectoral representation—federal officials plus private-sector infrastructure operators, developers, academics, small businesses, creators, cybersecurity experts, rural voices, and consumer groups. The seven‑year sunset limits the committee’s lifespan and signals a temporary, programmatic effort rather than permanent governance. Because the statute allows the Secretary to determine the number and selection process, composition and balance will be set by Commerce rulemaking or chartering procedures.
Compendium scope, stakeholder consultation, and operational priorities
Commerce must maintain an ongoing compendium of guidelines focused on deployment, interoperability, operational foundations (hashing, key storage), cybersecurity risk reduction, and economic comparisons to competing technologies. The statute requires close consultation with private stakeholders, support for open-source approaches, standardized terminology, and alignment of recommendations to ease of use—directives that push Commerce toward performance-based, repeatable guidance rather than prescriptive technical mandates. The provision also requires Commerce to weigh both private- and public-sector needs, including small businesses and governments.
Limits on compulsion and permission to consult other agencies
The Act contains explicit rules of construction preventing Commerce from compelling private entities to share information, request assistance, adopt recommendations, or implement best practices—preserving voluntariness. It also authorizes Commerce to consult with other relevant federal agencies as appropriate, creating a coordination channel without reallocating regulatory authority. The upshot is an administrative coordination and guidance function with no new coercive powers.
Annual transparency obligations and a final advisory report
Section 4 requires Commerce to post to its website and submit to relevant congressional committees an initial public report within two years and annual follow-ups describing Commerce’s activities, recommended legislation to strengthen U.S. competitiveness, and emerging risks and long-term trends. It also mandates a final report with the committee’s findings 18 months before the committee sunsets. These reporting duties create an evidence base for future legislative or regulatory changes but do not themselves establish enforcement mechanisms.
This bill is one of many.
Codify tracks hundreds of bills on Technology across all five countries.
Explore Technology in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Federal agencies assessing blockchain adoption — gain a centralized advisory resource and a public compendium that catalogs use cases, security practices, and interoperability standards to inform procurement and pilot decisions.
- Infrastructure operators and developers — receive government-curated best practices and visibility into federal priorities, which can lower adoption friction and help align commercial offerings to public-sector needs.
- Small businesses and rural stakeholders — are explicitly included in committee representation and guidance work, which may surface lower-cost, repeatable deployment patterns and open-source tools tailored to limited IT budgets.
- Artists and content creators using tokens and digital assets — the statute lists creators as potential committee participants, increasing the odds that guidance will address creator-focused tokenization, rights management, and marketplaces.
- Cybersecurity and identity vendors — the bill prioritizes key storage, hashing, and cyber risk reduction, creating potential demand for services and products that implement recommended practices.
Who Bears the Cost
- Department of Commerce — must staff, run, and sustain the advisory committee, develop the compendium, and publish reports without specific appropriations in the text, creating administrative and operational costs for the department.
- Private stakeholders who participate — companies and nonprofits will expend time and possibly share technical information (voluntarily) to engage with the committee and public compendium, and may face reputational or IP concerns in open processes.
- Federal agencies adapting to Commerce guidance — agencies that elect to implement recommendations may incur integration, security-hardening, and procurement costs when piloting blockchain solutions.
- Small vendors and startups — if federal or market actors coalesce around Commerce-recommended standards, smaller firms may need to invest to meet interoperability or security expectations to stay competitive.
- Congress and oversight bodies — increased reporting and consultation imply staff time and potential requests for follow-up legislation or hearings, imposing opportunity costs on legislative offices.
Key Issues
The Core Tension
The central dilemma is promotion versus protection: the bill pushes the federal government to accelerate U.S. deployment and competitiveness in blockchain through voluntary standards and coordination, but it does so without coercive authority or earmarked funding—so policymakers must choose between rapid, market‑led adoption (which risks security, consumer, and legal harms) and slower, more prescriptive regulatory approaches that could stifle innovation. Commerce’s advisory posture solves the coordination problem at low political cost but leaves unresolved who will enforce security, protect consumers, and adjudicate token legal status.
The Act centralizes coordination but leaves substantive regulatory authority unchanged: Commerce gets convening power and a mandate to publish guidance, but no enforcement tools, appropriations, or rulemaking authority. That structure creates a practical dependence on voluntary industry cooperation and interagency buy-in for any real effect.
Without clear funding or a mechanism to require adoption, the compendium’s influence will depend on whether federal procurement, grant programs, or standards bodies choose to reference Commerce outputs.
The statute pushes simultaneously toward openness (standard terminology, open-source infrastructure) and heightened security (key storage, cyber risk reduction), a pair of objectives that can conflict in practice—open-source components ease interoperability but can increase the attack surface if not properly managed. The committee’s broad membership aims for inclusion, but also raises capture risks: heavy representation from incumbent infrastructure operators could skew recommendations toward proprietary solutions.
Also unresolved are cross‑agency alignment and legal risk around ‘‘tokens’’—the bill treats tokens as technical objects without clarifying their regulatory treatment under securities, commodities, or consumer-protection laws, leaving a gap between Commerce guidance and legal accountability frameworks managed by agencies like the SEC, CFTC, Treasury, and FTC.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.