# RWA Daily Update - 2026-10-09

## Lesson title

A blockchain can record a fact without proving it

Access date: October 9, 2026 (PDT), checked with the local system clock.
Publication: https://managingexpectations.net/rwa.html
Status: educational review of established research, not a new announcement.

## Authoritative publication checked

Chanelle Duley, Leonardo Gambacorta, Rodney Garratt and Priscilla Koo Wilkens, "The oracle problem and the future of DeFi", BIS Bulletin No 76, September 7, 2023.

- Official landing page: https://www.bis.org/publ/bisbull76.htm
- Working official full PDF: https://www.bis.org/publications/bulletin-76-oracle-problem-and-future-defi.pdf
- Landing-page legacy PDF link: https://www.bis.org/publ/bisbull76.pdf
- Source class: research authored by economists and published by BIS; the publication explicitly says views are those of its authors, not necessarily BIS.
- Full PDF retrieved using Python urllib and extracted with pypdf: 9 PDF pages, 1,222,307 bytes. Printed pages start at PDF page 3.

## Extracted facts and claim mapping

1. Printed page 2 / PDF page 4, "Oracles": "Oracles are third parties that collect and disseminate data on real-world events." The section explains transmitting those data to the blockchain so contracts can reference them. Supports the plain-English definition.
2. Printed page 3 / PDF page 5: software oracles use APIs/databases; hardware oracles use peripherals including probes and sensors; human oracles obtain information from people. Supports the input-source examples.
3. Printed page 3 / PDF page 5, "The oracle problem in DeFi": conditional payments can help address trade-finance frictions, but "if the data used to direct contingent actions are unreliable due to oracle manipulations, the original financing problem persists." Supports the distinction between executing instructions correctly and verifying external events.
4. Printed page 4 / PDF page 6, "Living with the oracle problem: the role of trust and governance": discusses multiple oracles for redundancy and cross-verification, while identifying complexity, efficiency and scalability trade-offs.
5. Printed page 4 / PDF page 6, "DeFi versus TradFi": discusses unclear recourse without oversight and the consequences of false data driving immutable contracts. The lesson does NOT generalize that every modern tokenized arrangement is unchangeable or lacks administrative controls.

## Educational interpretation and limits

- The shipment-arrival example is hypothetical and our explanatory application of the trade-finance discussion, not a reported transaction or quotation from the paper.
- Questions about independent checks, conflicting reports, pause authority, correction and legal remedies are editorial diligence questions, not a universal regulatory checklist.
- On-chain agreement on a reported input does not independently verify the underlying physical event. Separate data-source reliability from ledger execution.
- The paper's pessimistic forecast about pure crypto DeFi is the authors' analysis. It is not used as proof that all institutional RWA arrangements fail or that oracle safeguards cannot work.
- No product endorsement, investment recommendation, return estimate, buy/sell language or claim of guaranteed safety.

## No-hype summary and novelty

A reliable automation system still needs reliable external inputs and accountable handling of disputes. Multiple feeds can help with checking, but add costs and do not remove the need to examine who produced the underlying information.

Reviewed prior daily lesson titles through October 8 and searched existing notes for oracle references. September 11 discussed FX pricing and liquidity providers; September 16 discussed fund NAV data distribution; October 8 covered audit scope. Today's distinct focus is external-event verification in conditional trade-finance payments, using a newly added official research source rather than repeating a platform or fund launch.

## Practical watch question

Who verifies the real-world event before the tokenized payment becomes irreversible?

## Retrieval notes and secondary background

- Web search available; used only to discover official BIS material.
- The legacy PDF URL returned a landing-page extract rather than the report body through web_extract. Recovered by retrieving the direct /publications/...pdf URL with Python urllib; confirmed PDF parsing and read the full document.
- Also checked https://www.bis.org/fsi/fsisummaries/exsum_23905.htm ("Financial stability implications of tokenisation - Executive Summary", August 28, 2025). The extraction was partial; no lesson claim relies on that partial extract.
- No blocked or snippet-only claims were used as substantive evidence.