Tokenization and Trust

Tokenization is taking hold. That much is settled. It is showing up in financial market clearing and settlement, payments, and in products that did not exist three years ago. What is not settled is what “tokenization” actually means.

My read: the majority of tokenization efforts are best categorized as updating existing flows between existing parties using new DLT technology. Improving flows is not the same thing as remaking a market, and the press releases rarely distinguish between the two. I recommend you parse the hype carefully as it is at or near its apex.

Regular readers will recognize the theme, and I laid out the taxonomy in 101 Update: CBDCs, Stablecoins and Tokenized Deposits, and also argued in Stablecoins: A New Model of Trust enabled by Technology that the defining innovation is the trust architecture rather than the technology, and applied it most recently to SWIFT’s blockchain announcement in Parsing the Hype.

Continue reading

SWIFT – Tokenized Payments/Deposits – Parsing the Hype

Last week SWIFT announced that 17 of its member banks tested its new blockchain ledger, positioning the network for “tokenized cross border payments” (SWIFT press release). Cue the headlines. My view: this is a me too announcement from an incumbent that is meaningfully behind, and it does not change the trajectory of where tokenized money is actually settling.

The real story is that the big banks are not waiting for SWIFT. They are building their own tokenized deposit networks, joining Canton, integrating with commercial customer platforms like Fireblocks, and quietly redrawing the settlement map. SWIFT gets to be one option among many, useful when a correspondent bank leg or a customer requirement forces its inclusion. It is no longer the default.

Regular readers will recognize this thesis from prior posts. See JPMorgan, Citi and TCH: Tokenized Deposits ON Chain, Augustus Protocol and Emerging Settlement Standards, and the 101 Update on CBDCs, Stablecoins and Tokenized Deposits for the underlying architecture and taxonomy. This post extends the thesis by explaining what the SWIFT announcement actually tells us and what it does not.

Continue reading