Stack Diagram

Three architectures. Five layers deep.

Build LLC section-cut comparison of HQLA management infrastructure across a unified ledger (Agorá), multi-chain (current state), and traditional pre-tokenization. Solid borders mean code-enforced — the mechanism cannot be bypassed. Dashed borders mean policy-enforced — compliance depends on an external actor.

COMPLIANCE DEPTH →HQLA Infrastructure — Stack ComparisonBuild LLC section-cut style · 5 architectural layers · Code-enforced vs. policy-enforcedA-401 · SECTION CUTStableHQLA · StablecoinAtlasL5ApplicationL4ProtocolL3ExecutionL2ConsensusL1NetworkSTATE TRANSITION · L3 EXECUTIONUnified Ledger (Agorá)wCBDC + Tokenized DepositsMulti-Chain (Current State)Fragmented HQLA PoolsTraditional (Pre-Tokenization)Physical Bonds + RTGS CashTreasury DashboardLCR Alert SystemJIT Liquidity EngineCollateral OracleAtomic Collateral SwapHaircut Smart ContractCentral Bank ConsensusUnified Settlement RailManual RebalancingEnd-of-Day LCRBridge AggregatorOff-Chain PricingPer-Chain EscrowRepo Smart ContractOpen ValidatorsMultiple P2P NetworksTreasury WorkstationMonthly LCR FilingTri-Party Repo AgentCustodian SettlementBatch NettingManual Haircut CalcCentral CounterpartyRTGS / SWIFTLEGENDIdentityDiscoveryReservesTransferExecutionTokenReportingGateMonitorObligationCode-enforced (solid)Policy-enforced (dashed)

Read the borders — Solid = code-enforced (cannot be bypassed). Dashed = policy-enforced (depends on external actor). The Traditional column is entirely dashed. The Unified Ledger is almost entirely solid. This is the compliance-depth argument: tokenized HQLA doesn't just improve liquidity — it shifts enforcement from trust to cryptographic proof.

Journey Map

Eight stages. One atomic collateral swap.

How it works: Every HQLA collateral swap mapped through the STP 8-stage sequence.

Gates accumulate — before the state change at S6, each checkpoint must pass
Obligations radiate — after settlement, reporting duties fire asynchronously
Hover any checkpoint — see the protocol, actor, and enforcement type

HQLA Collateral Swap — Settlement Journey MapSTP 8-stage sequence · Gates accumulate before S6 state change · Obligations radiate afterHQLA ROUTEGateMonitorObligationSCREENING ZONESTATE TRANSITION← GATES ACCUMULATEOBLIGATIONS RADIATE →S1IntentBank TreasurerS2IdentityKYB ValidatorS3DiscoveryReserve OracleS4NegotiationHaircut EngineS5TransportCCTP v2 / BridgeS6AuthorizationLCR MonitorS7FacilitationAtomic SwapS8FinalityCompliance Layer

The Problem

Netting vs. Atomic: The Liquidity Gap

The Netting Advantage

Batch compression hides the true HQLA cost

Bank A owes Bank B $100M. Bank B owes Bank A $95M. Net settlement: $5M. HQLA needed: minimal. This is how traditional FMIs keep liquidity requirements low — batch netting compresses gross obligations.

The Atomic Demand

Every trade needs 100% HQLA live on the ledger

In atomic DvP, every trade settles instantly and individually. That same $100M trade requires $100M in HQLA live on the ledger. No netting. No end-of-day compression. Intraday liquidity demand spikes 10-20× compared to netted systems.

The Fragmentation Trap

Right assets, wrong ledger

A bank has $10B in HQLA — but it's split across ten Digital FMIs. A major trade arrives on Ledger C, where only $200M is parked. Trade fails. This is liquidity fragmentation — the treasurer's nightmare in a multi-ledger world.

Dimension	Netted (Traditional)	Atomic (On-Chain)
HQLA per trade	Netted obligation only (~5%)	Full gross amount (100%)
Intraday demand	Compressed via multilateral net	10-20× higher per trade
Settlement window	End-of-day batch	Real-time, per-transaction
Liquidity location	Single CSD/RTGS	Fragmented across FMIs
Collateral mobility	Manual repo, T+1	Tokenized, atomic, cross-chain
LCR monitoring	End-of-day calculation	Real-time on-chain oracle
HQLA composition	Physical bonds, cash reserves	Tokenized Treasuries, wCBDC, MMF shares
Collateral rehypoth.	Opaque chain of custody	On-chain transparency, view keys

Proof of Concept

