The U.S. Senate moved forward with an amendment to the 21st Century ROAD to Housing Act that would temporarily block the Federal Reserve from issuing a retail CBDC, codified as Section 10 and set to expire on December 31, 2030. The practical message is that Congress is drawing a time-boxed line: no broadly accessible, Fed-issued digital dollar liability for the rest of the decade unless lawmakers change course.
The amendment advanced on a heavily lopsided cloture vote around March 2–3, 2026, passing 84–6, which signals broad cross-party appetite to pause retail CBDC development. Section 10 is written to be hard to route around: it bars the Fed and member banks from issuing a CBDC or any substantially similar digital asset, whether issued directly or indirectly through intermediaries. The prohibition is explicitly temporary and becomes inoperative after December 31, 2030 unless Congress enacts follow-on legislation.
What Section 10 allows and why “privacy” becomes a design requirement
Section 10 defines a CBDC as a “digital asset denominated in U.S. dollars” that is a direct liability of the Federal Reserve and intended for broad public accessibility. That definition matters because it targets the retail model specifically, leaving space for private-sector dollar tokens while drawing a firm boundary around Fed liabilities.
The amendment includes a carveout that permits private, permissionless, dollar-denominated digital currencies—so long as they preserve cash-like privacy. This carveout is effectively a policy endorsement of market-led digital dollars, but with a condition that becomes operationally thorny: the phrase “preserve cash-like privacy” turns privacy from a marketing feature into a compliance focal point. For stablecoin issuers and infrastructure providers, that language is likely to drive questions about what “privacy-preserving” means in practice, how it can be evidenced, and how it coexists with existing monitoring and reporting obligations.
What teams should do now in practical terms
For payment architects and risk owners, the immediate work is not theoretical. First, product specifications will need clearer privacy claims and sharper evidence trails to align with the carveout’s intent. If privacy is being elevated into the statutory framing, teams will need to be able to demonstrate how their design choices preserve user confidentiality while still supporting auditability. Second, firms need to tighten documentation around proof-of-reserves, custody segregation, and counterparty disclosures, because the overall policy direction favors private rails—but does not excuse weak controls.
The White House has indicated support for the amendment, framing it as protecting privacy and individual liberty. That alignment reduces the near-term risk of executive resistance, even though it does not eliminate the possibility of legislative adjustments before 2030. For market participants, the operational takeaway is that the “public option” for a retail CBDC is deferred, and private stablecoins and dollar-token infrastructure become strategically more important during the window—along with higher expectations around demonstrable privacy and audit-ready governance.