# RWA Daily Update - 2026-09-24

## Lesson title

A blockchain fork does not double the underlying asset

Access date: September 24, 2026 (PDT). This is a new educational angle using an established official source, not a claim of breaking news or a recent fork incident.

## Authoritative source checked

Securities and Futures Commission of Hong Kong, Circular on intermediaries engaging in tokenised securities-related activities, November 2, 2023.

- Official page: https://apps.sfc.hk/edistributionWeb/gateway/EN/circular/doc?refNo=23EC52
- Official PDF: https://apps.sfc.hk/edistributionWeb/api/circular/openFile?lang=EN&refNo=23EC52
- Retrieval: web extraction returned a partial page; direct Python urllib retrieval of the official PDF succeeded. The 238,101-byte PDF was parsed with pypdf and contains seven pages. Relevant passages were read from PDF pages 2 and 4.

## Extracted facts and claim mapping

1. Paragraph 7, page 2: tokenised securities are fundamentally traditional securities with a tokenisation wrapper; existing securities legal and regulatory requirements continue to apply.
2. Paragraph 8, page 2: intermediaries should manage ownership and technology risks. The circular explicitly lists "forking, blockchain network outages and cybersecurity risks".
3. Paragraph 19, page 4: material information and risks should be disclosed clearly and comprehensibly.
4. Paragraph 20(a), page 4: material information includes "whether off-chain or on-chain settlement is final".
5. Paragraph 20(d), page 4: material information includes "key administrative controls and business continuity planning for DLT-related events".
6. Footnote 5, page 4: examples include cyberattacks, network failures, forks, lost administrative or investor cryptographic keys, and unauthorised transfers.

## Facts versus educational interpretation

- Official-source facts: the risk categories and disclosure expectations above.
- Plain-English explanatory definition: a fork can leave competing ledger histories. Not every fork necessarily produces two enduring networks or duplicate tradable tokens.
- Illustrative example only: a bond token visible on two branches is not a reported incident. A copied digital record does not by itself create a second underlying bond or double the issuer's payment obligation. The actual claim depends on the legal arrangement and recognised record.
- Derived due-diligence questions: who chooses the recognised branch, whether transfers can be paused, and how discrepancies are reconciled. These are not quoted universal legal requirements and do not imply all products have identical administrative powers.
- Jurisdiction: Hong Kong regulatory guidance, not Canadian legal advice or a worldwide rule. No claim is made that this circular is a complete statement of current requirements in every jurisdiction.

## No-hype summary

An RWA's normal transfer workflow is only part of the design. A network split needs a legally and operationally defined recovery path. Ledger duplication alone is not duplicated real-world value. Read the documents that identify the authoritative ownership record, finality rules and accountable recovery operator.

## Practical watch question

If the ledger splits, which record proves my claim, and who has authority to restore it?

## Novelty and access notes

Reviewed prior daily lesson titles through September 23. The August 11 SFC lesson covered general product-and-technology due diligence; today's narrower lesson concerns competing ledger histories and recovery authority. September 22 covered concentrated operational failure, not fork reconciliation.

An initial research attempt at https://www.bis.org/cpmi/publ/d225.pdf returned only partial content through web extraction. Direct urllib retrieval returned HTML rather than a PDF, causing a PDF parse failure. That incomplete retrieval was not used as evidence for today's lesson. The SFC PDF provided the verified source instead. No web-search claims or third-party snippets were used.

## Editorial boundary

Educational only; not investment, legal, tax or custody advice. No buy/sell recommendation, yield forecast, product endorsement, or claim that tokenisation guarantees ownership, liquidity, legality or safety. No new external link was needed in the page source trail because the official SFC circular is already listed. Existing historical notes remain intact.