Swift's blockchain shared ledger is a permissioned distributed ledger, launched in pilot on July 9 2026, that lets banks settle tokenised cross-border payments against a single shared record instead of exchanging messages across chains of correspondent banks. It went live with 17 banks and is Swift's first move from pure messaging into ledger-based coordination of value.
​

The shared ledger is best understood as an orchestration layer over many distributed-ledger technologies rather than one chain trying to hold everything. Banks issue tokenised deposits, smart contracts coordinate transfers, Chainlink CCIP connects the surrounding networks, and Swift keeps the whole thing aligned to the ISO 20022 messaging standard while running 24 hours a day.
​

Swift's blockchain shared ledger is a shared, permissioned record on which participating banks issue and move tokenised deposits for cross-border settlement. Launched in pilot on July 9 2026 with 17 banks, it replaces the reconcile-both-sides model of correspondent banking with a single source of truth that all participants read and write to under agreed rules.
​

Swift is the cooperative that runs the messaging network more than 11,000 institutions use to instruct cross-border payments. Historically Swift moved messages, not money: the value moved separately through correspondent accounts. The shared ledger changes that by giving banks a common ledger where the tokenised representation of value and the instruction to move it live together. Swift's own program is described on SWIFT.
​

The shared ledger works by having each bank issue tokenised deposits, then settling transfers between those tokens through smart contracts on a permissioned EVM network. Swift coordinates the messaging in ISO 20022 format, and Chainlink CCIP links the ledger to roughly 70 other networks so value is not trapped on one chain. The network runs around the clock.
​

In practice, a payment that once hopped through several intermediary banks becomes a transfer of tokenised deposits recorded once, on a ledger both banks trust. The smart contract enforces the conditions of the transfer, and the ISO 20022 message carries the structured payment data that compliance and reconciliation systems already expect. The ISO 20022 standard is the same data model banks are migrating their existing rails toward, which lowers the integration cost of the ledger.
​

Consensys built Swift's shared ledger on Hyperledger Besu, an open-source Ethereum Virtual Machine client, deployed as a permissioned network. Chainlink's Cross-Chain Interoperability Protocol provides the interop layer. The design is in the Linea family of EVM engineering but is not the public Linea network; it is a private, bank-permissioned deployment.
​

Hyperledger Besu is a production Ethereum client documented at Besu (hyperledger.org), chosen because it is EVM-compatible and supports permissioned validator sets, which regulated settlement requires. Chainlink CCIP, at Chainlink, handles cross-chain messaging so the shared ledger interoperates with the wider network landscape rather than becoming an island. Building on EVM tooling means banks can reuse a large, well-audited developer ecosystem.
​

Tokenised deposits are commercial-bank deposits represented as tokens on the shared ledger. Each token is a direct claim on money held at the issuing bank. They are not stablecoins, which non-bank issuers back with reserves, and they are not central-bank digital currency. The issuer, the backing, and the supervision are all different.
​

The distinction drives who carries credit risk and how regulators treat the instrument. A deposit token keeps the money inside the regulated banking system and on the issuing bank's balance sheet, which is why banks favour it for institutional settlement. For the differences that matter in practice, see Tokenized Deposits vs Stablecoins and the primer What Is a Tokenized Deposit?.
​

The shared ledger is designed as an orchestration layer because value in 2026 lives on many ledgers at once: tokenised deposits on permissioned chains, stablecoins on public chains, and other assets elsewhere. No single chain holds all of it, so the useful layer is the one that coordinates settlement across them, which is exactly what Swift's use of CCIP signals.
​

This is the central architectural point. Connecting roughly 70 networks through an interoperability protocol is an admission that the future is multi-ledger, not one-chain-wins. The value accrues to whoever routes reliably between ledgers on cost, speed, and finality. That framing separates a shared ledger that coordinates from a chain that competes to hold everything.

Not yet. In the pilot, final settlement still relies on Swift's traditional rails and existing correspondent relationships. The shared ledger removes reconciliation friction and adds a common record, but the leg that moves value with legal finality is unchanged for now. Calling it the end of correspondent banking overstates a pilot.
​

What the pilot genuinely tests is whether tokenised deposits on a shared ledger can eventually carry final settlement across corridors without the intermediary chain. That is a meaningful shift if it works, and a measured one because it runs alongside the existing network rather than switching it off. The roster of participating banks is covered in The 17 Banks Piloting Swift's Blockchain Ledger.
​

Eco is cross-chain settlement infrastructure for stablecoins, operating as an orchestration layer across rails, which is the same category Swift's shared ledger occupies for bank money. Swift routes across networks with CCIP; Eco Routes selects between CCTP, Hyperlane, and LayerZero on cost, speed, and finality for stablecoin flows.
​

The Swift pilot validates the thesis that the durable layer in cross-border payments is orchestration across many ledgers, not a single settlement chain. Bank deposit tokens, stablecoins, and other tokenised money will coexist, and the connective layer between them is where the leverage sits. That is where Eco builds.
​

Related reading

Methodology and sources: Pilot go-live date, participant count, and shared-ledger design from Swift's July 9 2026 announcement (swift.com). Build details (Consensys, Hyperledger Besu, Chainlink CCIP) from Hyperledger, Consensys, and Chainlink primary documentation. Messaging standard from iso20022.org. Last updated July 2026.
​