Sebastien Rousseau
Get in touch ›

Wholesale Digital Markets in the UK: Tokenised Gilts, Settlement, and the New Champion Role

Tokenised gilts on DLT, atomic against tokenised cash. Intraday repo as the immediate prize. The Champion role exists because polite stand-offs kept the City stuck at PoC.

9 min read

Wholesale Digital Markets in the UK: Tokenised Gilts, Settlement, and the New Champion Role

Tokenised wholesale finance is no longer a thought experiment. In 2026 it is the operating baseline for sterling capital markets. The Bank of England's RTGS renewal, the joint FCA/BoE Digital Securities Sandbox (DSS), and the appointment of a Wholesale Digital Markets Champion now sit on the same chart — and that is the point. The pieces are designed to interlock (Bank of England, GOV.UK).

The Champion is the lever that forces them to.

Executive Summary / Key Takeaways

  • The Champion is the coordination layer the City has been missing. The remit reaches across HM Treasury, the FCA, the Bank of England, and the major sell-side and buy-side desks — built to break the polite stand-off that kept earlier digital-markets initiatives stuck at PoC (Global Government Finance).
  • Gilts go first because they are the hardest asset to get right. HQLA on DLT, settled atomically against tokenised cash, validates the full stack — issuance, trading, repo, collateral, central-bank money — on the deepest sterling pool (Bank of England).
  • Intraday repo is the immediate prize. T+0 atomic repo of tokenised gilts releases capital that today sits idle as same-day liquidity buffer. The savings drop straight through to ROE.
  • Orchestration replaces standalone networks. The Regulated Liability Network, Canton, private bank DLTs, RTGS, and tokenised commercial bank money each carry workflows banks already run. The job is to route across them, not pick one.
  • Policy-as-code is the only compliance model that keeps up. Sanctions, KYC, position limits, jurisdictional gates — encoded in the settlement layer, executed atomically with the trade, producing a cryptographic audit trail rather than a log a regulator has to trust (Association of Corporate Treasurers).
  • Architecture is the moat. The winners weave workflow, data, rail, control, and unit economics into one operating model. The losers run a portfolio of disconnected pilots and call it a strategy.

The Champion Mandate: Coordination, Not Ceremony #

Wholesale market reform in the UK has long failed on the same point — coordination. Treasury sets policy, the Bank runs settlement, the FCA owns conduct, and the City delivers product. Each one is competent. None of them, alone, can force interoperability between a tier-one bank's tokenisation platform and a CSD's settlement engine. That is the gap the Champion is appointed to close.

The role is built around the DSS. The Sandbox is the only place in the UK regulatory perimeter where firms can issue, trade, and settle real digital securities — including tokenised gilts — under tailored waivers to CSDR and existing settlement rules (Bank of England, FCA). It is live, not theoretical. The Champion's job is to make sure the institutions inside it build to the same standards on identity, settlement finality, and message format — so that the platforms that emerge actually talk to each other.

That is the difference between a Sandbox and a sandpit.

Why Tokenise Gilts? #

Gilts are the foundation of the sterling system. They are the collateral the Bank takes in repo, the asset banks hold against LCR requirements, the instrument pension funds use to match liabilities. They are also, today, settled with operational plumbing that hasn't fundamentally changed in twenty years — CREST batches, T+1 conventions, end-of-day liquidity reconciliation. The capital trapped in that workflow is not small.

Putting gilts on DLT changes three things at once.

Intraday repo becomes atomic. A T+0 repo of a tokenised gilt against tokenised cash settles in seconds, not hours. The institutional liquidity buffer that today funds same-day cash needs can be released back into the market. For a tier-one bank running a large repo book, that is basis points of funding cost — and basis points of ROE.

Collateral mobility stops being a phone call. A digital gilt can be pledged or recalled across jurisdictions instantly to meet a margin call. The slow chain of intermediated custody messages — fax, SWIFT MT, end-of-day reconciliation — gives way to a smart-contract movement with cryptographic proof of pledge.

Principal risk in settlement disappears. Atomic delivery-versus-payment means the gilt leg and the cash leg execute as one indivisible operation. Either both settle or neither does. The settlement window that today exposes one counterparty to the other's mid-trade default closes to zero.

These are not future benefits. They are running in the Sandbox now.

The DSS Operating Model #

The DSS is a live regime. To use it as a platform rather than a PoC, banks need an architecture that holds together under regulatory scrutiny and commercial pressure. Five pillars do the load-bearing work.

Workflow Over Technology #

Start with the friction. Trapped liquidity, settlement breaks, reconciliation cost, failed payments — these are the problems clients pay to remove. Technology is justified only where it removes them. Tokenisation is a means, not the product. A platform that ships intraday repo of tokenised gilts has a use case. A platform that ships a tokenisation engine looking for one does not.

Data as the Control Plane #

ISO 20022 payloads bound to on-chain transaction hashes turn settlement data into a single source of truth. Without that binding, smart-contract automation is brittle and reconciliation reverts to spreadsheets. With it, banks get straight-through processing, real-time controls, and analytics clients will actually pay for (Association of Corporate Treasurers).

Orchestration Across Rails #

The Regulated Liability Network, Canton, private bank DLTs, RTGS, tokenised commercial bank money — each one carries workflows banks already run. Forcing every transaction onto one network is the wrong fight. The right architecture routes each workflow to the rail that gives the best combination of cost, speed, settlement finality, jurisdiction, and resilience. That decision is made at runtime, not hard-coded into the platform.

Policy-as-Code Compliance #

Atomic settlement leaves no room for after-the-fact compliance. Sanctions screening, KYC validation, position limits, jurisdictional restrictions — all of it has to execute inside the settlement layer, simultaneously with the trade. The output is a cryptographic audit trail, not a database log. Zero-knowledge identity proofs make this work without leaking client data across counterparties. This is the only compliance model that survives intraday volume.

Unit Economics That Survive a Board Meeting #

Every initiative needs hard numbers. Basis points saved on collateral funding. Intraday liquidity buffer reduction. Settlement-fail rates. Reconciliation FTEs displaced. Cycle time to onboard a counterparty. Anything else — headcount, press coverage, deck slides — is not ROI. Without these metrics, the "innovation" budget becomes a sunk cost the next CFO writes off.

Architecture Matrix #

Layer What the DSS Demands in 2026 The Institutional Prize The Cost of Getting It Wrong
Workflow Client friction dictates product design Clear business case, capital release, immediate adoption Tokenisation platforms with no users — innovation theatre on a board deck
Data ISO 20022 payloads bound to on-chain transaction hashes Straight-through processing, audit-grade evidence, paid analytics Bad data moves faster — more reconciliation breaks, not fewer
Rail Routing across RTGS, RLN, Canton, private DLTs, tokenised cash Capital efficiency, finality on demand, lower funding cost Channel sprawl, fragmented liquidity, controls duplicated five times
Control Policy-as-code, zero-knowledge identity, atomic compliance Risk mitigated at the moment of trade — no T+2 surprise Manual investigations days later — and the fines that follow them
Economics Verifiable unit-cost reductions tied to client outcomes Evidence-led scaling, ROE that survives audit Sunk innovation spend, no durable return, board writes it off

What This Means by Institution Type #

"The decisive question is design discipline: which data, rails, controls, liabilities, and client workflows belong together."

Tier-1 Banks #

Build the orchestration layer. Tier-1s cannot afford for each new tokenised asset or DLT network to spawn a bespoke operating model. The role is to be the regulated bridge between off-chain and on-chain liquidity — providing the legal wrapper, the balance sheet, and the supervisory relationship that makes the Sandbox work for the rest of the market. Stand at the gateway, charge for the access, defend the franchise.

Regional Banks #

Stop building proprietary rails. The advantage is trust and local knowledge. Offer corporate treasurers the visibility, fraud controls, and reliable access to tier-one digital liquidity pools they cannot build themselves. The strategy is integration, not invention.

Fintechs and Market Infrastructure Providers #

The fintechs that win in 2026 will not be the ones running yet another standalone network. They will be the ones providing the integration layer — orchestration engines, oracles, compliance-evidence tooling — that reduces complexity for banks. Add to the bank's stack, do not compete with it. The market has spoken on standalone networks.

Corporate Treasurers #

Stop accepting end-of-day reporting. Demand programmable banking: automated sweeps, real-time liquidity visibility, instant collateral deployment, ISO 20022-grade reconciliation data. The platforms that provide these already exist. The leverage is the threat of moving the workflow.

What Happens Next #

The Champion role is a forcing function. The DSS is a live regime. Tokenised gilts are settling in test, with production on the near horizon. Each piece works alone. The question for 2026 is which institutions assemble them into a single operating model — and which spend another year defending the legacy stack on a quarterly earnings call.

The banks that win will not be the ones with the loudest blockchain marketing. They will be the ones whose architecture is invisible — workflow, data, rail, control, and economics weaving together so cleanly that the client never sees the seams. That is the standard the City is now competing against. Singapore, Switzerland, and Frankfurt are watching. They have noticed.

Questions? Answers.

What is the Digital Securities Sandbox (DSS) and why does it matter?

The DSS is a joint FCA/Bank of England regime that lets firms issue, trade, and settle real digital securities — tokenised gilts included — under tailored waivers to CSDR and existing settlement rules. It matters because UK firms can run live DLT-based wholesale market infrastructure with regulatory air cover, not as throwaway PoCs.

Why tokenised gilts specifically, instead of corporate bonds or equities?

Gilts are the deepest, most regulated asset in the sterling system — the collateral the Bank takes, the LCR backbone, the liability-matching instrument for pensions. Tokenising them tests the full stack on the hardest asset class. Anything else is easier by comparison.

What is the difference between RLN, Canton, and a private bank DLT?

The Regulated Liability Network is a shared-ledger model for tokenised commercial bank money issued by multiple regulated institutions. Canton is a permissioned, privacy-preserving DLT widely used in capital markets. Private bank DLTs are single-institution networks. A 2026 orchestration layer routes across all three depending on the workflow.

How does atomic DvP eliminate principal risk?

A non-DvP settlement window has one leg of a trade settling before the other. Atomic DvP uses a smart contract to make both legs execute as one indivisible operation — either both settle or neither does. A counterparty default mid-window can no longer leave one party exposed because the window does not exist.

What does "policy-as-code" mean in practice?

Compliance rules — sanctions screening, KYC validation, position limits, jurisdictional restrictions — encoded directly in the smart contract or settlement layer and executed at the moment of trade. The output is a cryptographic audit trail, not a database log the regulator has to trust.

How should a bank measure ROI on a DSS pilot?

Basis points saved on collateral funding. Intraday liquidity buffer reduction. Settlement-fail rate. Reconciliation FTEs displaced. Cycle time to onboard a counterparty. That is the list. Headcount, press coverage, board-deck slides are not ROI — never have been.

References #

Last reviewed .