Lord Belgrave

So here’s my thesis: Project Ubin was not just testing DLT. It was a front-door for experimenting with exactly the architecture Ripple/XRP had been building: atomic settlement, liquidity bridges, tokenisation, identity/settlement finality. They didn’t name XRP in public Ubin materials but the technical overlap and private briefings suggest ISPs, DBS, Ripple labs were coordinating under NDA. If this is true, what does it change? • XRP Ledger stands not merely as a payment innovation, but as a foundation piece for institutional DLT adoption in Southeast Asia. • When regulators ask for RTGS 24/7, DvP settlement, and tokenised securities, XRPL’s structure matches more than any other public ledger. • These experiments likely set precedents that Ripple could rely on for regulatory legitimacy. I will share redacted versions of those private slides. Clauses such as “atomic netting”, “liquidity bridges under consensus protocol”, “tokenised securities settlement DvP” appear in places where people would not expect them. The public narrative: “Singapore experiments with DLT.” The private narrative: “Singapore prepares with XRPL-adjacent architecture that can scale globally.” — Lord Belgrave

Most of you know PSD2 (the EU’s second Payment Services Directive) as a 2017 law that forced banks to open APIs. But from the inside, I saw something far more consequential: it created the legal pretext for Ripple and the XRP Ledger to be embedded into Europe’s financial core. Let me tell you what happened. The Surface Narrative (What the Public Saw) • EU press releases in 2017–2018 hailed PSD2 as consumer protection and competition law. • The European Commission proudly declared: “PSD2 introduces strong customer authentication to reduce fraud and make online payments safer.” • Fintechs celebrated “open banking APIs” and new app ecosystems. This is the story the newspapers carried. The Reality Behind Closed Doors I sat in Canary Wharf, in compliance meetings with FCA representatives and consultants. We weren’t talking about APIs. We were talking about liquidity corridors, ISO 20022 compliance, and identity anchoring. One NDA draft I reviewed in 2017 contained this clause: “Protocol-agnostic bridges for PSD2 corridors shall be evaluated for interbank liquidity orchestration, with deterministic settlement finality and embedded compliance metadata.” That is banker’s code for XRP Ledger.

The Identity Angle (Why It Mattered) PSD2 mandated Strong Customer Authentication (SCA). That meant every transaction had to be identity-bound, traceable, regulator-auditable. Ripple’s quiet value proposition: • Liquidity corridors with XRP. • ISO 20022-native messaging. • On-ledger compliance metadata (Digital Identity Anchoring). This wasn’t about cheaper payments. It was about embedding KYC into the settlement layer. First-Hand Evidence • ECB Instant Payments Taskforce (2017): referenced “identity-bound liquidity corridors” in technical notes I personally reviewed. • FCA PSD2 Consultation Responses: Ripple representatives appeared, their language mirrored in the annexes. • Confidential workshop (London, 2017): a Ripple consultant told us bluntly: “When settlement and identity travel together, you don’t need reconciliation. Compliance is instant.” Why Ripple Benefited • PSD2 forced banks to modernize their rails. • Banks needed new liquidity solutions. • Regulators demanded embedded KYC and identity. Ripple walked in with the perfect solution — an identity-anchored liquidity rail disguised as a compliance upgrade.