The bill establishes a federal safe harbor protecting blockchain developers and providers of blockchain services from being treated as money transmitters, financial institutions (per 31 U.S.C. 5312), or otherwise requiring licensing or registration under state or federal law—so long as they do not have "control" over users' digital assets. "Control" is defined narrowly in the text as the unilateral and independent legal ability to obtain data sufficient to initiate transactions that spend digital assets without third-party approval.
The measure also defines key terms (blockchain developer, blockchain network, blockchain service, control, and digital asset), preserves intellectual property law, and limits state- or local-law interference by allowing states to enforce laws consistent with the safe harbor while barring causes of action under inconsistent state or local laws. For developers, node operators, and fintech lawyers, the bill seeks to replace patchwork regulatory treatment with a single federal test focused on custody-like control rather than software distribution or network facilitation.
At a Glance
What It Does
Creates a statutory safe harbor: a person who creates, maintains, or disseminates blockchain software or provides blockchain services is not a money transmitter or financial institution unless they have "control" over digital assets. The bill supplies definitions for "control" and "digital asset" to set the boundary of the exemption.
Who It Affects
Open-source protocol developers, noncustodial wallet and node operators, hosted blockchain-service providers, custodial crypto firms, state regulators, and federal AML/CFT authorities all encounter changed legal exposure under the bill's safe-harbor test.
Why It Matters
It shifts regulatory focus away from software distribution and network facilitation toward a custody/control test, lowering licensing risk for many developers while creating new doctrinal questions about what counts as custody, possession, or reliance on intermediaries.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
At its core, the bill draws a line between actors who merely create, maintain, or make available blockchain software and those who functionally control users' digital assets. Rather than treating any party that distributes software or runs services as a money transmitter, the statute insulates actors unless they possess the specific, unilateral ability to obtain data that would let them initiate transactions spending a user's assets without the approval of another party.
That is the statutory hinge: custody-like power, not participation in a network or revenue model, determines regulatory exposure.
The bill's definitions matter for operational compliance. A "blockchain developer" covers entities that create, maintain, or disseminate relevant code; a "blockchain service" covers systems that enable multiple users to access a network, including services that enable sending, receiving, exchanging, or storing digital assets; and a "blockchain network" is described as a consensus-driven system that allows permissionless participation.
The "digital asset" definition requires exclusive possession and person-to-person transferability without necessary reliance on an intermediary—language that aims to separate native ledger assets from custodial claims or tokenized representations of off‑chain rights.Practically, the bill encourages designs and contracts that avoid unilateral control: developers and service providers will want to document noncustodial architecture (no access to private keys, no unilateral ability to sign transactions, clear user control over funds). That documentation will be critical in litigation or regulatory reviews because the safe harbor depends on whether the actor actually has the unilateral legal right and technical ability to effectuate transfers.
The statute does not modify securities, commodities, or other federal laws; it only narrows certain designations tied to licensing and registration that depend on custody or money‑transmission characterizations.Finally, the bill calibrates federal‑state interaction: it preserves intellectual property law and tells states they may enforce laws consistent with the safe harbor, while barring causes of action under state or local laws that are inconsistent. That approach tries to create a federal backstop for developers while leaving room for state regulation that aligns with the statutory test.
The Five Things You Need to Know
The safe harbor shields a blockchain developer or service provider from being treated as a money transmitter or financial institution unless the actor has "control" as defined in the bill.
The bill defines "control" as the unilateral and independent legal right and technical ability to obtain data sufficient to initiate transactions spending digital assets without third-party approval.
"Digital asset" is defined as intangible personal property that can be exclusively possessed and transferred person-to-person without necessary reliance on an intermediary.
The statute preserves intellectual-property law and permits states to enforce laws consistent with the safe harbor, but it bars causes of action under state or local laws that are inconsistent with the bill.
A "blockchain developer" in the text expressly includes any person or business that creates, maintains, or disseminates software that facilitates a blockchain network or blockchain service.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Identifies the Act as the "Blockchain Regulatory Certainty Act." This is a formal label only, but it signals the bill's purpose: to provide statutory clarity for blockchain participants by defining the scope of regulatory exposure rather than relying on agency or case‑by‑case analysis.
Safe harbor from money-transmitter and financial-institution treatment
Sets the substantive protection: developers and providers of blockchain services shall not be treated as money transmitters, financial institutions (per 31 U.S.C. 5312), or otherwise required to obtain licenses or registrations unless they have "control" over digital assets. For enforcement and compliance, this creates an affirmative test—custody-like control—that courts and regulators must apply when deciding whether an actor's activities trigger licensing obligations.
Interaction with other laws — IP carveout and state-law consistency
Clarifies that the Act does not change intellectual-property rights and places limits on state and local laws: states may enforce laws that are consistent with the safe harbor, but inconsistent state or local laws cannot give rise to causes of action or impose liability. The provision is a conditional savings clause that attempts to harmonize federal certainty with the state's policing power, while preventing conflicting municipal or state claims from undermining the federal test.
Definitions: blockchain developer, network, and service
Defines a "blockchain developer" broadly to include creators, maintainers, and disseminators of software; a "blockchain network" as a consensus-based, permissionless system; and a "blockchain service" as any multi-user system that provides or enables access to such a network, including services that let users send, receive, exchange, or store digital assets. These definitions make clear the safe harbor targets both open-source protocol contributors and hosted access providers, but they also require courts to parse whether particular offerings qualify as a "service" versus a custodial product.
Definitions: control and digital asset
Provides the operative definitions that gate the safe harbor. "Control" is defined as the unilateral legal right and technical ability to obtain data that would let a party initiate transactions spending assets without third-party approval; "digital asset" is defined by exclusive possessability and person-to-person transferability without necessary reliance on an intermediary. These are the mechanical criteria that will determine who falls inside or outside the exemption—and therefore will shape product design, contractual language, and recordkeeping.
This bill is one of many.
Codify tracks hundreds of bills on Finance across all five countries.
Explore Finance 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
- Open-source protocol developers: The bill protects developers who write and distribute blockchain code from being classified as money transmitters merely for publishing or maintaining software, reducing litigation and licensing risk for contributors and foundations.
- Noncustodial wallet providers and node operators: Services that are architected so they never hold users' private keys or possess unilateral signing ability will gain clearer statutory cover from money-transmission rules.
- Startups building middleware or indexers: Firms that provide access layers, analytics, or relay services without custody can operate with lower compliance cost and less risk of state licensing actions.
- Cloud and hosting providers running public nodes: Providers that host nodes but do not exercise unilateral control over funds get reduced exposure to money-transmitter classification, simplifying service offerings for enterprise customers.
Who Bears the Cost
- Custodial exchanges and wallets: Firms that do hold keys, custody funds, or can unilaterally move assets remain outside the safe harbor and therefore continue to face licensing, registration, and AML/CFT obligations.
- State and local regulators and plaintiffs' lawyers: The bill constrains some state-law causes of action and local regulation that are inconsistent with the federal safe harbor, reducing enforcement tools available to states and private litigants.
- Consumers using purportedly noncustodial services: If services are designed to avoid the "control" trigger but still enable recovery or administrative intervention, consumers may face diminished remedies if those design choices are later litigated as compliant.
- Compliance and legal teams at developers and providers: Businesses will need to invest in technical separation, documentation, and legal proof (e.g., key-management audits, contracts) to demonstrate non-control in disputes, shifting costs from licensing to operational compliance.
Key Issues
The Core Tension
The bill trades regulatory certainty for developers against reduced enforcement reach and potentially weaker consumer protections: it solves uncertainty by drawing a bright custody/control line, but that same line can let behavior that looks like intermediation escape licensing rules if technically structured to avoid "control," creating a classic trade-off between innovation-friendly bright lines and the flexible regulatory tools regulators use to police fraud and financial risk.
The bill places heavy weight on a single, fact-intensive custody test. That raises immediate questions: what technical arrangements constitute "unilateral" ability to obtain data sufficient to initiate a transfer?
Does running a hosted node that stores encrypted private key shards, providing backup/recovery services, or facilitating signature aggregation create control? The statute ties the exemption to both legal rights and technical ability, which leaves room for widely varying factual determinations in courts or by agencies.
Proving the absence of control will likely require technical audits, contractual limitations, and architecture choices that are costly and may not be definitive in litigation.
The definition of "digital asset" narrows coverage to assets that can be exclusively possessed and transferred person-to-person without reliance on intermediaries—language intended to exclude tokenized claims or off‑chain obligations. But many real-world tokens confer mixed rights (custodial arrangements, off-chain settlement, or representational claims), and the statute does not say how mixed instruments (or tokenized securities) fit.
The state‑law clause further complicates enforcement: while states may enact or enforce consistent laws, the bill bars causes of action under inconsistent laws—creating uncertainty over consumer-protection statutes, restitution remedies, or state enforcement theories that don't squarely map to the federal test. Finally, the bill does not address how federal agencies (FinCEN, SEC, CFTC) should apply this safe harbor when pursuing AML, securities, or commodity enforcement, leaving potential for regulatory mismatch and forum shopping.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.