Swift blockchain ledger requires key internal layers, Taurus co-founder warns

Taurus co-founder Lamine Brahimi said banks must deploy their own permissioned ledgers, wallet infrastructure and tokenization and smart-contract capabilities before they can connect to Swift’s new blockchain-based ledger. Swift’s system acts as an orchestration layer to enable 24/7 cross-border transfers of tokenized deposits while leaving final settlement and banks’ core systems in place.

By AI Newsroom· Reviewed by Pranav, Founder & Editor-in-ChiefPublished 1 minute agoUpdated 1 minute ago0 views

Swift blockchain ledger requires key internal layers, Taurus co-founder warns

Why It Matters

The comments clarify that Swift’s ledger does not replace banks’ internal custody or settlement systems and that meaningful adoption will require institutions to build or buy additional digital-asset infrastructure. That requirement affects how quickly and broadly tokenized-deposit rails can scale across the banking sector.

Key Facts

Source / date: CoinDesk interview published Oct. 7, 2026
Speaker: Lamine Brahimi, co-founder and managing partner of Taurus
Three required capabilities to connect to Swift ledger: A bank-owned permissioned ledger, digital-asset wallet capabilities, and tokenization plus smart-contract capabilities
Swift's ledger role: An orchestration layer for moving tokenized deposits around the clock, not a replacement for banks' internal systems
Banks that completed live transactions on Swift ledger: HSBC, Standard Chartered, DBS and Citi

Taurus co-founder Lamine Brahimi said banks must have three internal technology layers in place before they can directly connect to Swift’s new blockchain-based ledger: a permissioned ledger that can interoperate with Swift’s chain, wallet-management functionality, and tokenization plus smart-contract capabilities to integrate with Swift’s contracts. He made the comments in an interview with CoinDesk, characterizing Swift’s ledger as an orchestration layer rather than a replacement for banks’ back-office or settlement arrangements. Swift has positioned the ledger as a way to enable continuous, cross-border movement of tokenized deposits while leaving final settlement to existing systems. The network has already processed live transactions: HSBC and Standard Chartered executed the first interbank transfer in August, and DBS and Citi later completed a weekend dollar payment that settled in minutes instead of taking up to two business days. Brahimi said the additional infrastructure requirement is not necessarily a major obstacle for banks that already issue or custody digital assets, and he does not expect it to prevent Swift from maintaining its central role in cross-border messaging. He described the ledger as an early-stage product that gives banks an option to move money 24/7 without forcing them to abandon existing rails. Taurus announced integration with Swift in August and says its platform bundles the three needed layers — permissioned ledger, wallets and tokenization/smart-contract tools — which could reduce the need for banks to assemble multiple vendors. Swift reported in July that 17 banks were preparing live tokenized-deposit transactions; the organization’s messaging network still underpins roughly $1.5 quadrillion of money movements annually. Brahimi also noted that tokenized deposits to date have mostly been an institutional tool used by very large banks, and wider interoperability is required for broader adoption between institutions.