LF Decentralized Trust added Swift, Wells Fargo and 13 other members on September 24 while also moving Hashgraph-developed CLPR into a new open-source lab, giving institutional crypto teams a fresh test bed for cross-ledger messaging rather than another finished production rail.
| What you need to know |
|---|
| LF Decentralized Trust said Swift, Wells Fargo and 13 other organizations joined its membership roster on September 24. |
| The same update introduced CLPR as a bridgeless cross-ledger messaging protocol lab contributed by Hedera and developed by Hashgraph. |
| Hashgraph says CLPR uses state proofs so ledgers can verify each other without bridges, pooled liquidity or intermediary validator networks. |
| The useful reading is cautious: this is an open-source lab and early adopter program, not proof that banks are already moving live value through CLPR. |
The signal sits in membership and plumbing
The headline names matter because Swift and Wells Fargo sit close to the institutional payment and banking stack, but the more useful detail is the kind of infrastructure LFDT is trying to gather around them. In its September 24 announcement, LFDT listed 15 new members and paired that with technology updates for CLPR, Panurus and Hyperledger Cacti 3.0.
CLPR is the piece crypto readers should separate from the membership roll-call. LFDT describes it as a new bridgeless cross-ledger messaging protocol lab. The stated design uses state proofs so independent ledgers can verify each other’s state directly, without bridges, pooled liquidity or intermediary validator networks. That puts the project in the same problem area that has frustrated tokenized asset pilots for years: assets, messages and settlement instructions often stop at the boundary of one ledger.
Hashgraph wants developers in the room early
Hashgraph’s own CLPR contribution post frames the move as a code contribution and a call for participants in a Cross-Ledger Early Adopter Program. The program targets financial institutions, fintechs, asset issuers, liquidity providers and corporations, with three initial use cases: cross-border payments and in-flight FX, cross-ledger settlement, and collateral mobility.
That language matters because it keeps the claim bounded. CLPR is being opened for experimentation and contribution inside LFDT Labs. It is not a bank deployment announcement, and it does not say Swift or Wells Fargo are using CLPR in production. A fair read is that open-source governance is being used to reduce the vendor-risk question around cross-ledger plumbing before regulated institutions decide what, if anything, to build on top.
Panurus adds a tokenization thread
The same LFDT update also introduced Panurus, a platform-neutral token infrastructure project that evolved from the Hyperledger Fabric Token SDK lab. LFDT says it has already been deployed in CBDC projects in multiple markets and is meant to address privacy, performance and compliance requirements for tokenized assets.
That makes the announcement broader than one interoperability lab. LFDT is packaging three adjacent institutional problems: how new members coordinate, how ledgers communicate, and how tokenized assets are managed under real operational constraints. For CryptoFocus readers, the practical takeaway is not that a single protocol has won. It is that the institutional tokenization stack is still being assembled in public, and the newest LFDT update moves more of that assembly into neutral open-source venues.
Sources
Frequently asked questions
Did Swift or Wells Fargo announce a live CLPR deployment?
No. The available announcements say they joined LF Decentralized Trust. CLPR is described separately as a new LFDT lab and early adopter track.
Why is CLPR described as bridgeless?
Hashgraph says CLPR uses state proofs so ledgers can verify each other directly, rather than relying on bridges, pooled liquidity or intermediary validator networks.
Why does this matter for tokenization?
Tokenized assets often need identity, compliance, settlement and messaging to work across separate systems. LFDT’s update puts interoperability and token infrastructure under open-source coordination at the same time.
