Blockchain Regulatory Certainty Act of 2026
- Sponsor
- Sen. Lummis, Cynthia M. [R-WY]
- Committees
- Banking, Housing, and Urban Affairs Committee (primary)
- Last action
- Jan 12, 2026
Bottom line
The bill provides regulatory clarity by exempting non-controlling blockchain developers and infrastructure providers from money transmission laws, distinguishing them from financial intermediaries.
What it actually does
This bill clarifies that certain non-controlling developers or providers of distributed ledger services, such as those who create software or provide infrastructure for digital assets without having unilateral control over user transactions, are not to be treated as money transmitting businesses under federal law. It also exempts them from substantially similar state registration requirements, aiming to provide regulatory certainty for technology providers in the blockchain space.
Proponents argue
Supporters argue that this legislation is crucial for fostering innovation in the digital asset sector by preventing the misapplication of outdated money transmission laws to technology providers who do not custody or control user funds. They contend it provides necessary legal certainty, reduces regulatory burdens, and encourages the development of decentralized technologies in the United States.
Opponents contend
Critics might contend that while aiming for clarity, the bill could inadvertently create regulatory gaps, potentially making it harder for authorities to track illicit financial activities or protect consumers if certain actors are exempted from oversight. Concerns could be raised about the precise definition of 'non-controlling' and whether it adequately safeguards against potential misuse.
The bill is very short and straightforward, making it highly accessible for a reader to understand its core provisions and implications within a short timeframe.
Section 2(a)
Definitions for Distributed Ledger Services and Non-Controlling Developers
This section defines key terms central to the bill's scope. It clarifies what constitutes a 'digital asset,' a 'distributed ledger,' and a 'distributed ledger service.' Crucially, it defines a 'non-controlling developer or provider' as a person or business that creates or maintains distributed ledger services but lacks the legal right or unilateral ability to control, initiate, or effectuate user transactions without third-party approval.
Supporters argue
Supporters argue that precise definitions are essential for legal certainty, allowing innovators to understand their regulatory obligations and avoiding the stifling of new technologies by broadly applying outdated legal frameworks.
Critics contend
Critics might express concern that overly specific definitions could create unforeseen loopholes or become quickly outdated as digital asset technologies evolve, potentially hindering future regulatory adaptability.
Tradeoffs
The provision balances the need for clear legal boundaries to foster innovation against the risk that definitions might be too narrow or become obsolete, potentially creating regulatory arbitrage opportunities.
Section 2(b)
Exemption from Money Transmission Laws for Non-Controlling Developers
This is the core operative provision, stating that a 'non-controlling developer or provider' shall not be treated as a money transmitting business under federal law (31 U.S.C. 5330 and 18 U.S.C. 1960). Furthermore, it exempts these entities from any substantially similar state registration requirements, solely based on activities like creating software, providing hardware for self-custody, or offering infrastructure support for distributed ledger services.
Section 2(c)
Rules of Construction and Limitations of the Exemption
This section provides important caveats, clarifying that the bill's exemption does not affect other existing laws, such as those related to anti-money laundering (AML), countering the financing of terrorism (CFT), or the classification of entities as financial institutions for other conduct. It also states that the bill does not limit or expand intellectual property law, nor does it prevent states from enforcing consistent state laws. Finally, it prevents the creation of new causes of action or liabilities inconsistent with the Act.
The definition of 'non-controlling developer or provider' is critical, specifying that such an entity must not have the 'legal right or the unilateral and independent ability to control, initiate upon demand, or effectuate transactions involving digital assets to which users are entitled, without the approval, consent, or direction of any other third party.'
Section 2(a)(5)
Why it matters:It is standard legislative practice to place definitions at the beginning of a section. However, the specificity of this definition is highly consequential, determining exactly who qualifies for the regulatory exemption.
Case for: Supporters argue that this precise language is essential to accurately distinguish between true financial intermediaries and mere technology providers, ensuring that the exemption is narrowly tailored and does not inadvertently cover entities that should be regulated as money transmitters.
Case against: Critics might argue that the highly technical and specific nature of this definition could lead to complex legal interpretations or attempts by entities to structure their operations to fit within the exemption, potentially creating regulatory arbitrage or making enforcement challenging in practice.
Estimated impact: This definition significantly narrows the scope of money transmission laws for a specific class of blockchain participants, potentially affecting a large number of software developers and infrastructure providers in the digital asset space.