Regen Testnet 1001 Results
We are proud and excited to announce the results of the Regen 1001 Incentivized Testnet (and we promise to make a better name next time!)
Focus of Regen Test 1001
The primary focus of Regen Test 1001 was to test a coordinated upgrade module. This module was completed, and merged into the Cosmos SDK and Gaia 2.0.3 version being used for the next cosmos Hub Upgrade.
This gave the Regen Network community the opportunity to achieve three main goals:
- Test the coordinated upgrade module and address any issues raised by the cosmos hub and cosmos SDK community about the functionality of this SDK module.
- Test Regen Ledger functions built for our application-specific goals of a censorship resistant ecological ledger and contracting platform.
- Coordinate with our validator pool around the governance process.
These tasks were accomplished by completing two separate network upgrades using the coordinated upgrade module..
Naming conventions in Regen Network
Regen software versions are named after watersheds or bioregion Bioregions (eco-geo-cultural regions of the world such as the amazon, the great planes, the eurasian steppe etc).
The first software version was called Choco, a bioregion between the tropical western slopes of the Andes and the pacific Ocean of South America. The next upgrade was to Amazonas, the great tropical rainforest running from the on the eastern slope of the Andes in South America to the Atlantic ocean.
Both of these bioregions are places where there are active pilots using regen network as a ledger for land health and registry for the issuance of carbon and biodiversity credits to be traded and retired in service to incentivizing ecological stewardship.
This is the story of our metaphorical journey from the Choco rainforest over the Andes to the Amazonas as a community of validators. We tracked waypoints along the way to reward our epic community of validators for this adventure in network building and metaphorical mountain range crossing.
The journey in a nut shell:
The Amazonas Upgrade
The Regen Network Amazonas, (upgrade instructions). Upgrade was a smooth test of the upgrade module. The entire network upgrade took 3 min and 14 seconds from start to finish. Several validators even used the automatic upgrade binary and stepped out for coffee and let the script run the upgrade automatically.
After the upgrade, the community became restless and the fearless @meleacrypto initiated a param change vote. This attempted param change vote lead to the end of the test net (the end was planned, the result of the param change was not).The link above explains the post mortum. Essentially the naive application of a rule change caused all validators to be jailed.
All in all the test net and was a fantastic experience for the Regen Dev team and larger community.
And now without further adieu we give you THE RESULTS!
From the published incentive scheme here: https://github.com/regen-network/testnets/tree/master/archive/regen-test-1001
Drum roll please.
Top Twenty (out of 37):
6 POS Bakerz
13 Simply VC
You can find the complete list here: https://docs.google.com/spreadsheets/d/1ozbxnI96bym8ZGGuxYrAkf-4FmprU3CZqP15cS7oBb4/edit#gid=0
Dev and Validator Tools for Regen Network
Dev Update Channel: Dedicated to 100% signal, only important updates for validators in our community.
DVD Channel, Private channel for Developers, Validators and Delegators for Regen Network
Public Channel: water cooler discussion forum for the broader Regen Network Community
Open Science Channel: Chanel hosted by our science team for open source science in service to verification of ecological state with a focus on remote sensing.
Special thanks to all the validators who participated, special thanks to Joe at Chorus for special efforts, for Ethan Frey our lead engineer for great documentation, to the vitwit team for digging this data back out of the burning wreckage of the testnet put param change fail and calculating things meticulously according to our incentivized test net points system.
What Regen Network Development Inc will do better next time:
- Block Explorer working sooner
- Better documentation
- Testnet details on page one of Regen Ledger Github
- Weekly updates on where we are at in the testnet with links back to original documentation.
We’d love to hear from you if you participated and would like to share any feedback for making our next incentivized testnet better. Hit us up in the telegram DVD channel, or send an email to firstname.lastname@example.org.