Three chains. Three HQLA strategies. Running code.

What to know: Each POC demonstrates a different HQLA management strategy for atomic settlement.

Base (Coinbase) — JIT collateral swap using ERC-4626 tokenized Treasury vaults
Arc (Circle) — Real-time LCR monitoring with confidential balances
CCTP v2 Bridge — Cross-ledger HQLA rebalancing to solve fragmentation

HQLA Proof-of-Concept Exercises

Three tokenized Treasury scenarios demonstrating settlement integrity, regulatory clarity, and ledger optimization.

Chain

Base L2 (Coinbase)

Status

Simulated · ERC-4626 Vault

Buyer

Bank Treasury Desk

Protocol

ERC-4626 + x402 + Basel III Haircut

Step Flow

Treasury system detects shortfall

MonitorCode0ms

AI-driven treasury management system detects upcoming DvP trade on Base will breach LCR minimum. Triggers JIT rebalancing.

Institutional KYB gate

GateCode15ms

Bank counterparty verified via institutional KYB. Permissioned access to tokenized Treasury vault. Only Basel III entities proceed.

HQLA eligibility verified

GateCode50ms

On-chain oracle confirms tokenized Treasury is Level 1 HQLA. Zero haircut applied. ERC-4626 vault shares represent the underlying bond.

LCR ratio pre-check

GateCode20ms

Smart contract calculates post-swap LCR ratio. Must remain ≥100%. If swap would breach, gate blocks and alerts treasury desk.

Atomic collateral swap

GateCode2s

Single transaction: ERC-4626 vault shares (tokenized Treasury) swapped for USDC. Both legs atomic on Base. x402 conditional payment.

LCR reporting obligation

ObligationPolicyasync

Post-swap LCR recalculated. Intraday liquidity report filed. Basel III NSFR update triggered. Regulatory view key for audit.

Implementation

1// JIT Collateral Swap — Cloudflare Worker on Base
2import { Erc4626Vault } from "@openzeppelin/contracts";
3
4export default {
async fetch(request: Request): Promise<Response> {
  const treasury = await getTreasuryPosition();
7
  // Step 1: Detect LCR shortfall
  const lcrRatio = treasury.hqla / treasury.netCashOutflows;
  if (lcrRatio >= 1.0) {
    return Response.json({ status: "healthy", lcr: lcrRatio });
  }
13
  // Step 2: KYB verification
  const kyb = await verifyInstitutionalKYB(request);
  if (!kyb.verified) throw new Error("KYB gate: not authorized");
17
  // Step 3: Verify HQLA eligibility
  const bond = await queryHqlaOracle({
    asset: "UST-10Y-2026",
    standard: "ERC-4626",
    vault: TREASURY_VAULT_ADDRESS,
  });
24
  const haircut = getBaselHaircut(bond.hqlaLevel);
26
  // Step 4: Pre-check post-swap LCR
  const postSwapLcr = calculateLCR({
    currentHqla: treasury.hqla,
    collateralValue: bond.faceValue * (1 - haircut),
    cashReceived: bond.faceValue,
    outflows: treasury.netCashOutflows,
  });
34
  if (postSwapLcr < 1.0) {
    return Response.json({ status: "blocked", reason: "LCR breach" });
  }
38
  // Step 5: Atomic swap — vault shares for USDC
  const swap = await atomicCollateralSwap({
    vaultShares: bond.shares,
    usdcAmount: bond.faceValue,
    escrowContract: HQLA_ESCROW,
    windowBlocks: 6,
  });
46
  return Response.json({
    status: "settled",
    txHash: swap.txHash,
    newLcr: postSwapLcr,
    hqlaLevel: bond.hqlaLevel,
    haircut: haircut,
    settlement: "atomic",
  });
},
56};

How to use: Click tabs to switch between POC exercises. The step flow animates automatically (1200ms per step, 2 cycles). Click any step to pause the animation.

Note: Simulated and planned exercises are demonstrations. Live exercises reflect deployed consensus state.

Reading the shapes — Each step uses the Two-Model System's compliance encoding. Hexagons are gates (pre-conditions that block if they fail). Circles are monitors (concurrent observation). Diamonds are obligations (post-settlement reporting). Filled shapes = code-enforced. Hollow/dashed = policy-enforced. Colors map to compliance domains: blue = Identity, purple = Discovery, amber = Reserves, teal = Transfer, orange = Execution, green = Token, rose = Reporting.

Compliance Architecture

Every checkpoint maps to a regulation.

The big picture: Atomic HQLA management isn't just faster collateral — it's a compliance upgrade.

