In this sprint, we focused on our OneVault, SDK and the Protocol Transaction Layer for making a functional Domain Naming Service.
The list of changes includes:
- OneVault: Key Management and Signing
- SDK: Relay Create Domain Name and Transfer OLT Tx
- Transaction Layer
- Buy, Sell Search and List a Domain
- Level DB for DNS App
- JSON RPC Layer Changes
In the next sprint, we will continue our work on the Lynx Engine, Fix issues with the OneExplorer and lay down the cloud infrastructure for our Naming Service.
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.