DLT Capital Markets Infrastructure
Financial market infrastructure built on distributed ledger technology — enabling atomic DvP settlement, programmable cash legs, and shared-ledger synchronization that replaces the bilateral reconciliation burden of traditional capital markets.
Definition
DLT capital markets infrastructure is financial market infrastructure rebuilt on shared ledgers. It changes how institutions settle trades, synchronize ownership records, move collateral, and achieve finality across counterparties. The technology may be new. The markets it serves are not.
Capital markets are already fully digital — every trade settled through DTCC, every repo cleared through NSCC, every dollar transferred via Fedwire exists as an electronic book entry. What DLT infrastructure changes is the coordination model: from a messaging-and-reconciliation architecture, where each institution maintains a separate copy of the truth and bilateral messages attempt to synchronize those copies, to a shared-state architecture, where the ledger itself is the authoritative record. Digital financial market infrastructure (dFMI) — the BIS category for DLT-native FMI — replaces the synchronization layer with a shared record maintained collectively by network participants. The reconciliation problem does not improve. It is eliminated structurally, because there is no longer a separate copy of the record to reconcile against.
Why traditional infrastructure is operationally expensive
Three costs compound continuously under the legacy model. Settlement latency creates counterparty risk: from execution to settlement — T+1 in the US, T+2 in many international markets — the buyer carries economic exposure to seller default. The operational response is margin infrastructure through a CCP: complex and expensive machinery that exists entirely to manage the principal risk window that a T+0 atomic system eliminates by design.
Reconciliation burden scales with counterparty count and volume. Every bilateral relationship requires a daily cycle — position reconciliation against the custodian, cash reconciliation against the correspondent bank, trade reconciliation against the counterparty. The cost is operations headcount, investigation workflow, and the tail risk of a break that reflects a genuine error rather than a timing difference.
Trapped collateral is a direct consequence of netting and margin posting. Securities pledged as margin through NSCC or posted in a repo are legally encumbered until the position unwinds. The aggregate value of collateral locked in overnight netting cycles is a significant opportunity cost for any firm with large cleared positions.
Traditional FMI vs DLT-native infrastructure — operational comparison
| Attribute | Traditional FMI | DLT-Native Infrastructure |
|---|---|---|
| Settlement cycle | T+1 or T+2 — batch | T+0 — atomic, continuous |
| DvP mechanism | CSD book entry + Fedwire | Smart contract atomic swap |
| Reconciliation | Bilateral — daily, mandatory | Shared ledger — eliminated |
| Cash settlement | Central bank money (CeBM) | CeBM / EMT / stablecoin |
| Collateral management | Tri-party agent — manual | Algorithmic — oracle-driven |
| Finality governance | CSD / CCP declaration | Consensus mechanism + law |
From fragmented stack to single-stack infrastructure
Traditional post-trade operations run on a three-system stack: execution (OMS/EMS), clearing (CCP), and settlement (CSD). Each handoff between systems introduces latency, error risk, and reconciliation burden as trade data traverses three independent institutional environments — each maintaining its own record of each state transition.
Tokenized capital markets infrastructure replaces this with a single-stack architecture: execution, clearing, and settlement collapse into one atomic transaction. There is no CCP in the loop because counterparty risk is eliminated by atomicity — the transaction either completes in full or not at all. There is no CSD delay because the shared ledger is the settlement record. The operational infrastructure that exists to manage gaps between systems — breaks units, fails management, nostro reconciliation — is not improved. It becomes structurally unnecessary.
The most common institutional objection to single-stack infrastructure is liquidity: NSCC netting eliminates more than 95% of gross settlement obligations, and moving to atomic gross settlement appears to require dramatically higher intraday liquidity. Modern dFMI addresses this through on-chain netting algorithms — participants submit multiple atomic legs to a netting smart contract, which calculates net positions across the participant set and settles only the net amounts atomically. The result is T+0 finality with netting efficiency: the same principal risk elimination, without the gross liquidity cost that pure per-trade atomic settlement would impose.
The three-layer architecture: Asset, Cash, and Identity
Blockchain market infrastructure operates across three interdependent layers, each of which must be present for the system to function as regulated post-trade infrastructure.
Asset Layer — securities as tokens. Traditional instruments are tokenized to settle on-chain (equities, bonds, repo positions, fund units) or issued natively on DLT. Each token encodes the economic rights of the underlying instrument — dividend entitlement, coupon schedule, corporate action eligibility — in smart contract logic. A DLT-native bond pays coupons programmatically and maintains its holder register without a transfer agent. The ESMA DLT Pilot Regime has authorized live DLT-native issuance and settlement, with CSD Prague and 21X AG operational as of mid-2025.
Cash Layer — settlement money. The cash leg determines the regulatory standing of the settlement. The tiered reality: CeBM is the gold standard — zero credit risk, PFMI Principle 9 preferred, backed by the sovereign. The Bundesbank Trigger Solution demonstrated CeBM on a DLT rail by connecting Clearstream's D7 to TARGET2. But as of mid-2025, CeBM delivery on DLT rails is limited to bilateral pilot programs operating during bank hours. MiCA-regulated E-Money Tokens — USDC and EURC, classified as EMTs under MiCA Article 48 — are the operational standard available today: reserve-backed, regulated, and running on 24/7 global rails with no bank-hour constraints. The gap between gold standard and operational standard is credit risk (issuer vs. sovereign), not availability. Production dFMI runs on the operational standard while the gold standard matures.
Identity Layer — verified counterparties. Traditional settlement uses the Legal Entity Identifier (LEI) as the primary counterparty reference, but LEI is an off-chain identifier. The verifiable LEI (vLEI) — the GLEIF standard for cryptographically signed institutional identity — enables on-chain compliance verification: AML, sanctions screening, and regulatory authorization status embedded at the infrastructure level. Most current DLT deployments operate through pre-approved wallet address whitelists, which is a governance control. vLEI is the architectural direction that makes the identity layer infrastructure-native rather than manually maintained.
Core use cases: where DLT changes the operational calculus
Securities settlement is the foundational use case. Atomic delivery versus payment eliminates principal risk by design. For traditional instruments tokenized to settle on DLT rails, this converts T+1 counterparty exposure into same-session finality — without the CCP margin infrastructure required to manage the traditional principal risk window. On-chain netting algorithms preserve the liquidity efficiency of net settlement while delivering the finality and risk elimination of atomic execution.
Repo and collateral management is where efficiency gains are most pronounced. In traditional tri-party, a substitution event requires bilateral negotiation and agent processing measured in hours. In algorithmic tri-party, the smart contract executes substitution automatically — querying price oracles for updated valuations, rebalancing the collateral pool within the same block confirmation. Substitution timelines collapse from hours to seconds, freeing billions in trapped collateral. See tokenized collateral repo settlement for operational detail.
Cross-border treasury benefits from 24/7 availability and atomic finality. Traditional cross-border settlement runs through correspondent banking networks with posting latency, nostro reconciliation, and cutoff windows that create overnight funding gaps. Programmable EMTs on continuous DLT rails eliminate the correspondent bank from the chain. See stablecoin settlement and Arc Network for current implementations.
Hybrid reality and the regulatory architecture
The honest assessment of DLT capital markets infrastructure in mid-2025 is that institutional deployment is nascent. ESMA's June 2025 review of the DLT Pilot Regime — the most comprehensive regulatory assessment of live dFMI globally — found that neither CSD Prague nor 21X AG had recorded secondary market transactions on their authorized DLT MIs as of 31 May 2025. Infrastructure authorization has not produced market adoption.
The operational requirement for institutional firms is not DLT-native migration but hybrid capability: managing positions, cash, collateral, and compliance across traditional and DLT rails simultaneously, from a single system of record. The liquidity depth, regulatory certainty, and counterparty universe of NSCC, DTC, Euroclear, and Fedwire are not replicable on DLT infrastructure on any near-term horizon. See hybrid settlement infrastructure for the architectural detail of parallel rail operation.
The regulatory direction is clear even where adoption is not. ESMA's June 2025 report recommends making the DLT Pilot Regime permanent. The UK Digital Securities Sandbox provides a principles-based alternative under which secondary legislation can be disapplied case-by-case. The BIS PFMI framework applies to any dFMI seeking systemic designation — DLT-based infrastructure at scale faces identical oversight standards as traditional CSDs and CCPs. The regulatory question is no longer whether tokenized capital markets infrastructure is permissible. It is how to make it operationally competitive with the institutional trust and liquidity depth of the legacy infrastructure it complements.
Settlement architecture evolution — legacy to atomic
Devancore Glossary · devancore.com
Settlement architecture evolution — legacy to atomic
Devancore Glossary · devancore.com
How it works
DLT capital markets infrastructure reorganizes the traditional post-trade stack — execution system, CCP clearing, and CSD settlement — into a unified architecture built on three functional layers that operate simultaneously. The settlement event represents all three completing in a single transaction.
1. Asset Layer — tokenization and instrument representation
A security enters DLT capital markets infrastructure as a token: a smart contract deployed on a permissioned or public blockchain that represents the economic rights of the underlying instrument. For traditional instruments, tokenization begins with the legal framework: the token must represent the same beneficial ownership claim as the traditional DTCC book entry, with equivalent legal enforceability under applicable securities law. For DLT-native issuances — instruments that never exist in traditional book-entry form — the token is the primary record of ownership from issuance.
Each token carries its ISIN or CUSIP identifier linked to a unified instrument master, its smart contract address on the specific network, and embedded corporate action logic (dividend rate, coupon schedule, early redemption conditions). The instrument master is the bridge between traditional and DLT representations: one record, two potential settlement rails, one economic instrument. When an instruction arrives with a CUSIP, the infrastructure resolves it to the full instrument record including the contract address for any on-chain representation. When an on-chain event arrives with a contract address, it resolves to the CUSIP for regulatory reporting.
2. Cash Layer — programmable settlement medium
The cash leg funds each DvP transaction through the appropriate programmable cash instrument. For institutions with access to CeBM on DLT rails — via CBDC programs or the Bundesbank Trigger Solution — the cash leg transfers as a central bank liability, achieving PFMI Principle 9's preferred settlement standard. For institutions settling via MiCA-regulated EMTs (USDC/EURC), the cash leg transfers on 24/7 global rails as a reserve-backed instrument with settlement finality equivalent to the underlying blockchain's consensus mechanism. The selection is a regulatory and risk management decision: both deliver atomic DvP, but CeBM carries no issuer credit risk while EMTs carry the issuer's risk — a distinction that affects net capital, FOCUS Report treatment, and examination evidence.
3. Identity Layer — on-chain counterparty verification
Before a settlement transaction executes, the smart contract validates the identity and authorization status of both counterparties. In current implementations, this operates through pre-approved wallet address whitelists: addresses are approved by the DLT MI operator following off-chain KYC/AML verification, and the smart contract checks the whitelist before allowing a transfer to proceed. The ESMA DLT Pilot Regime requires authorized DLT MIs to implement equivalent admission controls to those required of traditional CSDs and trading venues — the technology changes the mechanism, not the substantive standard.
More advanced implementations aligned with the GLEIF vLEI standard enable the smart contract to query a cryptographically verified institutional identity directly, embedding regulatory compliance at the transaction level. This is the architectural direction for dFMI identity infrastructure: on-chain verification that eliminates the whitelist maintenance overhead and supports automated sanctions screening at settlement initiation.
4. Atomic DvP execution — the settlement event
The atomic DvP cycle runs in four steps, all within a single on-chain transaction:
Smart contract condition: The settlement contract is deployed with the trade details encoded — instrument, quantity, price, counterparty wallets. No human instruction is required at settlement time.
Condition validation: The contract checks both wallets simultaneously: does the seller hold the required tokens? Does the buyer hold sufficient programmable cash? If either check fails, the transaction reverts instantly. Nothing partial executes.
Atomic swap: If both conditions are met, the contract executes a simultaneous transfer — securities from seller to buyer and cash from buyer to seller — in a single block. There is no principal risk window: no state exists in which one leg has settled and the other has not.
Finality: The blockchain network's consensus mechanism confirms the transaction — within seconds on permissioned networks with deterministic finality, within 12–15 minutes on Ethereum proof-of-stake. At confirmation, the blockchain transaction hash is recorded as Rule 17a-3 settlement evidence and both parties' ABOR positions update. See delivery versus payment and settlement finality DLT blockchain for finality model mechanics across consensus types.
5. Algorithmic tri-party — automated collateral management
For repo and collateral management use cases, the DLT infrastructure replaces the intermediary tri-party agent with smart contract logic. The collateral smart contract holds the collateral pool tokens, queries price oracle feeds for real-time valuations, monitors the collateral coverage ratio against the repo or margin agreement terms, and executes substitution and margin transfer automatically when thresholds are breached.
The collateral management timeline collapses: a margin call that requires hours of bilateral communication and agent processing in traditional tri-party executes in seconds in algorithmic tri-party, with the smart contract generating an audit trail of each rebalancing event. The institutional governance requirement is unchanged: the smart contract logic must be reviewed and documented under the firm's written supervisory procedures, and oracle data sources must be validated and monitored. Technology automates execution; the judgment embedded in the contractual rules requires human institutional governance. See tokenized collateral repo settlement for operational detail on algorithmic repo settlement.
6. Hybrid rail integration — connecting DLT to traditional infrastructure
In institutional deployment, DLT capital markets infrastructure connects to traditional rails through a translation layer that handles three functions simultaneously. Protocol translation converts traditional instruction formats — FIX messages, SWIFT MT, ISO 20022 — into blockchain instruction formats (JSON-RPC calls, smart contract function parameters), enabling existing OMS and EMS systems to generate on-chain settlement instructions without modification. Finality model reconciliation normalizes the different confirmation timings of traditional and DLT settlement into a single position view, so that a trade settling on-chain at 14:32 appears in ABOR at 14:32 rather than at the next day's reconciliation cycle. Books and records synchronization maps on-chain transaction data to the required fields for Rule 17a-3 trade records — counterparty LEI, instrument identifier, economics, settlement timestamp, and blockchain transaction hash — satisfying the same substantive records standard as traditional settlement evidence.
See hybrid settlement infrastructure and DLT books and records financial institution for the architectural and compliance detail of operating across both rails simultaneously.
Three settlement architecture paths
Devancore Glossary · devancore.com
Three settlement architecture paths
Devancore Glossary · devancore.com
In Devancore™
Devancore — dFMI operating layer
Devancore Glossary · devancore.com
Devancore operates as the dFMI management layer — the institutional operating system above individual DLT market infrastructure operators, traditional CSDs, and CCPs, managing positions, cash, collateral, and compliance across all rails from a single system of record.
Rail-Aware ABOR: unified position accounting across settlement rails
Devancore maintains a single Accounting Book of Record (ABOR) that reflects positions settled across traditional and DLT rails simultaneously. A position settled via DTC book entry and a position settled via smart contract on a permissioned blockchain appear in the same ABOR — under the same instrument master record, with the settlement rail as an attribute rather than a separate ledger. ABOR positions update in real time from on-chain confirmations: when a DLT MI settlement completes, the position change appears immediately, not at end of day. A firm sees AAPL held at DTCC and a tokenized bond held on a DLT-native exchange in a single, unified view. This eliminates the rail reconciliation gap that accumulates when on-chain settlement and traditional accounting run on different update cadences. For positions on ESMA DLT Pilot Regime-authorized infrastructure, the relevant DLT MI's regulatory profile — exemptions, compensatory controls, finality model — is applied to the position record, not treated generically as a "digital asset."
Multi-FMI bridge: cross-network position management
Institutional DLT deployment is not converging on a single network. Canton Network, supported by Goldman Sachs and built on Digital Asset Holdings technology, serves one institutional segment. ESMA DLT Pilot Regime operators — 21X AG and CSD Prague — serve the EU regulatory-compliant segment. Arc Network provides multi-currency programmable cash infrastructure across multiple chains. Devancore connects to each through network-specific adapters, maintaining a single position view across all active DLT infrastructure operators while applying the correct finality model and regulatory profile to each settlement event. Cross-network netting logic allows positions on different networks to offset in the same economic instrument — the institutional requirement that no single DLT MI operator can satisfy alone.
Atomic-to-Net Bridge: liquidity management across atomic and batch rails
The treasury objection to atomic gross settlement — that moving from net to gross dramatically increases intraday liquidity requirements — is real. Devancore's Atomic-to-Net Bridge addresses it through shadow netting analytics that run continuously across all settlement rails. Every atomic DvP settlement event feeds the shadow netting engine, which calculates the firm's net obligation across traditional and DLT rails in real time. Treasury teams see one number — net liquidity required across all rails — not separate intraday pools for each blockchain network and Fedwire. Firms operate with the finality and principal risk elimination of atomic DvP while managing liquidity as a single net position, the same way treasury manages NSCC net obligations today.
Programmable compliance: Rule 17a-3 on DLT rails
Every on-chain settlement confirmed through Devancore generates a Rule 17a-3 trade record at the moment of finality — counterparty LEI, instrument ISIN/CUSIP, economics, settlement timestamp, and blockchain transaction hash. For EMT-settled positions (USDC, EURC), Devancore records the MiCA Article 48 cash leg classification and the issuer's reserve status as of settlement — supporting both the capital treatment decision under Rule 15c3-3 and the audit evidence required for examination. For CeBM-settled positions, the RTGS transaction reference is recorded alongside the on-chain hash.
Cross-rail cash: unified liquidity view
Devancore aggregates intraday cash positions across SWIFT-connected nostro accounts and on-chain stablecoin wallets into a single liquidity view — MT 942 / camt.052 intraday statements feeding the traditional position, blockchain node subscriptions feeding the digital position continuously. Automated on-ramp/off-ramp through regulated EMT issuers handles rail conversion as a treasury operation with a full audit trail. The Arc Network integration provides multi-currency programmable cash — USD, EUR, and additional currencies — enabling cross-border DvP settlement without separate liquidity pools per currency pair. See stablecoin settlement and hybrid settlement infrastructure for the cash layer mechanics in institutional deployment.