Forking RenBridge
Decentralization and Building Easier Front-Ends
To further pursue our goal of making RenVM integrations and adoption as easy as possible, we’ve made some improvements to RenBridge and its codebase. The improvements are two-fold:
Decentralization of UI
A UI that is free from centralized services is one of the many components in RenVM’s pathway to decentralization. With the release of RenBridge 2.1, it no longer relies on any centralized system for order storage.
The team has removed the use of Firebase for transaction persistence and relies instead on storage by RenVM itself. This essentially works by the gateway address generating a nonce. The nonce is calculated from a 24-hour window and user wallet address, so the “storage” is achieved by scanning gateway addresses, one address for one day (and the order is retrievable by scanning said gateways). Overall, this results in a more decentralized dApp as it doesn’t rely on an external single entry API like Firebase.
Easier to Fork
Firebase added additional complexity to RenBridge so by virtue of implementing the above, the new codebase is far easier to fork and get up and running! To further its simplicity, the Ren team has designed an easy guide to get you started. If you are looking to create a cross-chain bridge or integrate RenVM into your DeFi application, forking RenBridge is a great place to start!
The tutorial can be found below:
Looking forward
RenBridge 2.1 will be deployed in the coming days and we’re excited to see what new use cases it will inspire! As always if you have any questions, get in touch and we can help you get started.
Onwards and upwards,
— Michael Burgess, COO
About Ren
Ren is an open protocol that enables the movement of value between blockchains.
Website | Docs | Telegram | Announcements | Twitter | Reddit | Github
