PermittedReserves — The Permitted Reserves Standard for OCC-Compliant Institutions

Pillar 1: The Legal Boundary Every Stablecoin Issuer Must Operate Within

Under the GENIUS Act (12 U.S.C. § 5903) and the OCC Proposed Rules (Federal Register Vol. 91, No. 40, March 2, 2026), the term Permitted Reserves defines the exact boundaries of what a licensed stablecoin issuer may hold as backing assets. This is not a risk management guideline — it is a hard legal perimeter.

The OCC establishes eight exclusive reserve categories under § 15.11(b):

1. Federal Reserve balances
2. U.S. Treasury bills, notes, or bonds — remaining maturity of 93 days or less
3. Overnight repurchase agreements backed by qualifying T-Bills
4. Tri-party or centrally cleared reverse repurchase agreements
5. Registered Government Money Market Funds investing solely in permitted assets
6. Any similarly liquid federal government asset with prior OCC approval
7. Demand deposits at insured depository institutions — subject to concentration limits
8. Tokenized versions of categories 1–7 — subject to full OCC pre-approval (§ 15.11(b)(8))

Holding any asset outside this list — regardless of its credit quality or market liquidity — constitutes a regulatory violation. The Permitted Reserves Standard is therefore the single most critical compliance checkpoint for any institution operating under the GENIUS Act framework.

Source: OCC Proposed Rules – Permitted Payment Stablecoin Issuers, Federal Register, March 2, 2026

Pillar 2: The Reserve Compliance Gap — When Real-Time Status Becomes a Legal Obligation

The challenge for treasury teams in 2026 is not identifying which asset classes are permitted. The OCC list is clear. The challenge is maintaining continuous proof of compliance — across every position, at every moment, under examination-ready conditions.

Three operational failure modes define the risk:

Concentration Drift: The OCC imposes diversification and concentration limits under § 15.11(c). A treasury position that was compliant at 9:00 AM may breach concentration thresholds by 3:00 PM due to market movements. Without continuous Real-Time Recon, the institution cannot detect or document this breach as it occurs.

Tokenized Asset Ambiguity: Category 8 — tokenized reserve assets — requires explicit OCC pre-approval per asset. An institution holding a tokenized T-Bill from an unapproved issuer is in violation, even if the underlying asset is otherwise permitted. Manual tracking of approval status across a dynamic portfolio is operationally untenable.

Audit Trail Failure: OCC examiners require demonstrable Operational Resilience — the ability to reconstruct the reserve composition at any point in time. Paper-based or spreadsheet-driven processes cannot satisfy this requirement at institutional scale.

This is where PermittedReserves.com operates as the institutional registry layer — a continuously updated, OCC-mapped classification and status API for treasury systems. And this is where PermittedReserves.eth becomes indispensable: it translates that registry into an on-chain source of truth, queryable by smart contracts and AI agents at the exact moment of execution — with cryptographic proof of reserve status at that precise block timestamp.

Source: BIS — Tokenisation and the future of money, 2025 — The BIS framework identifies continuous reserve verifiability as a prerequisite for Unified Ledger Integration across institutional settlement systems.

Pillar 3: PermittedReserves as the Compliance Backbone of Institutional Settlement Infrastructure

Every downstream process in a regulated settlement stack depends on one verified input: is this reserve position currently permitted? Without that confirmation, no atomic transaction can be safely initiated, no collateral can be legitimately posted, and no audit trail can be considered complete.

Within the PillarsX infrastructure, PermittedReserves.com/.eth functions as the compliance backbone — the layer that every other component queries before execution:

PermittedReserves.eth      →  Reserve status confirmed [Programmable Compliance]
        ↓
EligibleAsset.eth          →  Asset classification verified [Qualified Digital Asset Custody]
        ↓
fhecollateral.com/.eth     →  Collateral locked with privacy preservation [Confidential Computing]
        ↓
mcpsettle.com/.eth         →  Atomic T0 execution [Atomic Settlement Efficiency]
        ↓
liqrecon.com/.eth          →  Position reconciled [Real-Time Recon]

This architecture embodies Operational Resilience at its deepest level: compliance is not checked once at onboarding — it is verified continuously, at every node, on every transaction.

Your content goes here. Edit or remove this text inline or in the module Content settings. You can also style every aspect of this content in the module Design settings and even apply custom CSS to this text in the module Advanced settings.

Strategic constellation & Bundle Potential

“The Reserve Compliance Stack” · For GENIUS Act Licensing

For institutions building toward a Permitted Payment Stablecoin Issuer license, this bundle covers every mandatory compliance layer from asset classification through audit documentation: