CBDC
A central-bank digital currency is a liability of the central bank. GBTD tokens are liabilities of commercial banks. Mixing the two is the most common error on this map. AI agents, x402, Hyperledger, Oracle and Linux Foundation software change the rails — not that test.
Official Bank of England Britannia seal. On this map it flags research adjacency in London — the Synchronisation Lab, not a Quant mandate, and not GBTD.
| Kind | Who owes it | Example | On this map |
|---|---|---|---|
| CBDC | Liability of a central bank | A digital pound, if issued, would sit here. | BoE Synchronisation Lab is adjacent experimentation — not a live CBDC. |
| Tokenised deposit | Liability of a commercial bank | GBTD tokens between Barclays, HSBC, Lloyds, NatWest, Nationwide, Santander. | The live UK Finance pilot. Quant is the named technology partner (Overledger + PayScript), not the issuer. |
| Stablecoin / crypto | Usually a private issuer or protocol | x402 agent payments can use tokens; Quant’s thesis is to settle them in bank money. | Layer 3 in Verdian’s architecture. Do not read a city pin as a coin listing. |
Test
A CBDC is a liability of a central bank. A tokenised deposit is a liability of a commercial bank. A stablecoin is usually a liability of a private issuer. Overledger can sit in front of any of them. That does not make every Overledger deployment a CBDC stack. GBTD, UK Finance, six banks, Quant as technology partner: commercial-bank money.
Sources & further research
Layer 2
Selected 26 September 2025. Live transactions of tokenised sterling deposits into mid-2026. Overledger and PayScript named as the foundation. Builds on Quant’s 2024 RLN phase. Use cases published by Quant in October 2025 include retail and wholesale movement of real money. Not Synthorus, not a digital pound.
How to use it · Use GBTD as the UK specimen of layer-2 tokenised deposits in Verdian’s architecture.
Sources & further research
Concluded lab
June 2023. BIS Innovation Hub London Centre and the Bank of England tested APIs for a retail-CBDC ecosystem. Quant’s newsroom says the company was on the vendor team with UST: Overledger for infrastructure, smart contracts and ledger interoperability; UST for the frontend API layer. The BIS page is explicit: purely experimental, not BoE policy, design or launch. Cite both URLs. Do not promote Rosalind into a standing Quant–BIS office in Basel.
How to use it · Use Rosalind as evidence that Quant has been in a CBDC-API room — as a concluded vendor credit, graded separately from GBTD.
Sources & further research
Layer 1 adjacency
February 2026: Quant selected for the Bank of England’s Synchronisation Lab, a simulated RT2 environment exploring atomic multi-bank treasury rebalancing. Quant’s press note is explicit: not endorsement, not policy, not live RTGS. Layer-1 thinking (finality, synchronisation) sitting beside commercial-bank programmable money — which is the three-layer diagram, not a digital-pound launch.
Sources & further research
Enterprise DLT
Oracle Blockchain Platform Digital Assets Edition (12–14 February 2025) is built on Hyperledger Fabric, with Besu/Enterprise Ethereum also in Oracle’s blockchain family — Linux Foundation Decentralized Trust software. Oracle’s blog names Overledger as the orchestration layer for XA/2PC cross-ledger workflows, quoting the BIS ‘singleness of money’ problem.
How to use it · Fabric (or Besu) as the permissioned ledger of record inside the bank; Overledger when that ledger must settle with another domain; Oracle as the operations plane.
Sources & further research
Agents
Three pieces have to click or agentic payments stay in the sandbox. MCP (Flow Applications) is how an agent calls a bank-grade workflow. x402 (Linux Foundation) is how an agent pays an HTTP resource. Tokenised deposits (GBTD) are how that payment can be regulated commercial-bank money. MIT’s Hardjono/South paper (2025) adds the ethics constraint: the agent must carry authenticated, authorised, auditable delegation — a person granted a scope, not a key left in a prompt. Quant’s July 2026 note is the join: Fusion x402-ready, x402 Foundation membership, settlement ambition in tokenised bank money. Architecture, not a claim that agents already clear sterling at Barclays.
How to use it · Prototype on x402; shape through Flow; settle in tokenised deposits; require delegated authority as in the MIT paper — not a Quant ethics SKU.
Did you know
CBDC
Did you know tokenised sterling deposits are not a digital pound?
A CBDC is a liability of the central bank. GBTD tokens are liabilities of Barclays, HSBC, Lloyds, NatWest, Nationwide and Santander. Quant was selected to provide the programmable-money infrastructure — Overledger and PayScript — not to issue the money. The future-of-money move is making commercial-bank money programmable without pretending it is central-bank money.
Open the distinction →CBDC
Did you know Project Rosalind was never a digital-pound launch?
The BIS Innovation Hub London Centre and the Bank of England tested APIs for a retail CBDC in 2023. Quant was on the vendor team with UST. The BIS page is explicit: experiment, not policy, not a design, not a launch. A concluded lab — not a standing Quant office in Basel, and not GBTD.
Open the BIS page note →CBDC
Did you know the Synchronisation Lab is not the digital pound either?
February 2026: Quant in a simulated RT2 environment for atomic multi-bank treasury bundles. Quant’s own press note says this is not endorsement, not policy, not a live RTGS connection. Synchronisation sitting beside RTGS is gateway thinking. It is still not a CBDC.
Open the lab note →