Tweet

CelerNetwork

29 Oct, 5 tweets, 2 min read

https://twitter.com/0xangelfish/status/1454120116862414854

In locally verified bridges, since liquidity is also self-managed by the relayers themselves, there is additional complexity in node scheduling and handling griefing as mentioned below (malicious relayer locks user fund). Celer cBridge 2.0 is the first to solve these challenges.

https://twitter.com/0xangelfish/status/1454120116862414854

https://twitter.com/CelerNetwork/status/1449146677558857731

For griefing challenge:

https://twitter.com/CelerNetwork/status/1449146677558857731

https://twitter.com/CelerNetwork/status/1448383819405357057

For coordination:

https://twitter.com/CelerNetwork/status/1448383819405357057

https://twitter.com/CelerNetwork/status/1447415169328451585

And finally, Celer cBridge 2.0 is the ONLY bridge that supports both locally verified mode and externally verified mode under a unified architecture to cater to different LP and user preferences seamlessly all together with common value capture through SGN

https://twitter.com/CelerNetwork/status/1447415169328451585

For more details please check out: blog.celer.network/2021/09/22/cbr…

• • •

Missing some Tweet in this thread? You can try to force a refresh

This Thread may be Removed Anytime!

Twitter may remove this content at anytime! Save it as PDF for later use!

More from @CelerNetwork

CelerNetwork

@CelerNetwork

15 Oct

🎉🥳#TGIF and it is ELI-5 time! Today, we talk about the last topic for the self-managed model for cBridge 2.0: how cBridge 2.0's design provides the first-ever solution to the "griefing problem" in the non-custodial bridging system using the Celer State Guardian Network.

1/n So what is “griefing”? In the self-managed bridging model of cBridge 2.0’s two models, two steps are always needed for the cross-chain transaction to happen for both the bridge nodes and the user in the following sequence.

2/n Step 1 for the user: make a “time-locked” transfer to the bridge node on the source chain, where only she has the key to unlocking this transfer.
Step 1 for the bridge node: make a locked transfer to the user on the destination chain, using the exact same lock as the user.

Read 9 tweets

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!