209 похожих чатов

5 ответов

8 просмотров

This blog post explains it all, a couple minutes read https://blog.celer.network/2021/11/29/cbridge-2-0-community-driven-upgrade-incoming/

Please check the blog post I linked above. It is a 2 min read and explains it very well

Pirmyne-Malzahar Автор вопроса
| Keith | DM first, I will not
Please check the blog post I linked above. It is a...

Sounds good now I just have to learn English good enough to understand.

Pirmyne Malzahar
Sounds good now I just have to learn English good ...

New Features and Upgrade Plan Included Features This upgrade contains the following three aspects: The ability to support native tokens on the source chain. This is an overwhelming request we have been hearing from our user community. The ability to be able to send non-wrapped ETH on Ethereum to other chains directly. The ability to support arbitrary message passing with low gas cost overhead. After discussions with our developer partner, we realized that the current message format limitation does not fulfill the logic passing functionality in the most cost-effective way. Inspired by the design of layer2.finance rollups, we’ve extended the message schemas to cater to arbitrary complex logic and large message passing cross-chain and to enable endless multi-chain dApp possibilities. The compatibility for “Bridge-as-a-Service” feature. Today, cBridge supports bridging of tokens where “canonical” versions of the token-in-interest already exist on multiple chains. In the future, cBridge can also serve as the direct bridge to create the canonical mapping of a token on different chains that the project wants to connect to. This upgrade will make some of the on-chain data structure compatible with this feature.

Похожие вопросы

Обсуждают сегодня

Карта сайта