Traditional enforcement — policy-enforced, depends on intermediaries acting correctly
Atomic enforcement — code-enforced, compliance gates execute in the same transaction as settlement

Domain	Regulation	Traditional Enforcement	Atomic HQLA Enforcement	Checkpoint
Identity (T6)	Basel III CRE 20 · GENIUS Act §4(a)(1)	Bank KYB (policy)	Institutional KYB gate — permissioned validator, code-enforced	⬢ Gate
Discovery (T4)	Basel III LCR 20.1 · HQLA Eligibility	Manual asset classification (policy)	On-chain HQLA oracle — Level 1/2A/2B attested cryptographically	⬢ Gate
Reserves (T2)	Basel III LCR 50 · Haircut Schedule	Risk team spreadsheet (policy)	Smart contract haircut — compiled into swap logic, code-enforced	⬢ Gate
Transfer (T5)	CPMI-IOSCO PFMI Principle 7	T+1 via custodian (policy)	CCTP atomic bridge — cross-ledger in seconds, code-enforced	● Monitor
Execution (T3)	Basel III LCR 40 · Intraday Monitoring	End-of-day LCR calc (policy)	Real-time LCR oracle — continuous on-chain, code-enforced	⬢ Gate
Token (T1)	CPMI-IOSCO PFMI Principle 8	Batch settlement (policy)	Atomic swap — tokenized Treasury ↔ cash in one tx, code-enforced	⬢ Gate
Reporting (T7)	Basel III Pillar 3 · GENIUS Act §4(a)(3)	Monthly/quarterly LCR filing (policy)	Post-swap obligation fires — real-time regulatory reporting	◇ Obligation

Code-enforced vs. policy-enforced — This is the core distinction the Two-Model System makes visible. Solid borders on the Stack Diagram mean code-enforced (the mechanism cannot be bypassed). Dashed borders mean policy-enforced (compliance depends on an external actor). Traditional HQLA management is entirely policy-enforced. Tokenized HQLA shifts enforcement from spreadsheets to smart contracts. See StablecoinAtlas for the full compliance checkpoint taxonomy.

Institutional Signals

Who's building tokenized HQLA infrastructure.

Entity	Initiative	HQLA Relevance	Status
BIS (7 central banks)	Project Agorá — unified ledger	wCBDC + tokenized deposits on single platform. Eliminates fragmentation.	H1 2026 REPORT
DTCC	DTC Tokenization Services	Tokenized Treasuries as HQLA. 1.4M securities in custody.	2026 LAUNCH
BlackRock	BUIDL — tokenized Treasury fund	$500M+ tokenized money market fund. Institutional HQLA vehicle.	LIVE
Franklin Templeton	BENJI — on-chain money market	Tokenized US Gov MMF. HQLA-eligible. On-chain NAV.	LIVE
Broadridge + Fnality	Intraday Repo on DLT	Real-time secured lending with wCBDC settlement.	PRODUCTION
ECB + HQLAx	Blockchain securities lending	DLT-based collateral transfer for euro-area HQLA.	PILOT
Federal Reserve	Basel III Endgame (July 2025)	LCR phase-in: 100% HQLA coverage for >$100B banks. 3-year transition.	ACTIVE

The Vocabulary Arc

Charter → HQLA → DvP

Charter grants the license. HQLA provides the fuel. DvP is the engine. This site sits in the middle of a three-property vertical mapping the full infrastructure from regulatory approval to atomic settlement execution.

StableCharter

OCC / State charter pathways for stablecoin issuers

Federal and state regulatory frameworks for stablecoin issuance. Charter types, capital requirements, and compliance pathways under the GENIUS Act.

StableHQLA

HQLA management infrastructure for atomic settlement

This site. Where tokenized Treasuries, JIT liquidity, and Basel III compliance meet multi-chain settlement infrastructure.

You are here

AtomicDVP

Delivery vs. Payment settlement on ZK-finality chains

Atomic delivery-versus-payment. Where HQLA meets the settlement engine. Live POCs on Base, Arc, and ACK.

This Site

Built for bank treasurers. Powered by developer infrastructure.

The bottom line: StableHQLA.com speaks TradFi — LCR, HQLA, haircuts, intraday liquidity.

The content — maps to developer infrastructure on ZK-finality chains
The transport — Cloudflare Pages with post-quantum encrypted transport (ML-KEM)

HQLA Infrastructure Reference ML-KEM Transport · Cloudflare Pages

Atomic settlement eats liquidity for breakfast.