Find the Right GRC Solution

Search and compare GRC technology built for the problems you’re trying to solve

Fed Explores Classifying Tokenized Deposits, Money Funds, and Stablecoins in Monetary Aggregates

Fed Explores Classifying Tokenized Deposits, Money Funds, and Stablecoins in Monetary Aggregates

By
Key Takeaways
  • The Federal Reserve Board published independent research outlining an analytical framework for potentially incorporating tokenized deposits, tokenized money market funds, and GENIUS Act-compliant payment stablecoins into official U.S.
  • monetary aggregates (M1/M2).
  • While not policy, this signals the Fed's forward-looking posture on digital asset classification and foreshadows potential future data reporting requirements for banks, fund issuers, and stablecoin issuers.
Deep Dive

This FEDS Note is explicitly framed as independent research rather than formal policy, but it carries significant signaling value for compliance teams at banks, broker-dealers, asset managers, and stablecoin issuers. The authors propose a two-part analytical approach—functional classification (medium of exchange vs. store of value) and four practical measurement considerations (data availability, reporting infrastructure, double-counting risk, and geographic scope)—to evaluate whether emerging digital assets should be folded into the Fed's M1 and M2 money supply measures. This matters because monetary aggregate classification can influence how assets are perceived by regulators, policymakers, and market participants, and may eventually drive new or modified reporting obligations.

Three asset classes are analyzed. Tokenized deposits, already commingled with traditional deposits in existing bank reporting (FR 2900, Call Reports), are deemed likely already captured in M1 or M2 depending on deposit type, with no immediate reporting gap—though the note flags that separately tracking tokenized deposits could help regulators monitor blockchain-based banking adoption. Tokenized MMFs are similarly already captured within non-M1 M2 via existing ICI reporting, but the note flags a potential future reclassification to M1 if medium-of-exchange use cases (e.g., collateral management, on-chain lending) become dominant. Payment stablecoins issued under the GENIUS Act present the most significant gap: they are not currently included in any aggregate, and the note identifies unresolved issues around standardized reporting formats, the reporting chain (direct to the Fed vs. through OCC or state regulators), double-counting of reserve assets already captured elsewhere (Treasuries, bank deposits, government MMFs), and challenges isolating U.S. versus global circulation on public blockchains.

No binding deadlines or compliance mandates are introduced by this note itself. However, it references the GENIUS Act's existing requirement for monthly reserve asset reporting by permitted stablecoin issuers, and a pending OCC proposed rulemaking (OCC Bulletin 2026-3) on redemption timeframes (two business days, extendable to seven under stress conditions). Compliance teams—particularly at banks engaged in tokenized deposit initiatives, MMF sponsors exploring tokenization, and GENIUS Act-licensed stablecoin issuers—should monitor this research stream closely, as it may presage future Fed guidance on H.6 statistical release methodology, data collection standardization, or cross-agency reporting coordination with the OCC and SEC.

From a risk perspective, this note underscores growing regulatory attention to blockchain-based financial instruments and the operational challenge of integrating novel asset classes into legacy reporting frameworks. Firms should proactively assess their own data governance capabilities for tokenized products, anticipate potential future requests for granular reporting that distinguishes tokenized from traditional instruments, and track parallel GENIUS Act implementation and OCC rulemaking developments, as these will likely converge with eventual Fed action on monetary aggregate definitions.

Source: Board of Governors of the Federal Reserve System

Regulatory data powered by Corlytics

Oops! Something went wrong