# RWA Daily Update - 2026-09-19 ## Lesson title Automation still needs a second pair of eyes Access date: September 19, 2026 (PDT). Educational source review, not investment advice. ## Sources checked and access trail 1. BIS Innovation Hub / Project Genesis, Report 2: A prototype for green bond tokenisation by the Liberty Consortium (November 2021). Working official PDF: https://www.bis.org/publications/project-genesis-prototype-digital-platforms-green-bond-tokenisation-report-2.pdf Direct Python urllib retrieval succeeded: HTTP 200, 6,719,522 bytes, 26 PDF pages. Text parsed with pypdf. Printed pages 19 and 23 verified directly; core lesson rests on page 19, "Bond lifecycle management". This is a historical prototype report, not a new product announcement or certification. 2. BIS report landing page (legacy address): https://www.bis.org/publ/othp43.htm Web extraction returned the report overview, dated November 4, 2021, identifying Report 2 as the Liberty prototype on public permissionless blockchain infrastructure. Direct urllib returned HTTP 404. Do not treat that legacy address as a verified live link. Access failures and recovery: The legacy PDF URL https://www.bis.org/publ/othp43_report2.pdf yielded readable text through web extraction, but direct urllib and curl returned HTTP 404. A targeted search located the current official /publications/ PDF address above, which was opened and verified directly. The current PDF is the new public source-trail link. No secondary-source claims are needed for the lesson. ## Extracted facts and exact passages - Page 19 describes administration from preparation and closing through ongoing coupon payments to bond owners. - Page 19: "Every activity performed by the issuer is enforced through a maker-checker process"; the report explains that this ensures the requisite review before proceeding. - Page 19: "all actions and their associated user are included in a fully auditable log that serves as a compliance record." - Page 23 describes the prototype as operated under the issuer's auspices. The lesson does not generalize this governance model to every tokenized system. - The report's abstract says it was drafted with the Liberty Consortium's technical inputs and that its views are not necessarily those of BIS or HKMA. The described controls are prototype design statements, not independent certification of a live service's controls. ## Fact versus educational interpretation Verified report content: issuer activities undergo maker-checker review; actions and users are recorded in an auditable log; bond servicing includes coupons. Plain-English interpretation: maker-checker means separating preparation/initiation from review/authorization. Automation and human accountability can coexist. Editorial due-diligence questions, not claimed Genesis features: can one administrator initiate and approve an action, who can alter permissions, and what happens when payment instructions are wrong? The source does not establish universal recovery or rollback guarantees. ## No-hype summary The distinctive lesson is separation of duties inside a tokenized workflow, not another general bond-lifecycle overview. A ledger can preserve evidence of an action without proving that it was authorized or correct. Review controls and an accountable audit trail address different problems. Neither guarantees solvency, coupon payment, legal enforceability, liquidity or safety. ## Published lesson Tokenization can automate record-keeping and payments, but automation should not erase accountability. One useful control is the maker-checker process: one person prepares an action and another reviews it before it proceeds. It separates doing something from authorizing it. The BIS Innovation Hub's November 2021 Project Genesis Report 2 describes this approach in the Liberty Consortium's green-bond prototype. Its bond-lifecycle section says every issuer activity passes through maker-checker review. It also records actions and the associated user in an auditable compliance log. The workflow covers administration from preparation and closing through ongoing coupon payments - the interest payments owed to bondholders. These are two different safeguards. Review is intended to catch a problem before execution; the log helps establish what happened and who acted. A permanent transaction record alone does not prove that the instruction was correct or properly authorized. For an RWA platform, ask whether a single administrator can both initiate and approve an action, who can change permissions, and how incorrect payment instructions are handled. These are due-diligence questions, not features established for every platform by this report. Genesis was a prototype, not a guarantee of current commercial performance, legal compliance or payment. A second pair of eyes cannot create missing cash or remove issuer credit risk. Watch question: Can one person initiate, approve and conceal a change - or are those powers genuinely separated? ## Scope and duplicate check Prior journal notes were searched for maker-checker, dual approval and separation of duties; no earlier matching lesson was found. Earlier lifecycle and green-bond lessons remain in the source trail. Today's entry adds an operational-control lens, does not claim a recent development, and retains the educational foundation unchanged.