Share article

So the US "banned the CBDC," and somehow ended up with a cleaner legal path for digital dollars that can be monitored, frozen, and reported anyway. Sure.
That is the core irony critics are circling after the GENIUS Act's passage: the bill draws a bright line against a Federal Reserve issued retail Central Bank Digital Currency (CBDC), while expanding the compliance scaffolding around privately issued stablecoins, the same dollar-pegged tokens that already move tens of billions of dollars in weekly on-chain volume. The surveillance risk, they argue, does not disappear just because the issuer's logo is private-sector instead of federal. [1]

Enjoy articles without ads?

Register for free and get unlimited access to all articles.

What the GENIUS Act actually blocks, and what it does not

The GENIUS Act explicitly bars the Federal Reserve from issuing a CBDC directly to individuals, or indirectly via a third party that would function as the Fed's retail distributor. [2] That design choice aligns neatly with the political framing that a "digital dollar" could become a tool for state control, something President Trump had attacked during the 2024 campaign cycle.
But the bill's critics say the fight was never only about who issues the token. The fight is about what the system requires to use it.

Stablecoins under a formal federal regime are still money-like instruments that:

  • flow through regulated issuers,
  • depend on banking rails for reserves,
  • plug into Bank Secrecy Act (BSA) obligations,
  • and can be conditioned on identity checks and transaction monitoring.

A CBDC ban does not automatically create a privacy win if the substitute product is built on stricter reporting rules than what existed before.

The critique: "private stablecoins" can still become surveillance rails

Aaron Day, a fellow at the Brownstone Institute and a vocal critic of the crypto industry, argues that the stablecoin versus CBDC distinction is mostly branding. The issuer changes, the surveillance outcomes do not.
The point is less about conspiracy and more about plumbing. Whether a token is issued by a central bank or a regulated private entity, the practical levers are similar once the government can mandate compliance at the issuer and banking layers:
  • Know Your Customer (KYC): identity verification tied to wallets, accounts, or customers.
  • Anti-Money Laundering (AML): monitoring patterns, screening addresses, generating alerts.
  • Suspicious Activity Reports (SARs): filings that can be triggered without notifying the subject.
  • Sanctions enforcement: blacklisting and blocking flows linked to designated entities.
  • Records and retention: keeping transaction and customer data accessible for audits and subpoenas.

Day's argument, as summarized in the source reporting, is that people worried about a CBDC are worried about surveillance and control, not the stationery used to print the issuer's name. [3]

The BSA is already the template, stablecoins just scale it on-chain

The US does not need a CBDC to monitor money movement. The BSA framework already requires banks and many financial intermediaries to collect identifying data, keep records, and report certain activity to the government. Stablecoins, once pulled deeper into a federal stablecoin compliance perimeter, can make that framework more continuous and more automated.

A key difference is that stablecoins settle on public blockchains where transactions are:

  • transparent by default, even when identities are not,
  • permanent, because history does not roll off a ledger,
  • and easy to analyze at scale using commercial blockchain analytics tools.

That combination matters. If compliance rules pressure stablecoin issuers and exchanges to link real-world identities to on-chain addresses, the government does not need a new CBDC database to get many of the same outcomes. The linkage can come from regulated chokepoints, then on-chain analysis does the rest.

This is where critics see the "mirage" in the CBDC ban: it blocks a specific institutional form, while allowing an adjacent model to achieve similar monitoring capacity through regulated stablecoin infrastructure.

"Programmability" is not exclusive to CBDCs

CBDC opponents often focus on programmability, meaning money that can be restricted by rule: where it can be spent, who can receive it, and when it expires. Supporters sometimes respond that stablecoins are not programmable in the same way.

That is only partly true.

Even without a central bank wallet, many major stablecoins already contain issuer controls at the smart contract level, including the ability to freeze addresses or block transfers. Those controls exist for compliance reasons, and regulators tend to like them.

A stablecoin regime that pushes more payment activity into a small set of compliant issuers can, in practice, concentrate these controls:

  • Issuer-level freezes can halt funds.
  • Exchange-level controls can prevent conversion back to bank money.
  • Wallet-level KYC can reduce the ability to transact pseudonymously.
  • Whitelisting (allowing only approved addresses) can make open networks behave like permissioned ones.
None of this requires the Federal Reserve to mint a retail CBDC. It requires a stablecoin market structure where "usable at scale" increasingly means "compliant by design."

Supporters say regulation is the point, critics say that is the problem

Backers of GENIUS style stablecoin legislation typically pitch it as consumer protection plus market clarity: reserve requirements, audits, redemption rights, and clear issuer standards. Senate Banking materials and broader bill commentary have framed the approach as a way to make dollar-pegged tokens safer and more mainstream. [4]

Critics are not disputing that guardrails reduce certain risks. They are disputing the tradeoff.

A stablecoin that is safer because it sits inside a reporting-heavy regime may also be easier to monitor, and easier to control. When every major on-ramp requires identity, and every major issuer must run surveillance and reporting, "private" starts to look like a procurement decision, not a civil liberties safeguard.

Takeaways (plain English version)

  • The CBDC ban is real, but narrow. It blocks the Fed from issuing a retail CBDC, not the broader emergence of state-shaped digital dollars.
  • Stablecoins can deliver similar surveillance outcomes. Especially when identity is linked to addresses via exchanges, issuers, or wallet providers.
  • Existing laws do heavy lifting. BSA and related rules already enable extensive monitoring, stablecoins can increase coverage and speed.
  • Issuer controls are a quiet policy lever. Freeze and blacklist functions are not theoretical, they already exist in major stablecoin contracts.

What to watch next (because the details always land here)

  1. Implementation rules and definitions. The practical impact depends on how regulators define key terms like "issuer," "custodian," and which entities fall under money services business style obligations. [5]
  2. Wallet compliance creep. Watch whether regulated stablecoins effectively require KYC at the wallet layer, either through whitelisting, "verified address" programs, or intermediary mandates.
  3. Expansion of reporting expectations. FinCEN guidance, enforcement actions, and bank examiner priorities will signal whether stablecoin transactions get treated more like cash, wires, or something stricter.
  4. Concentration among issuers. If compliance costs push the market toward a small group of large issuers, surveillance and control become easier to standardize.
  5. Privacy tech response. Increased monitoring pressure usually produces demand for privacy-preserving tooling (not necessarily illicit), such as selective disclosure identity systems or cryptographic privacy layers. Whether regulators tolerate those tools is the tell.

The GENIUS Act may keep "CBDC" off the label. Critics are asking whether the country still gets the same product, just shipped in different packaging, with better PR and the same receipts.