# RWA Daily Update - 2026-09-18

## Lesson title
A shared ledger is not a public transaction history

Access date: September 18, 2026 (PDT).
Status: educational case study of the May 2026 Project Agora report, not a new launch announcement.

## Sources checked and retrieval record

1. Bank for International Settlements (BIS), Project Agora: a shared programmable platform for wholesale cross-border payments, May 27, 2026.
   - Official report landing page: https://www.bis.org/publ/othp110.htm
   - Official full PDF successfully retrieved: https://www.bis.org/publications/project-agora-shared-programmable-platform-wholesale-cross-border-payments.pdf
   - Landing page retrieved with web extraction. Full alternative-path PDF retrieved with Python urllib: HTTP 200, application/pdf, 2,375,917 bytes, 97 PDF pages; parsed with pypdf.
   - Retrieval limitation: web extraction of https://www.bis.org/publ/othp110.pdf returned only a sparse excerpt. Direct urllib requests to that URL and https://bis.org/publ/othp110.pdf returned HTML rather than PDF, so they were not treated as verified PDF downloads. The BIS /publications/ PDF above supplied the actual evidence below.
   - Source class: official institutional research/prototype report. Findings are attributed to the report, not an independent production-security audit.

## Extracted facts and claim mapping

Page references below use printed report pages; PDF viewer pages are also provided.

- Printed p. 2 (PDF p. 7), Key features / Privacy controls: the prototype has token-level controls to hide sensitive information and transaction-level privacy groups to limit information sharing to relevant participants. Quote: "At the transaction level, privacy groups ensure that information is shared only among relevant participants in a transaction."
  - Lesson claim: sharing infrastructure need not expose every customer's details to every participant.
- Printed p. 2 (PDF p. 7), Financial crime controls: each institution implements AML/CFT, anti-fraud controls and sanctions screening independently and confidentially; the platform ensures required validations are completed before settlement.
  - Lesson claim: confidentiality does not mean skipping screening.
- Printed p. 15 (PDF p. 20), business requirement 11: "The prototype must share minimum necessary information, only with the institutions directly involved at each step of the workflow on a need-to-know basis."
  - Lesson claim: selective disclosure is a deliberate architecture requirement, not an automatic consequence of tokenization.
- Printed p. 70 (PDF p. 75), compliance analysis: "the sharing of outcome flags - even where no underlying data are disclosed - could trigger confidentiality obligations if the result can be combined with other information available to the recipient to identify the customer or account holder." Punctuation normalized from PDF extraction.
  - Lesson claim: a reduced output can still disclose sensitive information when combined with other data. The report discusses participating-jurisdiction requirements and consent; this is not a universal legal conclusion.
- Printed p. 70 (PDF p. 75), tipping-off analysis: the report says it cannot conclude that sharing compliance-check outcomes as implemented would avoid tipping-off concerns. Each participant would need its own legal analysis; regulator confirmation may be needed.
  - Editorial boundary: do not claim that an encrypted system or a yes/no compliance response automatically satisfies confidentiality or AML law.
- Printed p. 84 (PDF p. 89), key outcomes: "A shared ledger does not require shared data." Participants' data can coexist without being disclosed to every other participant; sharing is subject to jurisdictional requirements.
  - Lesson claim: a shared ledger is not necessarily a public transaction history.
- Printed p. 4 (PDF p. 9): further work includes cybersecurity, operational resilience, governance, rules, oversight and data governance for safe scalable deployment.
  - Lesson claim: prototype findings are not a guarantee of production safety or universal legal compliance.

## No-hype summary

The lesson is selective disclosure, not secrecy from regulators. Agora's report illustrates how institutions can coordinate tokenized money while restricting visibility of transaction data. Privacy controls and independent compliance checks coexist. Even a pass/fail output may create confidentiality concerns when recipients can combine it with other information. Buyers of RWA infrastructure should examine the data-access rules and legal responsibilities, not accept "private blockchain" as proof of privacy.

## Practical watch question

Who can see the underlying data, who sees only a result, and what can each recipient infer?

## Novelty and editorial limits

Prior journal notes already cover Agora's money layers, atomic settlement and real-value testing. Today's distinct lesson focuses on token-level versus transaction-level privacy and the confidentiality risks of compliance-result flags. This is a new educational angle from a previously linked official report, not newly published research.

The application to tokenized bonds and funds is an educational due-diligence inference, not a claim that the Agora prototype tested all those products. No token, investment, issuer or platform is recommended. A token does not automatically confer ownership, liquidity, safety, legality or yield. This note is not investment, legal, banking or compliance advice.