Australian Payments Plus used a proxy token model that kept a wholesale CBDC on private HashSphere while using a proxy representation on @Hedera. The token interchange was built on Hiero. Case study:

Private networks. End-to-end digital asset management. That's HashSphere and Asseto, live @Sibos 🌴 Stop by the @hedera booth #DISM03# or book a 1:1 with our leadership team:

End-to-end digital asset management, public and private networks, plus cross-ledger interoperability. That’s what the @hashgraph team is bringing to @blockworksDAS London, Hedera booth #18#: ✅ Asseto ✅ HashSphere ✅ CLPR Stop by to see them in action 👋

What is Hedera's CLPR? Hedera has added CLPR, invented by Hashgraph and known as "clipper," to the Linux Foundation Decentralized Trust as a new lab. The concept is simple: transfer tokens, data, and messages between ledgers without a bridge. (1) CLPR is a Bridgeless Messaging Layer Most public blockchains and enterprise-private chains operate in their own walled gardens. Most assets issued on one blockchain can't flow natively to another. In most cases, alternatives involve locking up value with an intermediary and creating a duplicate on another chain. This involves adding more trust assumptions and, at times, honeypots. CLPR follows a different approach. It uses cryptographic state proofs to let both blockchains verify each other's states. Endpoints do not assume custody. No liquidity pool sits in the middle. (2) It is designed for both private and public networks The CLPR’s first objective is to link HashSphere private networks to Hedera public networks, which involves transfers between Sphere-to-Sphere and Sphere-to-Hedera. Because HashSphere uses Hedera technology and aBFT, the transfer was intended to be as fast as settlement on the underlying network. (3) CLPR consists of two phases Firstly, each ledger operates its endpoints, which use the proofs to validate the transaction. These endpoints do not hold any value. If an endpoint fails, the transaction can stop and resume after the required proof is submitted. Second, when both ledgers support CLPR out of the box, the validators become endpoints. They validate one another through their own proof protocol. In case both ledgers are aBFT, Hashgraph claims the transaction itself becomes aBFT. (4) The issue is that of trapped liquidity CLPR is more than just a token transport system. The same channels serve for data communication, contract-to-contract calls, and steady streams of data between ledgers. The early adopter program focuses on institutional use cases: cross-border payments, cross-ledger settlements, and collateral movement. The main question is how cryptography-based proofs between ledgers can eliminate the intermediary that has characterized the cross-chain process until now. CLPR was designed with this question in mind, and it now has to prove it.

DvP bond settlement. Cross-border PvP FX. Intercompany treasury netting. Private transfer. These aren't hypotheticals. They're the actual settlement workflows of Tier-1 banks and multinationals and they all require transaction privacy that most networks can't deliver. Behind the Ledger Part 1 shows how HashSphere makes them possible today. 👉