# RWA Daily Update - 2026-10-05

## Lesson title
Who can approve an emergency network repair?

Access date: October 5, 2026 (PDT), checked with the local system clock. Educational review of established research, not breaking news or a claim about a particular network incident.

## Official source checked
Basel Committee on Banking Supervision, Working Paper 44, 'Novel risks, mitigants and uncertainties with permissionless distributed ledger technologies', August 28, 2024.

- Landing page: https://www.bis.org/bcbs/publ/wp44.htm
- Full official PDF successfully retrieved and text-extracted: https://www.bis.org/publications/novel-risks-mitigants-and-uncertainties-permissionless-distributed-ledger-technologies.pdf
- Sections used: 2.1 (printed pages 2-3; PDF pages 8-9) and 3.2 (printed page 8; PDF page 14). Section 3.1 (printed page 7; PDF page 13) supplies supporting continuity-planning context.
- Evidence class: official-hosted working paper; authors' analysis does not necessarily represent official Basel Committee, member-institution or BIS views. Not binding regulation.

## Extracted facts and supporting passages
1. Section 2.1, printed page 2: 'nodes must agree on changes and upgrades to the blockchain' in many permissionless blockchains. The text discusses difficulty addressing bugs and security vulnerabilities.
2. Section 2.1, printed page 3: 'Many of the governance mechanisms of permissionless blockchains occur off-chain.' It describes formal control structures and informal blogs, social networks and other forums.
3. Same page: decision-making can be 'time-consuming' and give rise to 'suboptimal results in emergencies in which timely action is necessary'. This supports the emergency-coordination angle, not a universal claim that decentralisation fails.
4. Section 3.2, printed page 8: a controller can restrict access, block/reverse fraudulent transactions and amend the code implementing the cryptoasset. The key boundary: 'The controller would not exercise control over the permissionless network itself, but over the specific tokens of a specific issuance.'
5. Section 3.1, printed page 7: monitoring network governance can inform continuity actions. Business continuity planning does not fully resolve unclear network responsibility and accountability. The paper describes fallback records and alternative chains but cautions that migration can be complex and expensive, with stress efficacy an open question at the time of writing.

## Facts versus educational interpretation
- Verified source content: the governance and controller distinctions above.
- Educational application: assess who monitors proposals, approves updates and invokes suspension or a fallback for an RWA product. These questions are our synthesis, not a prescribed regulatory checklist.
- Inference: token-freezing authority alone does not establish authority to repair the underlying network. No claim is made about a named issuer's actual powers.
- Date boundary: technology/mitigation observations are from the 2024 paper; no claim that its maturity assessment is an audited 2026 status.

## No-hype summary
Token-level controls and network-level governance are different. An issuer may administer its own token without being able to command the blockchain's validators or software upgrade process. Evaluate emergency authority and coordination, not just transaction speed.

## Watch question
Who can approve and implement an urgent repair - and what can the issuer do while agreement is pending?

## Novelty check
Reviewed prior daily lesson titles through October 4. September 24 covered fork/ownership reconciliation; October 3 distinguished approved wallets from network participants; October 4 addressed transparency and runs. Today's narrower topic is off-chain upgrade coordination and emergency repair authority, rather than another fork or allowlisting lesson.

## Access notes and unused leads
- BIS landing page and PDF web extraction were available, but the legacy PDF extractor returned an incomplete text representation with omitted passages.
- Direct Python retrieval of https://www.bis.org/bcbs/publ/wp44.pdf returned HTML rather than a PDF and could not be parsed. Used the official descriptive PDF URL above instead; validated its PDF signature and extracted the relevant pages with pypdf.
- https://www.bis.org/publ/work1226.htm was checked but concerns fiscal/monetary policy and cross-border bank lending. It was unrelated and was not used as evidence.
- No new external link needed in the page's source trail: the official descriptive PDF URL is already present. Added today's source-note link while retaining existing sources.

Educational only. No investment advice, price forecasts or buy/sell recommendation. A token does not automatically confer ownership, liquidity, safety, legality or yield.