In this sprint, we have re-focused on scaling interoperability and started the development on the Lynx Engine. We specifically focused on our new OneVault, which will manage keys and sign transactions for client applications. In addition, we continued to work on Load Testing and our Staking Methodology.
The list of changes includes:
- Final Load Testing for Chronos
- Lynx Engine
- Wrapper for ETH Tx
- Wrapper for BTC Tx
- OneVault: ETH and BTC Key Management
- Draft for Staking Methodology
In the next sprint, we will be working on automating Explorer deploymentand launching the Explorer on the updated protocol and generating an image for the cloud Marketplace and the Lynx Engine.
NOTE: After the release for 0.9.0, we have reset the Chronos network and purging the current data. This is so that we can run more tests on Chronos and ensure it’s stability.
New Release Management Structure
OneLedger has a new release process. We will continue to update our Master Branch on GitHub on a bi-weekly basis. However, on a Quarterly basis, we will mark a build as a Release Candidate and work with our partners to ensure they update their nodes to the Protocol version for the most recent Release Candidate. This means Chronos will be updated on a quarterly basis.
We are doing this to streamline our release process and structure it for our partners and community. We are starting this process with version 0.9.0. For example, after v0.9.0, our next Chronos update will take place on v0.10.0, while we keep pushing the biweekly updates i.e. v0.9.1, v0.9.2 and so on.