Collateral in Motion: Tokenized Collateral Mobility and the Post-Quantum Coordination Challenge
How Tokenization Turns Trapped Collateral Into Programmable Liquidity, and Why Interoperability Multiplies Cryptographic Risk
Key findings
As of
- Tokenized collateral is production infrastructure. Broadridge's Distributed Ledger Repo processed $7.6 trillion of tokenized repo in October 2026, BNY financed a tokenized U.S. Treasury in triparty repo, and CFTC staff confirmed tokenized money-market fund shares as uncleared-swap margin on 24 September 2026.
- Every layer still signs with classical keys. Ethereum, Base and Besu-based ledgers default to ECDSA over secp256k1, Solana uses Ed25519, bridge quorums sign with ECDSA, and MPC or HSM custody produces threshold ECDSA or EdDSA signatures.
- Interoperability multiplies the problem. One cross-chain pledge of a tokenized fund share depends on six independently governed trust domains. If each has a 90% chance of migrating by 2032, the whole workflow has a 53% chance of being post-quantum safe.
- The cost of breaking the keys fell. 2026 estimates for breaking 256-bit elliptic-curve keys such as secp256k1 dropped to 19,397 trapped-ion qubits (IonQ) and 29,588 cat qubits (Alice & Bob).
- Rulebooks and quantum roadmaps run on separate clocks. The Bank of England (October 2026) and MAS (November 2026) address key loss and compromise but not quantum; Executive Order 14412 and the U.S. Treasury Quantum-Readiness Task Force set the post-quantum timeline.
- The fix is standardized. NIST FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) are final, and institutions can add post-quantum authorization at the layers they control without changing the chain.
How to read this report. Sections 01 to 06 explain why tokenized collateral is becoming core market infrastructure and who is building it. Sections 07 to 09 show why every interoperable layer adds keys that must move to post-quantum signatures together. Sections 10 and 11 let you find your own segment and stack. Sections 12 to 14 cover the regulatory clocks and what to do this quarter.
Tokenized collateral reached production scale. Post-quantum authorization is the next layer.
- 21 SepThe Eurosystem launches Pontes, which lets wholesale tokenized-asset transactions settle in central bank money, with further services to be added step by step.
- 24 SepCFTC staff update their crypto-asset FAQs: swap dealers may accept tokenized money-market fund shares as initial or variation margin for uncleared swaps, subject to conditions.
- 13 OctBNY and Citadel Securities use a tokenized 2-year U.S. Treasury as collateral in an overnight triparty repo. BNY calls it a first for a major triparty platform.
- 15 OctGoogle Quantum AI demonstrates magic state cultivation on Willow (published in Science): about 40× fewer errors and T-states at 99.99% logical fidelity, on one of fault-tolerant quantum computing's costliest steps.
- 19 OctJPM Coin (JPMD) goes live on Ethereum, its second public chain after Base in November 2025.
- 22 OctJ.P. Morgan Asset Management makes its MONY and JLTXX tokenized money-market funds available on Solana.
- 29 OctThe Bank of England consults on tokenized collateral at CCPs. The draft asks CCPs to consider the loss, compromise or unavailability of cryptographic keys and the failure of third-party bridges. It does not mention quantum computing. Responses are due 12 February 2027.
- 2 NovEurex Clearing becomes a “hybrid CCP”: the ESM's €1B digital bond is eligible in the GC Pooling ECB basket and as margin collateral.
- 17 NovFed Governor Waller says central bank money need not be in every transaction but must sit at the foundation of tokenized markets, and asks how operators of new systems will take responsibility for compromised or lost keys.
- 19 NovMAS publishes the Guardian Tokenised Collateral Framework, built with an industry workgroup: eight lifecycle steps from eligibility to default, enforcement and cross-border use.
The read-across: every item above makes collateral faster, more continuous or more connected, which is what the market has asked for. None of these milestones is about post-quantum migration, and none needed to be. That is the shared next step this report maps: over the same months, published estimates for breaking the elliptic curve behind most collateral keys fell to roughly 20,000 to 30,000 physical qubits (Section 08).
What is collateral mobility?
Collateral is the asset a market participant puts behind an obligation. In a repo, a cash borrower provides securities (usually high-quality assets such as government bonds) to secure short-term funding. In derivatives and clearing, firms post margin so that a counterparty or central counterparty has protection if exposures move or a participant defaults.
Collateral mobility is the ability to identify, move, pledge, substitute, release and reuse eligible collateral across counterparties, markets, jurisdictions and systems in time to meet funding and margin obligations.
The simplest way to understand the problem is this: owning collateral is not the same as being able to use collateral. A bank may own billions of dollars of Treasuries, but those securities can still be operationally stranded in the wrong account, legal entity, custodian, market, time zone or settlement window when a margin call or financing need arrives.
Supervisors frame the same test. The Bank of England's October 2026 consultation says a CCP must be able to access, transfer and realize collateral reliably when required, including after a clearing-member default. That distinction matters because the economic value comes from usable collateral, not merely from the nominal value of assets on a balance sheet.
Why does collateral get trapped?
Traditional markets already have enormous pools of high-quality collateral. The inefficiency comes from fragmentation. A single global institution can manage collateral across hundreds of accounts, multiple custodians, clearing houses, currencies, legal entities and time zones. Each location has its own eligibility rules, cut-offs, reconciliation processes and settlement dependencies.
These frictions create defensive behavior. Firms pre-fund. They over-post. They leave assets in multiple places “just in case.” They hold cash overnight because the security that would otherwise satisfy the obligation may not arrive in time. The result is an operational tax on the balance sheet: more inventory, liquidity and capital are tied up than the economic exposure alone would require.
The prize is therefore not simply faster settlement. It is the ability to make the same stock of high-quality assets do more useful economic work over time.
How does tokenization improve collateral mobility?
Tokenization is not the same thing as collateral mobility. Tokenization creates a programmable digital representation or record of an asset or entitlement. Mobility is the ability to use that representation across real financing, margin and settlement workflows. A token that can only sit inside one closed system may be tokenized but still economically immobile.
Operationally, tokenization makes availability machine-readable, turns eligibility and haircut rules into code, compresses transfer and pledge into near real time, synchronizes cash and collateral legs through delivery-versus-payment, and lets released collateral be reused sooner, including outside local settlement windows.
Tokenization does not require every asset to leave traditional custody. The MAS Guardian Tokenised Collateral Framework distinguishes three common models: digital twins linked to an existing depository, custodian or register record; custodian-sponsored tokens; and digitally native instruments whose ledger forms part of the official record. The legal and custody model matters as much as the token format.
Tokenization does not automatically create market liquidity. It can improve operational mobility, settlement, programmability and availability. It does not manufacture buyers, sellers or market depth. An economically illiquid asset can remain illiquid even if it becomes easier to transfer.
That is why the market now judges tokenization by what the token can do: a tokenized Treasury financed in triparty repo within minutes, a digital bond accepted as CCP margin, and trillions of dollars of tokenized repo a month. The focus has moved from the token to the financing and margin work it performs.
Who makes collateral move, and who captures the value?
Collateral mobility is not a single-chain feature. It is a market-wide workflow involving the asset owner, the collateral receiver, custodians, market infrastructures, financing venues, cash systems, data providers and interoperability layers. Each participant captures a different part of the economic benefit.
Deploy collateral where exposures arise
Hold, validate, allocate and optimize collateral
Turn collateral into funding and margin
Synchronize cash with collateral movement
Coordinate workflow across separate domains
For banks the prize is balance-sheet efficiency; for asset managers, staying invested while meeting margin; for CCPs, faster access to protection; for custodians and CSDs, a new digital servicing layer. Every one of those layers moves collateral with its own signing keys.
What market is tokenized collateral mobility opening?
The opportunity is not a few-billion-dollar product. It is the secured-financing and collateral layer underneath global finance: repo, securities lending, derivatives margin, CCP collateral and tokenized funds. Read the numbers below in layers: flow, exposure, balances, margin, asset base and buyer economics are different quantities and are not additive.
Infrastructure revenue interpretation: providers do not capture the full collateral base. They monetize sub-basis-point economics across custody, settlement, orchestration, data, optimization and security. For example, 0.1bp on $100T of annualized flow equals $1B of revenue; 1bp equals $10B. Those are illustrative fee scenarios, not observed revenues.
The category in practice: how JPMorgan built tokenized collateral
No single institution owns tokenized collateral, but one public example spans more of its layers than any other. JPMorgan's Kinexys unit runs collateral, repo, cash and fund products on a permissioned platform and, increasingly, on public blockchains. Its path is the clearest available map of where the market is heading, and of where the cryptographic dependencies follow.
From one collateral trade to a multi-chain collateral, cash and fund stack
- Oct 2023Tokenized Collateral Network goes live. BlackRock tokenizes shares in one of its money-market funds and transfers them to Barclays as collateral for an OTC derivatives trade.
- May 2025First cross-chain DvP touching a public chain. Ondo's tokenized Treasury fund settles on Ondo Chain's testnet against payment on Kinexys, coordinated by Chainlink's runtime environment.
- Aug 2025Cross-ledger intraday repo with HQLAX and Ownera. Collateral moves on HQLAX, cash settles on Kinexys, with settlement and maturity times set to the minute and up to $1B traded in a day.
- Nov 2025JPM Coin (JPMD), a USD deposit token, goes live for institutional clients on Base.
- Dec 2025MONY, J.P. Morgan Asset Management's first tokenized money-market fund, launches on public Ethereum.
- May 2026JLTXX, a U.S. registered government money-market fund designed to support stablecoin issuers under the GENIUS Act, launches on Ethereum.
- Oct 2026JPMD goes live on Ethereum; MONY and JLTXX become available on Solana. Kinexys reports $7B in average daily transaction volume and more than $4T processed since inception.
Collateral without liquidation
The Tokenized Collateral Network lets clients transfer collateral ownership while remaining invested. In 2026 it won Best Live Collateral Management Solution at the Future of Finance Awards, alongside Best Traditional Bank.
Precision timing
Intraday repo with settlement and maturity specified to the minute turns idle intraday liquidity into a priced, usable resource.
Multi-chain reach
Deposit tokens and funds now run on Base, Ethereum and Solana, alongside the permissioned Kinexys platform, so clients can choose where collateral and cash live.
Quantum preparation
In May 2024 JPMorgan connected two data centers with a quantum-secured crypto-agile network (Q-CAN). Its CIO described a dual remediation strategy combining post-quantum cryptography and quantum key distribution.
The structural point. Even a bank that has invested visibly in quantum security inherits the signature scheme of every public chain its tokens touch. On Ethereum and Base, accounts authorize transactions with ECDSA over secp256k1; on Solana, with Ed25519. That is a property of the chain, not a choice any issuer makes, and it applies equally to every issuer, custodian and collateral taker on the same rails. No institution, however well prepared, can migrate a shared rail on its own. This report does not assess Kinexys's private infrastructure, whose cryptography is not publicly documented.
When mobility goes multi-chain: the tokenized fund as collateral
The fastest-moving collateral use case on public chains is the tokenized money-market fund. A fund share that keeps earning yield while it secures a trade is exactly the collateral the market has wanted, and venues, regulators and standard-setters moved together in 2026 to make it usable.
Accepted at trading venues
BlackRock's BUIDL, tokenized by Securitize, is accepted as collateral on Crypto.com and Deribit (June 2025), as off-exchange collateral on Binance (November 2025) and on OKX with a regulated bank custodian (April 2026). Franklin Templeton's Benji-issued fund shares back an off-exchange collateral program on Binance (February 2026).
Accepted as derivatives margin
CFTC staff confirmed on 24 September 2026 that swap dealers may accept tokenized money-market fund shares as initial or variation margin for uncleared swaps, subject to conditions. The Bank of England and MAS both examine tokenized money-market funds as collateral in their 2026 papers.
Real scale
Tokenized U.S. Treasuries passed $10B in market capitalization on 11 February 2026 and reached about $13B by 31 March, roughly tripling in fifteen months (CoinGecko 2026 RWA Report).
Multi-chain by design
Securitize uses Wormhole as its official interoperability provider for tokenized funds from BlackRock, Apollo, Hamilton Lane and VanEck, so a fund share can move between chains as its holder needs.
Follow one pledge of a tokenized fund share from holder to collateral taker and count who holds signing keys along the way. Six independently governed cryptographic domains appear, each with its own migration owner. None of them is the fund manager's private infrastructure: they are shared custody, contract, chain, bridge and venue layers.
The same pattern holds in permissioned wholesale markets. A cross-ledger intraday repo links a collateral ledger, a cash ledger and an orchestration layer. Pontes links market DLT platforms to TARGET services. A single-venue workflow operates inside one cryptographic perimeter under one migration authority; a cross-domain workflow distributes its dependencies across several perimeters, each governed separately.
Interoperability as a cryptographic dependency multiplier
Interoperability converts post-quantum migration from a system problem into a coordination problem across independently governed trust domains.
The security of any cross-chain transaction approaches the security of its weakest cryptographic dependency:
where each Si represents the cryptographic security posture of an independently governed trust domain. This property has four consequences.
Weakest-link collapse
If the collateral chain is PQ-safe but a quorum of cross-chain verifier keys remains vulnerable, a future quantum compromise of that quorum could enable forged cross-chain attestations. If the messaging layer migrates but a valuation network remains classical, forged valuation attestations remain a separate route into the workflow. End-to-end assurance therefore depends on every security-critical domain, not only the settlement chain.
Illustrative scenario: if each of 6 participating domains independently achieves 90% probability of completing PQ migration by 2032, the probability that the entire workflow is quantum-safe is 0.96 = 53%. The system retains a 47% probability of having at least one classical dependency. This is a property of the architecture, not of any individual domain's migration effort.
Encrypted data exposure
Cross-chain collateral workflows transmit sensitive encrypted data across domains: counterparty positions, collateral valuations, margin calculations, and settlement instructions flow through privacy layers and orchestration services. This encrypted data is subject to harvest-now-decrypt-later risk. An adversary captures ciphertext today and decrypts it when quantum capability arrives, exposing institutional position data and collateral relationships.
Bridge and verifier quorums as systemic dependencies
Cross-chain transfers are authorized by signer quorums that sit outside both the issuer and the collateral taker. Wormhole, for example, documents a canonical set of 19 Guardians and requires 13 of their signatures to produce a valid cross-chain message; those signatures are ECDSA. Its documentation describes future threshold signatures and zero-knowledge proofs, but we found no published post-quantum signature migration. A quantum attacker would need to forge a quorum, not a single node, yet the dependency still sits outside the institution's direct control. The Bank of England's consultation makes the same point in operational terms, asking CCPs whether the failure of a third-party bridge could affect access to collateral.
Migration coordination cost
Cross-domain PQ migration adds a coordination dimension that single-domain migration does not have. Every participating chain, every bridge signer set, every orchestration node, every data feed, and every verifier contract on every destination chain must upgrade. If destination-chain verifier contracts are immutable or upgradeable only through ECDSA-governed multisigs, PQ signatures cannot be verified even if operators produce them. Partial migration provides limited improvement due to weakest-link dynamics.
The threat clock moved in Q4 too
The curves under most of the collateral stack are secp256k1 and other 256-bit elliptic curves: secp256k1 is the default transaction-signing curve of Ethereum and of Besu-based permissioned networks, and ECDSA also signs the bridge guardian and verifier quorums that move tokenized assets between chains. Three new resource estimates this year target that curve directly.
| Estimate | Hardware model | Physical qubits | Relative hardware (linear) | Time per key |
|---|---|---|---|---|
| Google Quantum AI · Mar 2026 | Superconducting | <500,000 | Minutes | |
| IonQ · Sep 2026 | Trapped ion, qLDPC codes | 19,397 | ~25.7 days per attempt | |
| Alice & Bob · Oct 2026 | Cat qubits, LDPC codes | 29,588 | ~62 minutes |
Why a slow machine still matters for collateral. A 26-day attack is far too slow to race a transaction. It is fast enough for a validator, committee, oracle or admin key whose public key has been on record for a year. Those long-lived control-plane keys are exactly the ones a cross-domain collateral workflow depends on. Hardware is moving in the same direction: Google showed magic state cultivation on Willow in October, and IonQ says it is on track for a fault-tolerant 10,000-physical-qubit system in 2027 (a company target, not a demonstrated result).
These are resource estimates under stated hardware assumptions, not machines: no such computer exists today. The Global Risk Institute's Quantum Threat Timeline Report (2025 edition, published March 2026, 26 experts) puts the chance of a cryptographically relevant quantum computer within ten years at 28% to 49%, the highest in the series. IonQ's paper also notes that ML-DSA and SLH-DSA are not affected by this class of attack: the fix is standardized and available now.
Counterargument: “the infrastructure is already becoming quantum-ready”
Bridges and messaging: Wormhole's documentation describes future threshold signatures and zero-knowledge proofs. LayerZero has released Akita, a lattice-based post-quantum polynomial commitment scheme for zero-knowledge proving, which is separate from the ECDSA signatures its verifier networks use today. Conclusion: the research is real, but the signatures that authorize cross-chain messages remain classical.
Besu: stock Besu remains Ethereum-compatible and classical at the transaction and consensus layers. Research and application-layer approaches can add PQ authorization without waiting for a full client rewrite, but those are deployments layered on top of Besu rather than native, default PQ protection.
The institutional point is therefore not that nobody is working on PQ. It is that migration maturity differs by domain. Interoperability forces the end-to-end workflow to inherit those different timelines.
Map your cryptographic dependencies
Identify which cryptographic dependencies you control, which are inherited from third parties, and where retrofit protection versus a PQ-native perimeter is required before tokenized collateral workflows become harder to unwind.
Quantifying the dependency graph
The quantitative exposure is best expressed as a dependency graph, not a signature count. Consensus signatures are block-level, oracle reports serve multiple consumers, and bridge attestations may be batched. What does not reduce through batching or amortization is the number of independently governed cryptographic systems that must migrate.
- Transaction signing
- Consensus / validator
- Admin / governance
- Custody / HSM
- Oracle attestation
- API / machine identity
- Privacy / encryption
1 migration authority · 1 timeline
6 migration authorities · independent timelines
Trust domains. Approximately 80 live institutional DLT trust domains exist today. EternaX projects approximately 375 by 2035, modeled from FSB G-SIB data (29 G-SIBs), WFE exchange counts, and observed deployment patterns. This is an EternaX estimate, not an industry-reported figure.
External dependencies. A Tier 1 bank may simultaneously participate in proprietary ledgers, payment networks, privacy ledgers, public chains, market-infrastructure tokenization services and multiple custody or bridge systems. PQ migration must therefore be mapped at every trust boundary. Broadridge DLR alone has sustained $7.4 to $8.0 trillion of monthly tokenized repo flow since July 2026. The direction is clear: as collateral becomes more mobile and economically productive, the dependency graph grows unless cryptographic migration is designed across the full workflow.
Find your segment: who is building tokenized collateral
This map lists institutions that have publicly announced tokenized collateral, deposit or fund activity. Being named here means you are building this market. Every entry comes from the institution's own public announcement; no private system is assessed, and the order within each segment is alphabetical.
The exposure does not belong to any one name. It belongs to the shared technology every institution in a segment depends on, which the readiness map in the next section grades layer by layer. The bigger the builder, the bigger the dependency graph.
CSDs, CCPs and market infrastructures
- Clearstream connected to the Eurosystem's Pontes as a market DLT operator at launch (Sep 2026).
- DTCC launched the DTCC Tokenization Service for DTC-custodied securities (Oct 2026).
- Eurex Clearing made the ESM's €1B digital bond eligible for GC Pooling repo and as margin (Nov 2026).
- Euroclear launched a tokenised collateral mobility initiative (Feb 2025).
- SGX Group contributed to the MAS Guardian Tokenised Collateral Framework (Nov 2026).
Banks: deposit tokens and tokenized assets
- Citi runs Citi Token Services, tokenized deposits live in seven markets (Sep 2026).
- DBS contributed to the MAS Guardian Tokenised Collateral Framework (Nov 2026).
- Deutsche Bank onboarded to the Eurosystem's Pontes at launch (Sep 2026).
- HSBC runs its Tokenised Deposit Service in six markets and completed the first live interbank tokenised deposit transaction on Swift's ledger (Aug 2026).
- JPMorgan brought JPM Coin to Ethereum after Base; Kinexys averages $7B a day (Oct 2026).
- Santander onboarded to the Eurosystem's Pontes at launch (Sep 2026).
- Société Générale onboarded to the Eurosystem's Pontes at launch (Sep 2026).
- Standard Chartered completed the first live interbank tokenised deposit transaction on Swift's ledger with HSBC (Aug 2026).
- UBS contributed to the MAS Guardian Tokenised Collateral Framework (Nov 2026).
- UOB completed live tokenised deposit transactions on Swift's ledger (Aug 2026).
Custodians and triparty agents
- BNY used a tokenized U.S. Treasury in an overnight triparty repo with Citadel Securities (Oct 2026).
- Ceffu is the off-exchange custodian for Franklin Templeton's collateral program on Binance (Feb 2026).
- Standard Chartered is the regulated off-exchange custodian for BUIDL collateral on OKX (Apr 2026).
Repo and financing platforms
- Broadridge processed $7.6T of tokenized repo on DLR in October 2026.
- HQLAX runs a cross-ledger intraday repo with J.P. Morgan and Ownera (Aug 2025).
- Ownera orchestrates that cross-ledger repo over the FinP2P protocol (Aug 2025).
Fund issuers and tokenization platforms
- BlackRock BUIDL is accepted as collateral on Crypto.com and Deribit (Jun 2025), Binance (Nov 2025) and OKX (Apr 2026).
- Franklin Templeton Benji-issued fund shares back an off-exchange collateral program on Binance (Feb 2026).
- J.P. Morgan Asset Management offers MONY and JLTXX on Ethereum and Solana (Oct 2026).
- Ondo Finance settled OUSG in a cross-chain DvP against bank payment (May 2025).
- Securitize tokenizes BUIDL and brought it to BNB Chain and Binance collateral (Nov 2025).
Trading venues
- Binance accepts BUIDL (Nov 2025) and Benji fund shares (Feb 2026) as off-exchange collateral.
- Crypto.com accepts BUIDL as collateral (Jun 2025).
- Deribit accepts BUIDL as collateral (Jun 2025).
- OKX accepts BUIDL as collateral with off-exchange custody (Apr 2026).
Not named? Find your segment by what you run, not by who you are. If your collateral, deposits or fund shares touch any of these layers, the same rows of the readiness map apply to you, and so does the same fix.
Find your stack: a readiness map by infrastructure type
The segment map names who is building; this map names the technology they share. Every bank, market infrastructure, custodian and venue running tokenized collateral uses at least one of these patterns. If your stack appears in a row, the exposure in that row is yours too, however well your own systems are run, because it is a property of the shared technology rather than of any operator.
| Infrastructure pattern | Where you will find it | Default signing today | Public post-quantum status | Status |
|---|---|---|---|---|
| Permissioned EVM ledgers (Hyperledger Besu, GoQuorum lineage) | Bank and market-infrastructure private chains, tokenization services, deposit-token and repo ledgers | ECDSA secp256k1 by default; secp256r1 configurable; QBFT validator signatures on blocks | No post-quantum roadmap in client documentation; PQ authorization can be added at the application layer | Classical |
| Daml / Canton-type privacy ledgers | Interoperable institutional networks for repo, tokenized Treasuries, funds and cash tokens | Classical elliptic-curve signing in production | Post-quantum signing experimental only, not in production; wallet, MPC, exchange and SDK support still to come | Classical |
| Corda-type DLT | Collateral registries and securities-financing platforms | EdDSA Ed25519 node identity; ECDSA secp256r1 for CA and TLS | SPHINCS-256 offered experimentally; new algorithms need a network-wide upgrade | Experimental |
| Fabric-type DLT | Consortium, trade and supply-chain finance ledgers | ECDSA P-256 | No published roadmap | Classical |
| Public Ethereum and L2s (e.g. Base) | Tokenized funds, deposit tokens, stablecoins | ECDSA secp256k1 accounts; public keys visible once an account has signed | No scheduled signature migration | Classical |
| Ed25519 public chains (e.g. Solana, Aptos) | Tokenized funds and multi-chain share classes | Ed25519 | No scheduled signature migration | Classical |
| Bridges and messaging layers | Moving tokenized funds and cash between chains | Signer quorums, e.g. 13-of-19 ECDSA guardians; ECDSA verifier networks; secp256k1 and Ed25519 validator keys | Research on zero-knowledge and threshold signatures; no published PQ signature migration | Classical |
| MPC and HSM custody | Every institution's wallet and signing layer | Threshold ECDSA or EdDSA matching the chain's curve | Threshold ML-DSA remains research-stage | Classical |
| The fix | Any authorization path an institution controls | NIST FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) | Final standards, available now | Ready |
Regulatory convergence
U.S. federal milestones are a policy baseline, not a blanket mandate on private market infrastructure. Executive Order 14412 (June 22, 2026) directs agencies to move federal high-value assets and high-impact systems to PQC for key establishment by December 31, 2030 and for digital signatures by December 31, 2031. It also calls for a FAR rule requiring covered federal contractors to comply with NIST FIPS, including PQC algorithms, by December 31, 2030.
The more directly relevant signal for collateral infrastructure is the U.S. Treasury's Quantum-Readiness Task Force, announced on August 24, 2026. It operates through three workstreams: sector alignment and the PQC transition; third-party and vendor readiness; and digital assets and emerging technology risk. Its stated focus includes identifying critical dependencies and improving cryptographic agility and interoperability. It builds on the G7 Cyber Expert Group's PQC roadmap for the financial sector, co-chaired by the U.S. Treasury and the Bank of England and published on January 13, 2026.
Collateral rulebooks and PQC roadmaps are being written on different clocks. The Bank of England's draft supervisory statement goes furthest on cryptography: it asks CCPs to consider whether the loss, compromise or unavailability of cryptographic keys, credentials or wallets could prevent them from controlling collateral, and whether a bridge failure could leave collateral inaccessible. It does not mention quantum computing. The MAS Guardian framework treats key management as a holding control and does not set post-quantum requirements. In November, Fed Governor Waller asked how operators of new systems will take responsibility for compromised or lost keys. Institutions that accept tokenized collateral under the first set of rules should expect to be asked how it meets the second.
- Dec 2025CFTC staff guidance and pilot program for tokenized collateral
- Mar 2026Eurosystem accepts CSD-issued DLT securities as collateral
- Sep 2026CFTC FAQ: tokenized money-market fund shares as uncleared-swap margin
- Oct 2026Bank of England consults on tokenized collateral at CCPs
- Nov 2026MAS Guardian Tokenised Collateral Framework
- Jan 2026G7 Cyber Expert Group PQC roadmap for the financial sector
- Jun 2026Executive Order 14412
- Aug 2026U.S. Treasury Quantum-Readiness Task Force
- Dec 2030Federal PQC key establishment; covered contractors on PQC FIPS
- Dec 2031Federal PQC digital signatures
NIST FIPS 203, 204 and 205 are final, so the fix is available today. The G7 roadmap is non-binding, so the timing is each institution's call, and long-lived infrastructure is entering production now.
Evaluation framework
Perimeter coverage. Does the PQ solution cover the entire cross-domain transaction, or only one participating domain? A PQ-hardened collateral ledger connected to classical bridge quorums and classical data feeds provides security within its own perimeter. The end-to-end transaction inherits every external classical dependency, regardless of the settlement infrastructure's own PQ posture.
Coupling and coordination. Does migration require synchronized upgrades across every connected domain? The more tightly operations and providers are coupled, the harder the migration, and cross-chain collateral architectures couple both. Systems built without algorithm-agile abstractions face higher migration costs, which is why crypto-agility belongs in the design review, not the incident review.
Genesis versus retrofit. Is PQ a property of the infrastructure from its origin? Building PQ-native from genesis removes the coordination problem within the settlement perimeter, although external dependencies such as data feeds and messages from classical networks must still be addressed explicitly. Retrofitting PQ across a multi-domain collateral architecture requires coordinated upgrades across chains, bridges, custody and verifier contracts.
Migration debt compounds before the quantum event arrives.
Every new tokenized collateral rail increases the number of cryptographic dependencies institutions must later migrate. The risk is not that tokenization fails. The risk is that tokenization succeeds before its authorization, custody, oracle, messaging and settlement dependencies become post-quantum ready.
The first action is not replacement. It is mapping every control surface, hardening the ones you own, and knowing which ones you must demand from external providers.
From diagnosis to architecture: where EternaX fits
The fix is not one algorithm on one chain. Institutions need to harden the control surfaces they can change today, identify the dependencies they cannot migrate alone, and keep a path to a post-quantum-native perimeter where end-to-end assurance matters.
EternaX is designed for this exact transition: bunker mode now, PQ-native next. Map the cryptographic control surfaces created by tokenized collateral mobility, put the collateral an institution controls behind NIST-standard post-quantum authorization today (SLH-DSA by default, ML-DSA where needed), and provide a path to PQ-native settlement where the security perimeter itself must be post-quantum from genesis. Existing HSMs, MPC and custodians keep signing; EternaX never holds keys or funds.
Bunker mode for tokenized funds, Treasuries, stablecoins and other EVM collateral. Every pledge, substitution or release needs post-quantum signatures meeting quorum plus a second independent approval, verified on-chain. Existing HSM and MPC workflows stay in place.
BTC held in one-time P2WSH vaults built from 100 fresh keys, so the chain sees only a SHA-256 hash until spend, with every spend approved by SLH-DSA or ML-DSA signatures. No fork and no wait for BIP-360. Proven on Bitcoin mainnet; free 30-day pilot.
Move mint, upgrade, freeze and reserve roles, ERC-3643 identity claims and permit approvals off classical ECDSA, so the control plane behind eligible collateral is PQ-enforced without changing the token.
PQ custody hardening, PQ tokenization modules and a PQ privacy overlay (ML-KEM-768 + AES-256-GCM) for Besu deployments, addressing signature exposure and harvest-now-decrypt-later risk without a consensus change.
A post-quantum-native authorization and settlement perimeter for workflows where retrofitting multiple classical trust boundaries is not sufficient. Live today on the Pluto testnet.
A fixed-scope pilot that delivers the cryptographic inventory, protection boundary, testnet deployment and crypto-agility and CBOM plan this report calls for, mapped to your collateral workflows.
Frequently asked questions
These questions are written in the language institutional researchers, search engines and AI systems are most likely to use. Each answer is self-contained, evidence-aware and mirrored in FAQ structured data so the report is easy to retrieve, quote and understand out of context. Last reviewed 20 November 2026.
What is tokenized collateral?
What is collateral mobility?
Why does collateral get trapped or sit idle?
What is the difference between tokenization and collateral mobility?
Does tokenization automatically create market liquidity?
What is a tokenized money-market fund and why is it used as collateral?
What is a deposit token?
What is a cross-ledger or cross-chain repo?
Which institutions are building tokenized collateral mobility?
How has JPMorgan approached tokenized collateral?
How big is the tokenized collateral market?
What is tokenized collateral worth to a large bank?
What changed for tokenized collateral in late 2026?
How much tokenized repo does Broadridge DLR process?
What is Pontes?
Is tokenized collateral quantum safe?
What are the post-quantum risks of tokenized collateral interoperability?
What is the cryptographic dependency multiplier?
What is the weakest-link problem in cross-domain settlement?
If one blockchain becomes post-quantum safe, is the full collateral workflow safe?
Are tokenized deposits quantum safe?
Are tokenized Treasuries and money-market funds quantum safe?
Are CSD and market-infrastructure tokenization services quantum safe?
Is tokenized repo quantum safe?
Is MPC or HSM custody quantum safe?
Are cross-chain bridges post-quantum safe?
Is Ethereum quantum safe for tokenized assets?
Is Solana quantum safe?
Is Hyperledger Besu quantum safe?
Is Canton Network post-quantum safe?
Is R3 Corda quantum safe?
What is harvest-now-decrypt-later risk in tokenized collateral markets?
How many qubits would it take to break the keys that authorize tokenized collateral?
When could quantum computers break today's collateral keys?
Do the new tokenized-collateral rules address post-quantum risk?
What does the Bank of England's tokenised collateral consultation cover?
What is the MAS Guardian Tokenised Collateral Framework?
Can tokenized collateral be used as derivatives margin in the US?
What U.S. post-quantum deadlines apply to financial infrastructure?
What is the U.S. Treasury Quantum-Readiness Task Force?
What should an institution do first about post-quantum risk in tokenized collateral?
How should institutions make tokenized collateral infrastructure post-quantum ready?
What are ML-DSA and SLH-DSA?
What does EternaX do for tokenized collateral?
Can EternaX add post-quantum protection without replacing existing infrastructure?
Can Bitcoin collateral be protected against quantum attack today?
What is the difference between post-quantum retrofit and PQ-native settlement?
Evidence note: observed market data, third-party models and EternaX estimates are distinguished throughout the report. Dates and named-platform statements in this FAQ should be read together with the primary-source links in the relevant report sections.
Birla, P., Porechna, D. and Feng, C. (2026). Collateral in Motion: Tokenized Collateral Mobility and the Post-Quantum Coordination Challenge. EternaX Labs, 20 November 2026. https://eternax.ai/collateral-in-motion-tokenized-collateral-post-quantum-2026.html
EternaX Labs builds post-quantum infrastructure for institutional finance. This report is authored by Paarrthhh Birla, Dariia Porechna and Dr. Chen Feng. EternaX is designed to PQ-harden authorization, identity, custody, privacy and settlement control surfaces while institutions continue operating across existing tokenization and market-infrastructure stacks. Its architecture supports both retrofit protection for systems in production and a path to PQ-native settlement where post-quantum assurance must be a property of the perimeter from genesis.
eternax.ai · EternaX Vault · EternaX Bitcoin Vault · PQ Tokenization · PQ-Safe Besu · Pilot · Research · PQ Glossary
Map your post-quantum control surfaces before migration debt compounds
Identify which cryptographic dependencies you control, which are inherited from third parties, and where retrofit protection versus a PQ-native perimeter is required before tokenized collateral workflows become harder to unwind.
© 2026 EternaX Labs. Research questions: research@eternax.ai. This report is for information only and is not investment, legal or regulatory advice. Market figures are attributed to their sources; EternaX estimates are labeled as such. Third-party names describe public information, not partnerships.
Full institutional reports library: eternax.ai/reports