Hybrid Market Infrastructure

Why markets operate across several rails

A financial asset is not the same thing as the rail used to trade, settle, hold, or service it. An equity security can be represented through issuer records, a depository position, an intermediary account, and a tokenized entitlement. Each record can support a distinct function. An operating rail can include a conventional securities system, a custody platform, a payment rail, a private ledger, or a public blockchain. Hybrid infrastructure coordinates their relationship to the same lifecycle.

This is an intentional architecture, not a temporary failure to modernize. Different assets have different liquidity, custody, servicing, privacy, settlement, and regulatory characteristics. Large existing portfolios cannot be migrated in a single technical event, and counterparties will adopt new operating models at different times. A durable design must support conventional and digital forms together, along with controlled conversion and reconciliation between them.

Tokenization also does not create liquidity by itself. Liquidity depends on participant access, venues, market makers, financing, collateral treatment, conversion routes, reliable settlement, and post-trade operations. A tokenized position that cannot move between approved holders, be converted under defined conditions, or connect to the required cash and custody processes can create a new isolated pool rather than a deeper market.

The hybrid infrastructure stack

The instrument and rights layer establishes the financial object: issuer, class, terms, entitlement model, economic rights, and applicable restrictions. This layer answers what is being issued, held, transferred, or serviced. It is the reference point for every later mapping; a token contract cannot independently answer it.

The identity and data layer connects the instrument to its market representations. It can include FIGI hierarchy, CUSIP, ISIN, internal identifiers, legal-entity and account information, token contract, network, wallet, source lineage, and effective dates. These mappings are governed relationships, not a list of equivalent codes. Data Interoperability in Capital Markets explains the required data discipline.

The execution and instruction layer carries the actions that start a lifecycle: investment decision, order, allocation, transfer request, Tokenization Instruction, settlement instruction, corporate-action election, or de-tokenization request. The relevant workflow identifies the initiating party, authority, input data, controls, and expected result. It retains the instruction through subsequent handoffs rather than allowing it to become a disconnected technical event.

The record and custody layer maintains the holding relationship. It can include an issuer or transfer-agent record, depository account, intermediary or custodial sub-ledger, wallet mapping, and token contract state. The programme should state which record is authoritative for each defined fact. A record of token movement can be authoritative for a technical event while a different account or register governs an entitlement, registered-holder status, or customer relationship.

The settlement and servicing layer covers delivery, payment, conversion, income, corporate actions, tax, reporting, and closure. It links the position to operational work that must continue after trading activity. A token balance does not by itself determine a record-date entitlement, a tax treatment, an election, or an account allocation. Corporate Actions for Tokenized Securities addresses this connection.

The control and resilience layer monitors restrictions, configuration, network health, authority, reconciliation, exceptions, remediation, and retained evidence. It makes a hybrid operation operable during a disruption, mismatch, outage, or disputed event. The appropriate controls depend on the responsible programme, but they need defined owners, evidence, and a documented route from detection to resolution.

One economic right, several operating records

A hybrid model can maintain several records of related facts without creating several economic claims. The design needs a controlled relationship between the security or entitlement, source quantity, active representation, approved account or wallet, contract and network, event record, and reconciliation result. The relationships should show whether a conventional quantity is available, reserved, immobilised, converted, or returned.

For a tokenized entitlement, the relevant programme might control a conventional source position while a tokenized representation is active in an approved wallet. The active token supply should be reconciled to the designated control quantity. The underlying record hierarchy should specify how the provider handles a timing difference, erroneous entry, lost credential, or conversion request. One Economic Right, Multiple Records and Authoritative Record for Tokenized Securities explore this structure.

This fact-specific approach is more useful than declaring one universal system of record. Registered ownership, customer entitlement, participant account quantity, token balance, wallet eligibility, and exception state can be separate facts held by different systems. Interoperability requires these facts to be mapped, compared, and governed rather than casually collapsed into one ledger status.

Liquidity and settlement across rails

Cross-rail conversion is a lifecycle process. The programme validates the source instrument, account, authority, restriction state, and available quantity. It then reserves, immobilises, or otherwise controls the source position before creating the approved representation. The destination contract, network, and wallet receive the relevant event. Account and token records are compared, and a return path exists for de-tokenization or another authorised conversion.

Settlement requires similar sequencing. Delivery-versus-payment can involve cash and asset components processed by different systems. A token-network event may achieve technical finality before cash settlement, custody booking, or other account-side processes have completed. The operating model needs in-flight states, confirmations, deadlines, and reconciliation before it reports a fully completed lifecycle. Process Interoperability in Capital Markets will examine those controls in detail.

Networks as configuration choices

A blockchain network is one operating component of hybrid infrastructure. It can provide a consensus mechanism, a token environment, event visibility, and protocol execution. It does not determine the instrument's legal character, replace every account record, or resolve every post-trade control. A responsible programme assesses a network's reliability, security, observability, governance, transfer controls, capacity, cost, integration, and lifecycle support.

A multi-network design requires additional discipline. Every approved network, contract, wallet, token representation, source quantity, and conversion route must be mapped and monitored. Without that configuration, a programme can create unsynchronised representations of a related economic interest. Blockchain Eligibility for Financial Markets and Multi-Network Tokenized Securities cover these design choices.

DTC as a current hybrid reference

DTC's published tokenization-service design provides a practical example. In the December 2025 staff no-action letter, DTC described a Tokenization Instruction that debits eligible securities from a DTC Participant's conventional account and credits the Digital Omnibus Account. DTC stated that its Factory system would mint and deliver a tokenized entitlement to the participant's Registered Wallet, while LedgerScan would track relevant token movements and holdings. The stated de-tokenization process burns the token, debits the Digital Omnibus Account, and credits the participant's conventional account.

DTC announced the service launch on October 28, 2026 and described a multi-network model connecting traditional and digital environments. This is DTC's service implementation, with features and network support that can change over time. It is useful because it makes the hybrid principle visible: established account, governance, recordkeeping, and conversion controls remain linked to digital representation and movement. It is not the only possible market design or a general regulatory template.

The SEC's September 2026 Innovation Exemption also illustrates controlled market evolution. The exemption is temporary and conditional, covering limited trading of tokenized NMS stocks on specified Tokenized Securities Venues. It should be read as a targeted framework for specified activity rather than a blanket permission for tokenized securities or onchain secondary trading.

Hybrid market infrastructure in Devancore

Devancore can operate as a cross-rail coordination layer. It can connect instrument master data, provider records, accounts, wallets, contracts, networks, instructions, lifecycle events, reconciliation evidence, and exceptions across traditional, tokenized, and onchain environments. The aim is to give an institution one governed operating view while preserving the records and controls held by responsible providers.

Devancore can support research, execution orchestration, post-trade controls, servicing workflows, and reconciliation across hybrid rails. It does not act as an issuer, transfer agent, broker-dealer, clearing agency, depository, exchange, alternative trading system, custodian, or legal-title arbiter. It does not decide regulatory eligibility or replace a responsible provider's authoritative records and controls.