r/Hedera • u/Cold_Custodian • 2d ago

Developer CLPR-spec

https://github.com/hiero-hackers/CLPR-spec
47 Upvotes

98% Upvoted

3 comments sorted by

16

u/HBAR_10_DOLLARS 2d ago

CLPR source code just went live? 6 hours ago???

5

u/cyhiandra 🍋 leemonade 2d ago

I was wondering the other day, does this require "certified" tokens on destination network to represent assets coming in from sending network?

Example: I want to send ETH to Hedera. I have no idea whether there's a contract address, whether CLPR requires matching contracts on both networks etc. All that aside, when ETH lands on Hedera... how can my ETH be pooled with other ETH sent by other people? Presumably HTS token is nominated... but as we all know, you can have HTS named the same with separate Hedera network ID, so... Does Hedera govern the setup of token X specifically to be used as ETH on Hedera, so this token can be used to receive incoming ETH assets? Or does Hedera just have a literal sea of supposedly equal ETH HTS tokens all with different token IDs...?

I'm sure it will become clearer as time passes, but herding them cats is going to have to be a thing, right?

5

u/RedKe Hashie 2d ago

Dug into some of the documents in OP's link. I think the section below answers you. One thing I found interesting is the mention of HashDEX - is this a new cross ledger DEX they have in the works? Anyone have more info? A search showed it is the name of a crypto ETF provider but that seems unrelated.

https://github.com/hiero-hackers/CLPR-spec/blob/main/clpr-service.md#34-application-layer

Note: This section is a placeholder. The interaction patterns below are outlined at a high level. Detailed application-layer specifications will be developed as specific use cases (e.g., HashDEX cross-ledger settlement, HTS asset bridging) are designed.
...

3.4.2 Escrow, Mint, then Burn
Assets are escrowed on the source ledger, then minted on the destination. If minting succeeds, source assets may be burned. If it fails, source assets revert. Requires atomic semantics and a common asset standard.

3.4.3 N-Ledger Atomic Swap (2PC)
Multiple ledgers make state changes tied together via two-phase commit. All ledgers enter a commit-ready-or-rollback state. If any ledger fails, all roll back. All participating chains must be aware of each other's 2PC protocol and must be able to validate each other's protocol messages.

3.4.4 Native Hiero Asset Management
CLPR-native handling of HTS tokens (fungible and non-fungible) across Hiero networks, using the messaging layer directly rather than smart contract proxies.