Swift’s 17-Bank Ledger Pilot Runs on Ethereum Code, Settles on Legacy Rails

Swift confirmed on Thursday that 17 banks across six continents will pilot a “blockchain-based ledger” capable of moving tokenized deposits around the clock, including weekends — a structural gap the legacy correspondent-banking network has never closed. The catch for traders watching institutional crypto rails: the ledger settles transfers, but final settlement of underlying value still routes through Swift’s existing, business-hours-only messaging infrastructure, according to the announcement.

That distinction matters for anyone modeling how fast tokenized bank money can actually move. The pilot enables 24/7 transfer of tokens that represent deposits — effectively an IOU layer sitting on top of the traditional system — rather than a genuine shift of settlement finality onto distributed infrastructure. Legacy rails remain the ultimate arbiter of value, meaning the throughput gains are confined to the messaging and transfer layer, not to settlement risk itself.

GSIB roster signals scale, not decentralization

The participant list carries weight: Swift’s cooperative structure connects thousands of banks globally, and this pilot draws in institutions designated as Global Systemically Important Banks by regulators, including Citi, HSBC, BNY and Wells Fargo. Their presence signals that major balance-sheet holders are willing to test tokenized deposit transfers at scale rather than through isolated proofs-of-concept.

Structurally, though, the ledger is built with Ethereum-compatible architecture but operates as a largely centralized network controlled by Swift and its member institutions. For on-chain researchers, that’s the key read: this is not a permissionless deployment competing with public smart-contract rails, but a private, EVM-flavored ledger designed to interoperate with bank infrastructure while keeping governance inside the existing correspondent-banking cooperative.

Where the friction actually sits

The practical bottleneck traders should track is the settlement layer, not the transfer layer. Weekend and after-hours token movement solves a real liquidity-timing problem for banks holding tokenized deposits, but if final settlement can only clear when legacy systems reopen, counterparty exposure over weekends doesn’t fully disappear — it’s deferred rather than eliminated.

That gap between transfer speed and settlement finality is the same tension public blockchain infrastructure was built to remove. Swift’s pilot narrows the operational lag for banks without yet closing it, which keeps the institutional tokenization narrative running well ahead of the plumbing needed to fully back it.

For market structure watchers, the pilot is worth monitoring less for its blockchain branding and more for what it reveals about incumbent appetite: GSIB-level banks are now willing to run tokenized deposit flows on Ethereum-compatible rails, even while settlement risk stays anchored to systems built decades ago.

Read more: Circle Ships Native EURC on Base, Testing If MiCA Compliance Beats Bridged Liquidity