Questions / Question 05
Question 05, Delivery path
How does a tokenised asset move between blockchains without breaking settlement or title?
For delivery and operations leads at a bank, asset manager or market infrastructure who are choosing where a tokenised asset will live, and who need to know what happens when it has to move to another ledger or back to a traditional account.
Who’s asking
Raised in consultations and talks by
Listed because each raised this question in public. That doesn’t mean any of them has read or endorsed this page.
The short answer
Not by a standard route yet. IOSCO names the lack of interoperability across blockchains as a key structural challenge. In the one move we can read in detail, DTC says it would burn the token on one chain and issue a new one on another, while registered ownership doesn’t change.
Standard setters agree on the gap. IOSCO lists missing interoperability across blockchains among the things holding tokenisation back, and the FSB adds the link to traditional infrastructure. One technical route is a bridge, which the FSB defines as a protocol that issues a representation of an asset on another platform. IOSCO and the IMF both warn that bridges give attackers a target. Claims 1, 2, 3, 4 and 5.
The clearest documented design is DTC’s. In its request attached to the SEC staff’s no-action letter, DTC says a participant can ask to move a token to a wallet on a different blockchain. DTC would burn the old token and issue a new one. Going back to the traditional system works the same way: burn the token, credit the ordinary account. Through all of it the securities stay registered to DTC’s nominee, and DTC’s own tracking system is the official record of tokenized entitlements. Claims 13, 14, 15, 16 and 17.
Read the limits with it. The staff letter covers a pilot version and is withdrawn three years after launch. The staff say they don’t necessarily agree with DTC’s analysis. DTC also says it won’t give tokenized entitlements any collateral or settlement value in its own risk management. Claims 19 and 20.
Canton is the worked case here, because DTCC says its service is integrated with it. Canton’s docs describe moving a contract between synchronizers, the services that order and confirm transactions, as two separate steps with a pause in between. The trade itself then settles in one transaction where both legs happen or neither does. Claims 21, 22, 23, 24 and 25.
The rest of this paragraph is our assessment and sits outside the graded answer. Title survives the documented move because one register stays in charge. Settlement risk doesn’t vanish. It moves to the gap between the burn and the new issue, and to the legal question of when each step is final, which authorities still list as open. Claims 6, 8, 10 and 27.
In DTC’s description, a move to another chain means one token is burned and another is issued, and registered ownership doesn’t change.
We grade this answer announced. The gap is confirmed by IOSCO’s report. The mechanism rests on DTC’s own description of its service, in the request attached to an SEC staff letter and in the staff’s summary of it, so the answer is graded announced. How we grade.
Taking this to a committee?
We turn the most requested answers into Briefs: the working behind the answer, as files you can edit. This answer stays free either way.
How a documented move works, step by step
- Start with the register. Before any move, find which record your asset’s operator treats as the ownership record. In DTC’s description the securities stay registered to its nominee, Cede & Co., the whole time, and DTC’s tracking system is the official record of who holds which tokenized entitlement. Claims 14 and 17.
- The holder instructs the operator. A DTC participant with a token in a registered wallet tells DTC to convert it to a registered wallet on a different blockchain. Claim 13.
- The old token is destroyed and a new one is issued. DTC says it would burn the original token and issue a new one on the new blockchain. Claim 13.
- Going back to a traditional account is the same move in reverse. DTC burns the token, debits its omnibus account and credits the participant’s ordinary account. Until a token is burned, the matching securities can’t leave the omnibus account, so the same holding can’t be used twice. Claims 15 and 16.
- Inside Canton, a move between synchronizers takes two steps. A synchronizer is the service that orders and confirms transactions for the contracts assigned to it. The contract is unassigned from the first and assigned to the second, and it can’t be used in between. Claims 22, 23 and 24.
- Settlement waits until everything sits in one place. Canton’s docs describe reassignments bringing contracts to a common synchronizer, where one atomic transaction settles the trade, meaning both legs complete or neither does. The token standard says a transaction’s input contracts must all sit on the same synchronizer. Claims 25 and 26.
Exhibit 1
Title holds because one register stays in charge. Settlement risk sits in the gaps.
The documented move, step by step. The bar on top is who owns the asset. The dashed boxes are where the asset can’t be used, and where no source says who carries a loss.
Until a token is burned, the matching securities can’t leave the omnibus account, so the same holding can’t be used twice.
Steps 01, 02 and the exit are DTC’s description of its pilot service, graded announced. Steps 03 and 04 are Canton’s documentation, also announced. The risk windows are our assessment, graded speculated.
Exhibit 2
Three ways an asset changes ledger
| Design | Who moves it | Which record counts | Where the risk sits | Grade |
|---|---|---|---|---|
| Burn and reissue by one operatorDTC’s pilot | The operator, on the holder’s instruction. Claim 13 | The operator’s register. Ownership doesn’t change. Claims 14 and 17 | Between burn and issue. The operator can also move tokens to fix errors. Claims 18 and 27 | Announced |
| Bridge that issues a representationThe model standard setters describe | A protocol that issues a representation on the second platform. Claim 3 | The sources we read don’t say. | The bridge itself is a target for attacks. Claims 4 and 5 | Confirmed |
| Reassign inside one networkCanton synchronizers | The network, in two confirmed steps. Claim 23 | Unchanged. Each contract sits on exactly one synchronizer at a time. Claim 22 | The contract can’t be used mid-move, and stays pending if step two fails. Claims 23 and 24 | Announced |
Whether reassignment reaches beyond Canton is an open point. Our own reading is that it doesn’t, graded speculated in claim 28.
Worked case
Example Bank N.V. moves a tokenised position to Canton
Example Bank N.V. is invented for illustration. Every step below rests on a graded claim on this page.
- Check the record. The bank holds a tokenized entitlement through its custodian, a DTC participant. The securities stay registered to Cede & Co., and DTC’s LedgerScan is its official record of the token. Claims 14 and 17
- Instruct the move. The custodian asks DTC to convert the token to a registered wallet on Canton. DTC burns the old token and issues a new one. Claims 13 and 21
- Settle in one place. The token and the cash are reassigned to a common synchronizer, then settle in one atomic transaction. In between, the contract can’t be used. Claims 23 and 25
- Know what you can’t count on. DTC says it won’t give tokenized entitlements collateral or settlement value in its own risk management, and the staff letter covers a pilot that’s withdrawn three years after launch. Claims 19 and 20
Ask your committee: who bears a loss in the gap between burn and new issue? No source we read says. Claim 27
The evidence, all 28 claims
13 claims are confirmed, 13 claims are announced and two claims are speculated. The confirmed claims are texts from standard setters and authorities: IOSCO, the FSB, the IMF, ESMA, the FCA, the Central Bank of Ireland, UNIDROIT and the SEC staff on the limits of their own letter. None of them is a rule on cross-chain transfers. What DTC’s service does is graded announced, because it comes from DTC’s own request and the staff’s summary of it, and the staff don’t necessarily agree with DTC’s analysis. What Canton’s docs and token standard say is also announced. No source here is a court ruling.
Each claim has its own link, so you can cite it. Sources were opened on 20 November 2026. How we grade.
- 01Confirmed
IOSCO’s final report on tokenization says the key structural challenges in scaling it up are the lack of interoperability across blockchains and the lack of high-quality settlement assets.
IOSCO: Tokenization of Financial Assets, Final Report FR/17/25, November 2025
- 02Confirmed
The FSB lists the lack of interoperability among DLT platforms, and between those platforms and traditional financial infrastructure, among the challenges to scaling tokenisation.
FSB: The Financial Stability Implications of Tokenisation, 22 October 2024
- 03Confirmed
The FSB defines bridges as protocols that issue representations of assets on different, otherwise incompatible DLT platforms.
FSB: The Financial Stability Implications of Tokenisation, 22 October 2024
- 04Confirmed
IOSCO says APIs and smart contracts that lock up tokenized assets, used as bridges between networks, can be a vulnerability that attackers target.
IOSCO: Tokenization of Financial Assets, Final Report FR/17/25, November 2025
- 05Confirmed
The IMF’s October 2026 Global Financial Stability Report says bridges and other interoperability arrangements can introduce operational vulnerabilities, including a wider surface for cyberattacks.
IMF: Global Financial Stability Report, October 2026, chapter 3
- 06Confirmed
IOSCO describes settlement finality as a legally defined moment, after which users can be confident a transaction can’t be revoked or unwound.
IOSCO: Tokenization of Financial Assets, Final Report FR/17/25, November 2025
- 07Confirmed
ESMA’s October 2026 call for evidence says there’s a strong argument that the tokenised form of an asset already eligible as collateral shouldn’t become operationally captive to one venue, platform or infrastructure. It’s a consultation text, and it sets no rule.
ESMA: Call for evidence on CCP collateral tokenisation, 9 October 2026
- 08Confirmed
ESMA’s call for evidence says collateral must confer clear, enforceable and insolvency-protected rights that can be identified, controlled and realised without legal or operational uncertainty.
ESMA: Call for evidence on CCP collateral tokenisation, 9 October 2026
- 09Confirmed
The FCA reports that respondents to its call for input with the Bank of England wanted regulators to prioritise interoperability work, and stressed that it wasn’t simply a technical issue.
FCA: FS26/1, feedback on the call for input on the future of tokenisation
- 10Confirmed
The Central Bank of Ireland’s November 2026 feedback statement names transaction certainty as a legal question: when an on-chain transaction becomes legally final and irrevocable, including in insolvency.
Central Bank of Ireland: Feedback Statement to Discussion Paper 12, November 2026
- 11Confirmed
The UNIDROIT Principles on Digital Assets and Private Law define a transfer to include acquiring a proprietary right in a resulting digital asset, so a transfer need not deliver the same token that left. The Principles are a model for national law, and they aren’t law themselves.
- 12Confirmed
UNIDROIT’s commentary says a State’s other law, already in force, may determine what a transaction in a digital asset does to the other asset linked to it.
- 13Announced
DTC says, in its request letter attached to the SEC staff’s December 2025 no-action letter, that a participant may instruct it to convert tokens to a registered wallet on a different blockchain, and that DTC would burn the original token and issue a new one on the new blockchain.
- 14Announced
DTC says the registered ownership of securities represented by a tokenized entitlement would not change at any time, and that they would stay registered in the name of Cede & Co., its nominee.
- 15Announced
DTC says that on a de-tokenization instruction it would burn the token, debit the securities from its Digital Omnibus Account and credit them to the participant’s ordinary account.
- 16Announced
DTC says securities credited to the Digital Omnibus Account would not be transferable from it until a corresponding token is burned, to avoid the same securities being used twice.
- 17Announced
DTC says its LedgerScan system would track token movements on the blockchains, and that for recording tokenized entitlements LedgerScan’s record would be DTC’s official books and records.
- 18Announced
DTC says it would have the technological capability to transfer any of the tokens to address erroneous entries, lost tokens or malfeasance, which it calls Conditions Requiring Reversal.
- 19Announced
DTC says, in a statement the SEC staff note in their letter, that it would not ascribe any collateral value or settlement value to tokenized entitlements for its own risk management.
- 20Confirmed
The SEC staff letter covers what it calls the pilot version of DTC’s tokenization services, and says the letter is withdrawn three years after DTC launches it.
- 21Announced
DTCC says its tokenization service is integrated with the Canton Network and with DTCC’s private Besu network, with more blockchain networks to be added in 2027.
- 22Announced
Canton’s docs say every active contract on Canton is assigned to exactly one synchronizer at any given time.
- 23Announced
Canton’s docs describe moving a contract between synchronizers as a non-atomic procedure with two confirmation requests on two synchronizers, and say the contract can’t be used between the two steps.
- 24Announced
Canton’s docs say that if the second step of a reassignment fails, the contract stays pending until the situation is resolved.
- 25Announced
Canton’s docs say reassignments move contracts to a common synchronizer where one atomic transaction settles the trade: there’s no state where one party has paid cash and not received securities, or the reverse.
- 26Announced
CIP-0056, Canton’s token standard, says the input contracts of a transaction must all be assigned to the same synchronizer, and recommends that registries connect to the Global Synchronizer for settlement. It calls this only a recommendation.
- 27Speculated
Not confirmed: this is our own assessment. In the one cross-chain move we can read in detail, title holds because a single off-chain register stays in charge and the token is replaced, not carried across. The risk that’s left sits in the gap between the burn and the new issue, and no source we read says who bears it.
Our assessment, from claims 13, 14, 16 and 17
- 28Speculated
Not confirmed: this is our own assessment. A move between Canton synchronizers stays inside one network and one set of rules, so it isn’t a bridge to another blockchain. We’ve read no primary source that describes an atomic move of an asset between Canton and a different chain.
Our assessment, from claims 22, 23, 25 and 26
Who asked, and where
Every place we found this question raised in public, with a link you can open. Our buyer research adds new asks as it finds them.
- ISDA and GDFJoint response to the FCA and Bank of England call for input: how transfers across blockchains will be made enforceable, so settlement doesn’t fail and chains of title aren’t brokenJul 2026 · open
- AFMEResponse to the FCA and Bank of England call for input: where interoperability matters most, and which standards would helpJul 2026 · open
- FIAResponse to the FCA and Bank of England call for input: making interoperability between tokenisation platforms and existing market infrastructure a priorityJul 2026 · open
- TheCityUKResponse to the FCA and Bank of England call for input: where interoperability matters most, and which initiatives and standards would helpJul 2026 · open
- FCAFS26/1, the summary of responses: firms asked regulators to prioritise interoperability, including alignment with regulators outside the UKSep 2026 · open
- ESMACall for evidence on CCP collateral tokenisation: a question to the market on the interoperability challenges of tokenised collateralOct 2026 · open
- Central Bank of IrelandFeedback statement on Discussion Paper 12: respondents asked for recognised standards so tokenised holdings can move across platformsNov 2026 · open
- ISDAClarity on Chain talk, ISDA counsel: does a hedge fund need to be on the same chain as its counterparty to move tokenised collateral?2026 · open
- TD BankFintech Futures interview at Sibos 2026: interoperability between tokenised deposit networks, and the standards it needsSibos 2026 · open
- Franklin TempletonCAC26 panel on tokenised money market funds: running on ten chains, fragmentation and interoperability2026 · open
Open points
- Who bears the loss if a burn commits and the new issue fails. DTC’s request describes the steps. It doesn’t describe a failed conversion or say when each step is final in law.
- Whether an asset can move atomically between Canton and a different blockchain. We’ve read no primary source that describes it.
- How issuers that run one fund or bond on several chains keep a single ownership record. We didn’t open any issuer’s documents in this run, so the page says nothing about them.
- What DTC’s technology standards require of a blockchain before it’s approved. The letter refers to them and we didn’t open them in this run.
- What rules follow the consultations. ESMA’s call for evidence and the FCA’s feedback statement set no requirements on interoperability.
- What replaces the SEC staff letter when it’s withdrawn three years after launch. The letter covers a pilot version only.
What would change this answer
ESMA’s conclusions from its call for evidence, the FCA and Bank of England roadmap, a rule or court ruling on finality for a transfer across two ledgers, a DTC report of a reversal or failed conversion, or a Canton CIP that defines an atomic move to another network would each change this answer.
Disclosure from Mac Sibbs
I hold $CC and $CNTN. The full disclosure is on the site.
This page is general information, not legal, tax or investment advice. Found an error? Write to hello@thegoldenrecord.xyz. Corrections are dated on this page and logged in the corrections log.