Since June, the Ren dev team has been busy testing, improving, and stabilising the RenVM Testnet in preparation for its upcoming release. Over the last month, we have continued this rigorous testing and are now in the final stages.
If you want to be one of the first to get your hands on the release of our developer documentation/tools, let us know by signing up. So far, we have had expressions of interest from several dozen projects and individual developers, and the number continues to grow week by week!
Now, let’s dive into what was achieved since our last development update.
- At the end of June, the Ren dev team published a release candidate of RenVM Testnet to a small group of projects that have been helping us design, test, and improve RenVM. We have been gathering feedback from this group on the user experience, the development experience, and bugs that need fixing. Very soon, we will be releasing RenVM Testnet to the whole community.
- In anticipation of this release, we‘ve expanded our Developer Docs. We have added more explanations about how RenVM works, simple examples, more complex examples that show how to integrate with real-world projects (like this one), and guided tutorials. Our Developer Docs are now ready and waiting.
- We have started an open discussion on GitHub about Ren. This includes feature requests, improvements to existing features, discussions about governance, and the road to the becoming truly open-source. As RenVM is adopted and becomes used by more and more people, this will become the place where everyone can be heard.
- RenVM now has a new transaction management system that allows it to process multiple Bitcoin/ZCash (and other) transactions as one transaction. This makes RenVM cheaper, faster, and better for everyone.
- Designs for the next version of the Command Center have been finalised after receiving feedback from the Ren Ambassadors. We are now starting development and expect to roll out a new feature on a fortnightly schedule, in line with our sprint cycles.
- We have started rebuilding our P2P networking library as an open-source library,
🌪 airwave, so that others can see how it works, help build their own systems, and contribute to its development. It continues to be a work in progress as its design is finalised, documented, and tested.
- Our multi-chain infrastructure for Ethereum, Bitcoin, and ZCash has been revamped to be faster and more reliable, especially in testnet environments (which are typically not as well maintained). This includes ancillary libraries which handle de-duplication, automatic retries, and more, without disrupting other components.
- The underlying storage drivers for storing transactions, blocks, and other information have been redesigned to improve the crash resilience and reboot recovery of individual Darknodes. This means that if your Darknode crashes, it will be able to recover itself before you risk losing any rewards.
It has been another busy month for the Ren dev team. Our Testnet gets closer and closer every day and, as it approaches, we are growing more excited to share what we have built with the entire community. The feedback received so far has given us a lot of confidence in the stability, usability, and great necessity of RenVM.
Interoperability is on the horizon. Get ready for it!
— Loong Wang, CTO, Ren