The engineering team at RND has officially tagged a release candidate for Regen Ledger v5.0. A thorough auditing and testing process has been underway for the last three weeks and will continue through the release candidate phase to ensure the success of the software upgrade if the proposal is approved by the community.
As usual, the software upgrade on mainnet (Regen Mainnet) will be preceded by an upgrade on our stable test network (Redwood Testnet), providing an opportunity for validators to participate in a software upgrade on a live network before going through the same process on Regen Mainnet. The validator upgrade guide will be made available once an official release has been tagged and we are ready to submit the on-chain proposals for Regen Mainnet and Regen Redwood.
We will not perform an upgrade on our experimental test network (Hambach Testnet) and we will consider rebooting the network with an experimental version of v5.0 following a successful upgrade on Regen Mainnet. If you are using Hambach Testnet to experiment with CosmWasm, please reach out and let us know who you are and what you are building.
New Features
The new features made available in Regen Ledger v5.0 are as follows:
DAO support via Group Accounts
Regen Ledger now includes the group module made available in Cosmos SDK v0.46. The group module started out as a custom module built within the Regen Ledger repository and has since been added to Cosmos SDK as a core module refined and maintained by the Cosmos SDK core developers. The group module enables the creation and management of on-chain multisig accounts and voting for message execution based on configurable decision policies.
What does this mean within the context of Regen Ledger functionality? All entities on a Regen Ledger chain can now be managed by a group account. For example, the role of the credit class admin can be assigned to a grou
Thanks for the writeup. We are excited for the groups module! Looking forward to learning how the csDAOs can start using it. Will there be a UI for managing these things, or CLI only for now?
This is a HUGE upgrade. I am impressed with how quickly this release is coming on the heals of the marketplace launch. Kudos to the core dev team!
I am hugely in support of the upgrade before the holiday season. I understand there won’t be fully UI for the groups module yet, but think that once that is taken care of (ideally with Keplr integration as well) the usability of Regen Network will be transformed.
We recently discovered an issue in the release candidate for Regen Ledger v5.0 and have resolved the issue. A couple issues were also discovered by the core developers of Cosmos SDK in the gov and group modules made available in Cosmos SDK v0.46 and those issues have also been resolved and a new Cosmos SDK patch release was made available yesterday.
In order to perform a software upgrade on mainnet before the holidays, we would have needed to tag an official release yesterday and submitted a software upgrade proposal at the end of the day yesterday or first thing this morning. This would have required us to expedite our release process and therefore we have decided to post-pone the upgrade until after the holidays.
We will be spending the next week continuing auditing and testing and may still choose to tag an official release and upgrade our stable test network (Redwood Testnet) before the holidays but the RND engineering team will not be submitting a software upgrade proposal for mainnet until the first week of the new year.
Upgrade Timeline
We are currently looking at the following timeline:
November 7th - beta release tagged and testing/auditing begins
November 9th - upgrade overview presented on community dev call
November 28th - release candidate tagged and forum post submitted
December 14th - 15th - second release candidate tagged
December 19th - 21st - official release tagged
January 3rd - 5th - software upgrade proposals submitted, voting period begins, validators start preparing for the upgrade
January 10th - 12th - voting period ends and, if the proposal passes, the software upgrade is executed
Note: The above timeline is an estimate and subject to change. Any changes will be first announced here in this discussion thread and links to this discussion announcing updates will be shared in other channels including the Governance channel of our Discord server.
Thank you again for all your support and patience.
The RND engineering team has officially submitted the on-chain proposal for the upgrade to Regen Ledger v5.0. Given a one week voting period, Fridays are generally not the best day, January 16th is a national holiday in the US, we chose a block height that is estimated for January 17th at 1600 UTC.