EligibleAsset — The Convergence Identity for Regulatory-Grade Reserve Classification

Eligible Asset Standard: Twin-Bundle: EligibleAsset.com + EligibleAsset.eth

Pillar 1: Why “Eligible Asset” Is the Most Critical Term in U.S. Banking Infrastructure 2026

The term Eligible Asset is not marketing language. Under the GENIUS Act (12 U.S.C. § 5903) and the OCC Proposed Rules (Federal Register Vol. 91, No. 40, March 2, 2026), it is a legally binding classification that determines which assets a Permitted Payment Stablecoin Issuer may hold as reserves. The OCC defines eight exclusive categories:

1. Federal Reserve balances
2. U.S. Treasury bills, notes, or bonds with a remaining maturity of 93 days or less
3. Overnight repurchase agreements backed by T-Bills (93-day maturity)
4. Tri-party or centrally cleared reverse repurchase agreements
5. Registered Government Money Market Funds
6. Any similarly liquid federal government asset approved by the OCC
7. Tokenized versions of categories 1–6 — subject to full regulatory compliance and OCC pre-approval (§ 15.11(b)(8))

Category 7 is the inflection point for the entire digital asset industry. The OCC explicitly states that institutions seeking clarity on whether a specific tokenized asset qualifies must request a formal opinion. Without a machine-readable, on-chain source of truth for this classification, Programmable Compliance is impossible — and every automated treasury decision carries unquantified legal risk.

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

Pillar 2: The Eligibility Gap — A Systemic Risk No Treasury Can Afford

The operational challenge for banks and stablecoin issuers in 2026 is not a lack of regulation. It is the speed and verifiability of compliance. A treasury system must know in real time: Is this asset still eligible?

The answer depends on remaining maturity, counterparty credit rating, tokenization status, and OCC approval — parameters that can change daily. Without a dedicated eligibility identity layer, three critical failure modes emerge:

Settlement Failure: An AI agent accepts an asset as collateral that no longer meets OCC § 15.11(b) criteria. The result: cascading Atomic Settlement Efficiency breakdown and exposure to Herstatt risk.

Audit Gap: An examiner cannot trace the eligibility chain on-chain. Real-Time Recon fails. The institution cannot demonstrate compliance at the moment of transaction — a direct violation of OCC supervisory expectations.

Fiduciary Breach: An autonomous agent executes a treasury allocation without a verified eligibility signal. Under the emerging doctrine of Fiduciary Agentic Responsibility, the institution — not the algorithm — bears the liability.

EligibleAsset.com provides the institutional API layer: a continuously updated, OCC-mapped classification registry accessible to compliance teams and treasury systems. EligibleAsset.eth translates this registry into an on-chain oracle — queryable by smart contracts, stablecoin protocols, and AI agents at the moment of execution, with cryptographic proof of the eligibility state at that exact block timestamp.

Source: BIS — The role of tokenisation in the monetary system, 2024/2025 — The BIS framework confirms: atomic settlement processes require machine-readable asset classification as a precondition for Unified Ledger Integration.

Pillar 3: EligibleAsset as the Gateway Layer of the PillarsX Infrastructure Stack

No asset can be atomically settled, tokenized, or posted as collateral before its eligibility is established. Within the PillarsX architecture, EligibleAsset.com/.eth is the mandatory first checkpoint — the gate through which every institutional transaction must pass.

EligibleAsset.eth        →  Eligibility verified [Qualified Digital Asset Custody]
        ↓
fhecollateral.com/.eth   →  Privacy-preserving collateral lock [Confidential Computing / FHE]
        ↓
mcpsettle.com/.eth       →  Atomic T0 execution [Atomic Settlement Efficiency]
        ↓
liqrecon.com/.eth        →  Instant position reconciliation [Real-Time Recon]
        ↓
dtaverify.com            →  Audit trail & proof of eligibility [Digital Transfer Agent]

This is Operational Resilience by design: every node in the chain has a verified identity in both Web2 and Web3.

Remove EligibleAsset from this stack and every downstream process operates on unverified inputs — a condition no

regulated institution can accept.

Strategic Constellations & Bundle Potential

Bundle A — “The Compliance Stack” · For Permitted Payment Stablecoin Issuers (OCC § 15.x)

Designed for banks and fintech institutions pursuing a stablecoin issuance license under the GENIUS Act. Each domain addresses a discrete regulatory checkpoint:

Bundle B — “The Agentic Treasury” · For AI-Driven Treasury Systems

Addresses the emerging requirement for Fiduciary Agentic Responsibility: AI agents allocating capital on behalf of institutions must prove every decision was based on verified, eligible assets — at the exact moment of execution.

Bundle C — “The Tokenization Gateway” · For RWA Tokenization under OCC § 15.11(b)(8)

The OCC explicitly permits tokenized reserve assets — but requires a formal pre-approval process. This bundle positions PillarsX as the reference infrastructure for that workflow:

→ Related: PillarsX / PermittedReserves — EligibleAsset defines the category. PermittedReserves manages the live status. → Related: PillarsX / ProgrammableCompliance — When EligibleAsset establishes the truth, ProgrammableCompliance ensures it is automatically enforced.