The Act directs the Secretary of Commerce to serve as the President’s principal policy advisor on the deployment, use, and competitiveness of blockchain technology and related tokenization, and to promote applications built on distributed ledger technology. It creates a Blockchain Deployment Program within the Department of Commerce to coordinate federal efforts, develop standards, promote security, and advance interoperability.
The Act also establishes advisory committees and requires ongoing reporting to Congress, with a sunset of seven years for the program.
At a Glance
What It Does
Defines blockchain technology and tokens, designates the Secretary to lead policy, and creates a Blockchain Deployment Program to coordinate deployment, security, and tokenization efforts.
Who It Affects
Federal agencies adopting blockchain; private sector developers, operators, and vendors; and nongovernmental stakeholders participating in an advisory framework.
Why It Matters
Establishes a formal, cross‑agency approach to blockchain adoption, security, and interoperability, aiming to raise U.S. competitiveness while managing national security considerations.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
This bill sets a federal policy framework for blockchain and tokenization. It begins by defining blockchain technology, distributed ledger technology, tokens, and tokenization, ensuring everyone operates with the same vocabulary.
It then elevates the Secretary of Commerce to a central role, charging the department with guiding policy development, coordinating interagency efforts, and promoting the deployment of blockchain technologies in a secure and interoperable manner. A Blockchain Deployment Program is created within the Department to lead these efforts, with responsibilities that include improving security practices, encouraging industry-wide standards, and fostering open-source infrastructure where appropriate.
The bill emphasizes coordination with other federal agencies, private sector stakeholders, and public-private partnerships to advance practical use cases and resilience across supply chains and critical systems.
The Five Things You Need to Know
The Secretary of Commerce becomes the President’s principal policy advisor on blockchain, tokens, and tokenization.
A Blockchain Deployment Program within the Department of Commerce will coordinate federal efforts and promote security, interoperability, and practical deployment.
Advisory committees with broad federal and nonfederal participation must be formed within 180 days to guide adoption and policy.
Best practices are to be developed to reduce cybersecurity risks, enable interoperability, and support open-source infrastructure and secure key management.
The Secretary must report to Congress not later than two years after enactment and annually thereafter, detailing activities, risks, and legislative recommendations.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions for blockchain and related terms
Section 2 establishes the core meanings the rest of the bill relies on: blockchain technology or other distributed ledger technology, coverage of tokens, and tokenization. The definitions are crafted to ensure a common understanding across agencies and industry participants, reducing ambiguity when assessing deployment, security, and regulatory considerations. This definitional groundwork is essential because it anchors policy scope, program activities, and the interpretation of “applications built on blockchain technology.” Without precise terms, interagency coordination and industry guidance could drift apart, undermining interoperability and risk management.
Department of Commerce leadership on blockchain; program creation
Section 3 designates the Secretary of Commerce as the lead policy official for blockchain deployment and competitiveness. It directs the Secretary to develop policy recommendations addressing deployment, use, and risks, and to promote stability, security, and interoperability of blockchain systems and tokenization. Subsection (b) outlines concrete actions, including creating a Blockchain Deployment Program within the Department, promoting best practices, and coordinating with federal agencies to align efforts. Subsection (c) requires ongoing engagement with the public to disseminate best practices and to support private‑public collaboration. Subsection (d) broadens the scope to include national and economic security implications, while subsection (e) provides protections and limits around voluntary actions by private entities. Subsection (h) authorizes advisory committees within 180 days, composed of senior officials from government and nongovernmental stakeholders covering infrastructure operators, developers, industry users, academia, and other relevant groups. Overall, this section creates a centralized, formal mechanism to guide adoption, security, and interagency coordination while incorporating broad stakeholder input.
Reports to Congress
Section 4 requires a reporting cadence: not later than two years after enactment and annually thereafter. Reports must describe the Secretary’s activities, propose any needed additional legislation to strengthen competitiveness, and identify emerging risks and long‑term trends related to blockchain technology, tokens, and tokenization. These reports are public on the Department of Commerce website and submitted to relevant congressional committees, providing policymakers and industry with ongoing visibility into the program’s progress and evolving risk landscape.
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
- Blockchain infrastructure operators, service providers, and developers who gain clearer Federal guidance, interoperability standards, and a more predictable regulatory environment for deployments and tokenization.
- Federal agencies that deploy blockchain solutions can leverage centralized leadership and best practices to reduce duplicative work and strengthen security across government systems.
- Industry groups and private sector participants can align around standardized terminology, open‑source tooling, and cost‑effectiveness analyses that illuminate deployment pathways and ROI.
- Rural stakeholders and other underrepresented groups receive opportunities to participate through advisory committees and targeted engagement designed to surface diverse perspectives.
- Academia, think tanks, and consumer groups gain access to federal data and expert collaboration to study and shape policy and practice.
Who Bears the Cost
- Private sector entities may incur costs to align products and processes with new best practices, interoperability standards, and reporting expectations.
- Federal agencies will need to allocate staff time and resources to coordinate with the Blockchain Deployment Program and implement related policies.
- Small and medium‑sized businesses may face compliance and governance costs associated with participating in standards development and advisory activities.
- Vendors and infrastructure providers may incur expenses to support security enhancements, documentation, and interoperability requirements.
Key Issues
The Core Tension
How to reconcile a proactive, government‑led push for broad blockchain adoption and security with the private sector’s need for operational flexibility, cost control, and voluntary compliance, while ensuring interoperability and open‑source support without creating excessive regulatory or fiscal burdens.
The bill emphasizes collaboration, standardization, and risk reduction, but it also relies on voluntary engagement and nonbinding best practices rather than mandatory controls. The Rules of Construction clarify that private entities are not obligated to share information or adopt every recommendation, which preserves flexibility but may slow uniform adoption across the private sector.
Funding, staffing, and long‑term maintenance of the program depend on future appropriations and agency prioritization, which could influence the pace and rigor of implementation. Open questions remain about the precise allocation of responsibilities among agencies, the sufficiency of advisory committee participation, and the balance between open‑source activity and secure, controlled deployment.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.