![]() ![]() It can be 25 if you are a typical app developer or 500 if you are super cautious Currently, bridge implementation decides X for the app developer, but soon app developers will be able to determine X for themselves. Trust that Ethereum blocks are final after X confirmations.Specifically, to trust the bridge, you need to: There is no authority outside Ethereum miners and NEAR validators. ![]() So we built a bridge, called Rainbow Bridge, to connect the Ethereum and NEAR blockchains, and we created the lowest possible trust level one can have for an interoperability solution - you only need to trust what it connects, the NEAR and Ethereum blockchains, and you don’t need to trust the bridge itself. We want them to have the same asset on both blockchains and even have apps that seamlessly communicate across the boundary. ![]() For example, we can leverage performance on one blockchain while leveraging community and ecosystem on another blockchain.Īt NEAR, we do not want Ethereum developers to choose between NEAR and Ethereum and commit to only one. We want to freely move our assets and data between the blockchains, or even better - run our product on several blockchains at the same time and leverage each of them. There are lots of blockchains and scalability solutions, and it is hard to decide which one to use when we are building a product, especially when it means committing with the assets or data.
0 Comments
Leave a Reply. |