# RWA Daily Update - 2026-10-02 ## Lesson title A shared ledger still needs reconciliation with bank records Access date: October 2, 2026 (PDT), verified with the local system clock. Educational review of an existing prototype report, not a new announcement or a claim about the project's current deployment status. ## Authoritative sources checked 1. Bank for International Settlements / Institute of International Finance, Project Agora: A shared programmable platform for wholesale cross-border payments, report landing page dated May 27, 2026. - https://www.bis.org/publ/othp110.htm - Access: web extraction returned the report title, date and summary. It describes a prototype, with reduced reconciliation burdens as a potential benefit, not elimination of all reconciliation. 2. Full official report, 97 PDF pages: - Landing-page PDF link: https://www.bis.org/publ/othp110.pdf - Successfully downloaded official PDF: https://www.bis.org/publications/project-agora-shared-programmable-platform-wholesale-cross-border-payments.pdf - Access: web extraction of the short PDF URL was incomplete. Direct urllib retrieval of that URL returned HTML rather than a PDF and PDF parsing failed. The alternative BIS publications URL returned application/pdf; its PDF signature, page count and relevant text were verified using pypdf. - Local working evidence: _work/rwa-2026-10-02/agora.pdf and agora.txt (not deployed). ## Extracted facts and evidence mapping - VERIFIED OFFICIAL REPORT, printed page 10 / PDF page 15, "Project assumptions": "Balances and transactions recorded on the Project Agora platform are treated as the authoritative record for tokenised deposits and tokenised reserves." The source spells the project name with an accented final a; this note uses ASCII punctuation and transliteration for reliable public Markdown display. - Same paragraph: "Participants remain responsible for reconciling with their internal systems, and the prototype assumes continued interactions with legacy infrastructure." - VERIFIED OFFICIAL REPORT, printed page 16 / PDF page 21, business requirement 13: customer relationships, compliance obligations and reconciliation with traditional systems remain with issuing and participating institutions. The shared platform does not absorb those responsibilities. - VERIFIED OFFICIAL REPORT, printed page 82 / PDF page 87, "Limitations of the Project Agora prototype": interoperability with external infrastructures, including domestic RTGS and core banking systems, was not tested. Transactions from real-world production applications or live institutional systems were not tested in the described prototype. - SCOPE LIMIT: printed page 10 says other types of tokenised asset classes were outside the prototype scope. This is a wholesale-payment example relevant to the cash side of RWA workflows, not proof of a tested bond or fund settlement service. ## No-hype summary A shared authoritative record can reduce mismatches among participants, but it does not automatically keep every institution's internal records consistent. Reconciliation means comparing records and resolving differences; it is not the same as reversing a legally final payment. The report keeps that responsibility with institutions and explicitly limits the integration testing completed. The educational application to RWA platforms is to ask which record governs, how surrounding systems stay aligned, and who handles an exception. ## Practical watch question If the shared ledger and the bank's internal records disagree, who detects the break, which record governs, and who fixes it? ## Novelty and editorial boundaries Previous Agora lessons covered tokenised deposits/reserves, prototype status and privacy. Today's distinct focus is the explicit retained reconciliation obligation and the boundary between an authoritative platform record and internal bank records. Recommendations about mismatch detection and exception handling are educational questions derived from the report, not claims that a particular operating service has those controls. No investment recommendation, forecast, yield claim or estimate is made. A token does not automatically confer ownership, liquidity, safety or legal enforceability. ## Published lesson text A shared ledger still needs reconciliation with bank records A shared ledger can reduce disagreements between banks without eliminating the need to check their own books. Reconciliation means comparing records and investigating mismatches. It is not the same as reversing a settled payment. The May 2026 Project Agora report makes this distinction explicit. Its prototype treats platform balances and transactions as the authoritative record for tokenised deposits and central-bank reserves. Yet participants remain responsible for reconciling with their internal systems. A common record is therefore not a promise that every connected database automatically stays aligned. Why does this matter for RWA? A tokenized bond or fund transaction still needs a reliable payment side. Institutions must know how the shared record relates to the systems they use to run their business. Agora's business requirements preserve institutional responsibility for reconciliation, alongside customer relationships and compliance. There is also a testing boundary: the report says interoperability with domestic real-time gross settlement systems and core banking systems was not tested in this prototype. That limits what this report proves; it does not establish the status of later work. The lesson is to distinguish fewer reconciliation steps from no reconciliation responsibility. Ask how discrepancies are detected and resolved before treating a synchronized ledger as an end-to-end operating service.