A clip from an old SWIFT webinar resurfaced on X this week, and the crypto crowd is reading it as vindication. A SWIFT representative confirms that roughly 45 to 50 commercial banks sat down around 2015 to evaluate the available distributed ledger stacks of the time — Bitcoin, Ethereum, Stellar, Ripple, and a handful of others — under an effort referenced as Project Genesis. The headline in XRP circles writes itself: SWIFT already tested it. Decompiled, the story is more interesting than the screenshot suggests.
Strip the marketing layer off and what SWIFT ran in 2015 was an architectural bake-off, not a procurement RFP. The question on the table was whether a shared, append-only ledger could replace or augment the messaging-plus-correspondent model that moves trillions through SWIFTNet every day. The candidate networks were all early-stage primitives: Bitcoin's UTXO-and-proof-of-work base layer, Ethereum's pre-Constantinople account model, Stellar's Federated Byzantine Agreement consensus, and Ripple's RPCA validator quorum. Every one of them failed at least one of the requirements a banking messaging consortium considers non-negotiable — deterministic finality the legal team can sign, identity bound to KYC'd nodes, message-level confidentiality, and throughput that does not collapse when a single corridor pushes a billion-dollar batch.
That is why the operational descendants of the work — Project Aber between Saudi Arabia and the UAE, and the BIS-coordinated mBridge initiative — did not run on a public XRP Ledger or the public Stellar network. They ran on permissioned forks and bespoke CBDC rails with institution-only validators. The cryptography stayed; the public token economics did not. Engineers who have shipped a settlement system can read between the lines: when a regulated participant lists "atomic settlement" as a requirement, what they actually want is the consensus primitive, not the asset on top of it.
There is a real signal in the resurfaced clip, though, and it cuts both ways. The signal is that the largest financial messaging network on the planet did the homework early and concluded that 2015-era public ledgers were not ready for the load. A decade of zero-knowledge rollups, BFT consensus improvements, and confidential-transaction work later, that conclusion is overdue for a re-run. SWIFT itself has been quietly piloting interlinking experiments with Chainlink's CCIP and tokenization platforms; the bake-off never actually ended, it just moved to a private branch.
What this changes for builders: stop treating the SWIFT clip as a stamp of approval and start treating it as a spec document. The requirements that knocked XRP and XLM out of contention in 2015 — deterministic finality, permissioned identity, message privacy, predictable throughput — are the exact requirements the next generation of settlement rails has to meet. Build to that contract, not to the marketing one, and the second-round evaluation is yours to lose.