Wholesale Settlement &
Tokenized Cash Infrastructure

1. TARGET2, TIPS & RT1 Core Stack

The Eurosystem’s settlement infrastructure relies on a tiered system designed for large-value payments and instant retail clearing. At the core is TARGET2 (T2), a Real-Time Gross Settlement (RTGS) system processing transactions in risk-free central bank money (CeBM). TARGET2 operates on a strict schedule, closing on weekends and public holidays, creating a structural operating mismatch with the 24/7/365 cycle of decentralized financial markets.

To address real-time retail settlement, TIPS (TARGET Instant Payment Settlement) operates continuously on a 24/7/365 basis, leveraging central bank accounts. While TIPS guarantees instant finality in CeBM, it is architecturally constrained by transaction caps (standardized at €100,000) and optimized for low-value, high-volume retail transactions rather than high-value, multi-party wholesale financial settlements.

Separately, RT1 (operated by EBA Clearing) provides a commercial bank clearing alternative. Operating under SEPA Instant Credit Transfer rules, RT1 clears commercial bank money (CoBM), requiring participants to hold liquidity buffers at the Eurosystem to secure net settlement finality, introducing additional credit risk and operational complexity.

2. The ECB Trigger Solution

To resolve the gap between DLT-native assets (like tokenized bonds) and central bank money without minting a native wholesale CBDC (wCBDC) on public ledgers, the Deutsche Bundesbank introduced the Trigger Solution. Adopted by the Eurosystem for its wholesale trials, this interoperability bridge links DLT networks to legacy RTGS systems via an API gateway.

The Trigger Solution does not issue central bank money directly on the DLT ledger. Instead, when a transaction occurs on the DLT network (e.g., an EIB bond token transfer), the smart contract locks the asset and emits an execution event. The Trigger Oracle reads this event, translates the instruction into an ISO 20022 message, and submits it to TARGET2. T2 processes the cash leg (debiting the buyer's account and crediting the seller's). Once settled, T2 confirms back to the oracle, which triggers the release of the locked asset on the DLT.

This approach avoids complex legal questions regarding the custodian status of central bank money on distributed ledgers. However, it relies heavily on the oracle infrastructure, introduces potential API latency, and does not natively support complex smart contract functions (like on-chain multi-party liquidity pools) because the cash leg remains isolated in a centralized database.

3. ECB Trigger API / TARGET2 DvP Workflow

The diagram below illustrates the technical step-by-step API flow of the ECB Trigger Solution, bridging a DLT bond transaction (e.g., European Investment Bank digital bond issuances on HSBC Orion or Canton Network) with cash settlement on TARGET2.

4. The Unified Ledger Hypothesis (BIS)

The Bank for International Settlements (BIS) has proposed a more integrated conceptual framework: the Unified Ledger hypothesis. In this conceptual model, wholesale central bank money (wCBDC), commercial bank tokenized deposits, and tokenized real-world assets (RWAs) are co-located on a single shared, programmable database platform.

The Unified Ledger hypothesis eliminates the translation lag and oracle security risks of trigger models. By having the cash leg and the asset leg exist on the same database, atomic settlement is achieved natively. This allows for complex financial logic—such as automated escrow, dynamic collateral margin calls, and multi-party atomic clearing—without exposing participants to intermediate settlement delays or bridge exploits.

However, the Unified Ledger hypothesis faces massive political and structural hurdles. It requires commercial banks and central banks to participate in a shared, multi-tenant database infrastructure, raising questions of national sovereignty, system governance, and the operational independence of commercial institutions.

5. Comparative Settlement Rails Matrix

A detailed technical comparison of the three primary tokenized settlement cash models available to institutional market participants. Note the asymmetric, non-uniform regulatory and operational gaps reflecting real-world market design.

6. Intraday Liquidity & Collateral Implications

Bridging DLT networks that run 24/7/365 with legacy RTGS systems like TARGET2 (which close during weekends and holidays) introduces significant liquidity fragmentation and **bridging friction**.

When a DLT-native asset is traded on a Saturday, the cash leg cannot settle in central bank money via TARGET2 until Monday morning. To maintain continuous atomic DvP settlement, participants are forced to adopt one of two inefficient strategies:

• Pre-Funding: Banks must lock up liquidity by pre-funding specialized RTGS accounts prior to weekend closures, effectively locking up capital that could otherwise be deployed elsewhere.
• HQLA Collateralization: Banks can pledge High-Quality Liquid Assets (HQLA) like government bonds to secure intraday credit lines, but this locks up collateral buffers, reducing overall velocity.

This cash-locking effect reduces the overall velocity of capital, creating a structural cost premium for 24/7 institutional trading. Until central banks provide continuous, interest-bearing wholesale wCBDC accounts that operate 24/7/365, liquidity velocity will remain structurally constrained.

7. Operational & Structural Constraints

The deployment of digital sovereign money structures introduces fundamental trade-offs between system safety, compliance, and user adoption.

A. Privacy vs. Compliance (GDPR & ZKPs)

Wholesale settlements on shared ledgers must guarantee absolute transaction confidentiality to protect proprietary trading strategies and comply with banking secrecy laws (such as GDPR). However, regulators require auditability to prevent anti-money laundering (AML). Central banks are exploring Zero-Knowledge Proofs (ZKPs) to hide transaction amounts and counterparties while proving compliance cryptographically. Yet, current ZKP systems introduce high computational overhead and processing latency, conflicting with high-speed RTGS requirements.

B. Offline Settlement Challenges

In retail contexts, digital currency must function offline during power outages or connectivity failures. Implementing offline settlement requires tamper-resistant hardware (e.g., Secure Enclaves or HSMs on mobile devices) that can verify and record transactions locally. Preventing the "double-spending" of digital cash without a real-time central ledger remains an open cryptographic challenge, limiting early digital euro rollouts to connected devices.

C. Bank Disintermediation & Flight to Safety

In times of systemic financial stress, corporate and retail depositors might attempt to instantly migrate their funds from commercial banks (exposed to fractional reserve risk) to risk-free wholesale wCBDC or retail digital euro accounts. To prevent sudden bank runs and the loss of commercial bank credit creation, the ECB has proposed strict retail holding limits (e.g., a cap of €3,000 per citizen) and highly restricted access for wholesale entities, limiting the systemic utility of the network.