A second institutional tokenisation rail is forming on a timeline parallel to the DTCC July 2026 launch — a shared tokenised-deposit network operated by The Clearing House, targeting first-half 2027. It is governed by banking-supervisory and payment-system law, runs 24/7, and is built across multiple competing institutions on one shared rail. The Layer 5 governance vacancy is structurally wider here than in Cohort A.
Two complementary pipelines, partially shared and partially distinct control content, strengthening the platform's overall defensibility narrative.
| Dimension | Cohort A — Tokenised securities | Cohort B — Tokenised deposits |
|---|---|---|
| Asset class | Tokenised securities | Bank deposit liabilities (deposit tokens) |
| Anchor catalyst | DTCC tokenisation launch | TCH shared deposit network (announced Jun 2026) |
| Governing law | Securities law (SEC / FINRA, custody) | Banking + payment-system law (BSA/AML, OFAC, FDIC, Reg HH / PFMI) |
| Rail operator(s) | DTCC · Canton · Euroclear · Hyperledger | The Clearing House · BNY · Cari Network · DBS / Kinexys |
| Launch horizon | July 2026 | H1 2027 (no vendor selected) |
| Rules maturity | Maturing — frameworks largely exist | Undefined — no GENIUS-equivalent; FDIC / AML unconfirmed |
| Settlement cadence | Periodic / cycle-driven | 24/7 / always-on |
| Structure | Operator-centric | Multi-bank consortium (governance diffuse) |
| Prospect access | Issuer- and operator-led | Consortium banks + peer base |
| Layer 5 gap | Single-operator neutrality gap | Consortium neutrality gap (wider) |
The shared-rail framing is strongest when the cohort is shown as a category. The TCH network is the anchor catalyst; BNY, Cari, DBS / Kinexys, and JPM Coin are already in flight.
No competing participant bank will accept another's governance layer over a shared rail, and the operator is a neutral payments utility, not a GRC product vendor. A neutral third-party governance-and-assurance fabric is structurally required — not merely useful.
No GENIUS-Act-equivalent exists for tokenised deposits. Regulators appear to treat them as an evolution of existing deposit law. FDIC-insurance status and BSA/AML expectations remain unconfirmed as of mid-2026; CSBS has formally asked the agencies for clarity.
An H1 2027 launch with no blockchain vendor yet selected gives a longer embedding window than DTCC's July 2026 horizon. The undefined-rules state is exactly when a governance-infrastructure provider can shape the eventual standard.
Warm-relationship pathways into the cohort are documented in the engagement vault and discussed on a private basis; named institutions are not cited on this surface pending verification.
Each delta maps to existing infrastructure where possible — shared evidence engine, 3LOD workflow, cross-border regulatory mapping engine — and is specified as an extension, not a fork.
Tokenised deposits sit in a different regulatory body than securities. A banking-supervisory control library is needed alongside the existing securities / crypto-asset set.
Maps to · Extends the framework-library architecture (60+ jurisdiction mapping). Reuses the control-object schema.
The 37-module baseline assumes single-institution deployment. A shared rail with competing participants plus a neutral operator requires network governance, not institutional governance. This is the differentiated build.
Maps to · Extends the 3LOD workflow and evidence engine to a network scope. New tenancy model.
Securities settlement tolerates point-in-time attestation; an always-on deposit rail does not. 'The bridge' (where tokens mint and burn against actual deposits) is the proof point for the FDIC-insurance and not-a-stablecoin claims.
Maps to · Evidence engine extension (streaming mode); new reconciliation control set.
The FDIC has signalled it will look through labels — a digital asset that mirrors the definition of a deposit will be treated as one regardless of naming. Continuous characterisation evidence is a governance requirement, not a marketing question.
Maps to · Cross-border regulatory mapping engine — deposit-token extension.
With the CSBS clarity request open (Nov 2025) and NPRMs mid-flight (Apr 2026), supplying the attestation format the rules will eventually require is the strongest form of regulator-side embedding. The product → standard path.
Maps to · New external-facing surface on the evidence / attestation layer; reuses existing supervisor read-only patterns.
24/7 deposit-rail screening will run on AI transaction-monitoring models. Proposed stablecoin AML/sanctions rules already require independent audit and note that internal audits often lack independence — directly relevant to the AI screening deposit-token flows.
Maps to · AI Assurance OS (existing) — pointed at the Cohort B monitoring stack.
24/7 deposit rails break the assumption that LCR / NSFR / intraday-liquidity is a periodic calculation. The CSBS clarity request named liquidity risk as a priority; the Liquidity Resilience Engine already covers Basel III periodically — a Cohort B extension would stream intraday net positions and concentration across participants.
Maps to · Liquidity Resilience Engine extension — depends on Δ2 (network tenancy) and Δ3 (streaming evidence).
Δ2 (network governance) is the critical-path dependency for Δ3, Δ6, and Δ7 at network scope.
Per Cabier's audit-ready standard, the following must be verified before any of this content appears in client-facing BD materials. Status flags below are maintained in source and updated as each item clears.
Market and regulatory facts reflect reporting available as of June 2026 and require primary-source confirmation before client-facing use.
Cohort B working sessions are scheduled with consortium participants, operators, and supervisor counterparties on a private basis. Please reference this brief in your enquiry.