The No Bailout for Crypto Act forbids federal bailouts of entities and systems engaged in digital-asset activities. It sets statutory limits on federal financial assistance and on the use of two emergency backstops often relied on during market stress.
If enacted, the bill would remove a government safety net that market participants often expect in crises. That raises immediate questions for risk management, interconnection with banks, and how regulators will handle contagion without resorting to public funds.
At a Glance
What It Does
The bill defines a set of covered actors and technologies (including digital asset intermediaries and decentralized finance trading protocols) and prohibits federal agencies from providing financial assistance to them for the purpose of preventing failure. It also blocks those actors from accessing emergency Federal Reserve lending under section 13(3) and forbids use of the Exchange Stabilization Fund to benefit them.
Who It Affects
Covered parties include custodial crypto firms, centralized exchanges, entities that provide financial services with respect to digital assets per the Bank Holding Company Act definition, and automated DeFi protocols as defined. Federal banking agencies, the Federal Reserve, and the Treasury would face new statutory constraints when evaluating crisis interventions tied to digital assets.
Why It Matters
By removing key emergency backstops, the bill formalizes a no-rescue policy for crypto exposures, changing incentives for capital planning, counterparty risk, and contingency arrangements. Firms that previously priced rescue risk into business models will have to revise liquidity and counterparty strategies, and regulators will need alternative tools for containing spillovers.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill begins by setting out precise definitions for the covered technologies and actors. It defines blockchain in broadly functional terms, carves out ‘‘decentralized finance trading protocols’’ as systems that execute preprogrammed, non‑discretionary transactions without a custodian, and imports the GENIUS Act and Bank Holding Company Act definitions for several other core terms.
Those definitional choices determine which market participants fall inside the ban and which remain outside it.
The core prohibition directs that no Federal agency may provide ‘‘financial assistance’’ to the enumerated digital‑asset participants to prevent their failure. The statute does not create a new subsidy program; instead, it removes the option of agency relief by statute.
Separately and explicitly, the bill denies covered actors access to emergency lending established under section 13(3) of the Federal Reserve Act and disallows any use of the Exchange Stabilization Fund to benefit them. Those two prohibitions take aim at the two most significant forms of rapid public‑sector liquidity support used in past crises.Finally, the bill includes a narrowly drawn rule of construction preserving the Federal Reserve’s existing authority to lend to depository institutions under section 10B of the Federal Reserve Act.
That carve‑out leaves the Fed’s traditional toolset for lending to banks intact, but it does not create new authority to prop up non‑bank crypto actors. Execution of the statute will turn on how agencies interpret phrases like ‘‘financial assistance’’ and ‘‘with respect to digital asset activities,’’ how the GENIUS Act cross‑references operate in practice, and whether market participants can lawfully rely on bank intermediation to obtain support indirectly.
The Five Things You Need to Know
The bill imports the GENIUS Act definitions and the Bank Holding Company Act’s 4(k)(4) financial‑services definition to identify which firms qualify as covered ‘‘digital asset intermediary’’ or ‘‘financial service provider.’”, It defines ‘‘decentralized finance trading protocol’’ to mean a blockchain system that executes financial transactions via a predetermined, non‑discretionary algorithm without any person maintaining control of users’ digital assets.
The statute bars any Federal agency from providing financial assistance to covered digital‑asset entities or protocols for the purpose of preventing their failure or bankruptcy.
The bill expressly prohibits covered entities from accessing emergency liquidity facilities established under section 13(3) of the Federal Reserve Act.
It forbids use of the Exchange Stabilization Fund (31 U.S.C. 5302) to benefit covered digital‑asset actors but clarifies that the Federal Reserve’s authority to lend to depository institutions under section 10B (12 U.S.C. 347b) remains unchanged.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title — 'No Bailout for Crypto Act'
This single‑line section gives the act its public name. Practically, that signals congressional intent and frames subsequent provisions, which courts may reference when resolving statutory ambiguities about scope or purpose.
Definitions for covered technologies and actors
Section 2(a) supplies the operative definitions the rest of the bill uses. Key inclusions: a functional definition of blockchain; a narrow definition of decentralized finance trading protocols requiring automated, non‑discretionary execution and no custody by a third party; a definition of digital asset intermediary tied to the Bank Holding Company Act’s scope of ‘‘financial services;’’ and cross‑references to the GENIUS Act for terms such as ‘‘digital asset’’ and ‘‘digital asset service provider.’’ Those choices matter because a firm’s classification under these definitions controls whether the ban applies.
Broad prohibition on federal financial assistance
This paragraph prohibits any Federal agency from extending ‘‘financial assistance’’ to the listed covered entities or protocols when the purpose is to prevent their failure or bankruptcy. The wording is preventive: it removes statutory authority for rescue‑style support rather than setting prudential requirements on participants. The phrase ‘‘financial assistance’’ and the clause ‘‘with respect to digital asset activities’’ will likely be the focal point for implementing guidance and litigation over scope.
Ban on access to section 13(3) emergency lending
This subsection prohibits the named digital‑asset actors from using emergency liquidity facilities established under section 13(3) of the Federal Reserve Act. In practice, that prevents the Fed from designing facility terms that could be used by these actors in crisis. Given section 13(3)’s role in past market rescues, this clause removes a rapid liquidity backstop for covered entities.
Prohibition on Exchange Stabilization Fund support
Section 2(d) bars the Treasury from deploying the Exchange Stabilization Fund to benefit covered digital‑asset actors. The ESF has historically been a flexible, sometimes off‑budget tool for FX and emergency support; this clause closes that channel for rescue operations involving the enumerated digital‑asset activities.
Rule of construction preserving Fed lending to banks
This short clause preserves the Federal Reserve’s authority under section 10B to lend to depository institutions. It is a narrow safety valve: while the bill prevents direct public rescues of crypto actors, it leaves unchanged the Fed’s ability to support banks, which could still be used to address banking‑system stress that happens to be connected to digital‑asset exposures.
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
- Federal taxpayers and the federal budget — by statutorily reducing the legal pathways for direct public rescues, the bill limits potential fiscal exposure from future crypto failures.
- Policy makers and some regulators favoring market discipline — the statute codifies a no‑rescue stance that removes moral‑hazard expectations and could incentivize stronger private risk‑management practices.
- Traditional banks and insured depository institutions — their deposit‑insured status and access to Fed 10B lending remain intact, potentially reducing competitive pressure from entities that might otherwise anticipate public backstops.
- Entities selling private‑sector risk‑mitigation (insurers, custodians, clearing services) — clearer no‑rescue rules increase demand for private liquidity lines, insurance, and custodial assurances.
Who Bears the Cost
- Digital‑asset intermediaries and centralized exchanges — they lose a potential public liquidity backstop and may need higher capital, liquidity lines, or private insurance to operate safely.
- DeFi protocol users and counterparties — automated protocols that cannot obtain public liquidity support may experience deeper, faster price collapses and liquidation cascades during stress.
- Non‑bank financial service providers that engage in digital‑asset activities — these firms face higher compliance costs and may be shut out from informal implicit support relationships with regulators.
- Federal agencies and regulators — they inherit interpretive and supervisory burdens to define the statute’s key terms, supervise spillovers into the banking system, and design non‑rescue containment strategies.
- Creditors and investors in crypto firms — removing public backstops increases the probability of creditor losses in insolvency and raises the cost of capital for the sector.
Key Issues
The Core Tension
The central dilemma is simple and sharp: Congress can choose to protect taxpayers by eliminating public rescue options for crypto actors, thereby enforcing market discipline, but doing so increases the risk that failures will transmit to banks, investors, and the broader financial system — creating pressure for ad hoc interventions that the statute seeks to forbid.
The bill advances a clear policy: no statutory bailouts for specified crypto actors. But that clarity shifts complexity into the margins.
The text relies heavily on defined terms and cross‑references (the GENIUS Act and the Bank Holding Company Act) to determine who is covered. Small differences in definitions — for example, whether a hybrid custodial model counts as ‘‘control of digital assets’’ or whether a bank that provides crypto custody remains a ‘‘financial service provider with respect to digital asset activities’’ — will drive compliance outcomes and litigation.
Agencies will need to issue detailed guidance to avoid divergent and disruptive interpretations.
A second implementation challenge is circumvention and contagion. The statute bars direct federal assistance to covered actors, but it does not outlaw indirect support routed through depository institutions.
Banks could still receive emergency support under section 10B and use private contracts to provide liquidity to crypto firms, or the market could seek backdoor stabilization using bank intermediaries. That raises both legal questions (what constitutes a benefit ‘‘with respect to digital asset activities’’) and systemic ones: a hard statutory ban may reduce moral hazard but increase the chance of disorderly failures that spill into the banking system, forcing regulators to choose between strict statutory compliance and ad hoc crisis management.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.