Hey folks,
As many of you know, during the Cosmos SDK 0.47 upgrade, @anilcse and the Vitwit helped us successfully complete the migration by standing up a temporary upgrade chain called regen-upgrade, which replaced regen-redwood. That chain has served its purpose well, but Vitwit would now like to shut it down in place of us spinning up a new, longer-term testnet.
The RND PBC is happy to take initiative to spin up a new chain, but we need support on a few things:
-
Validators: Ideally, we’d like 3–5 validators running nodes to keep the testnet resilient. We can get started with fewer if necessary, but having a strong validator set would be great.
-
Name: Our last testnet was named
regen-redwood. Curious if folks want to keep this name, or if we as the community want to explore a new name. -
Coordination: We’ll need to agree on parameters, initial setup, and testnet governance. Generally, I think we keep the existing params used on
regen-upgradeand adjust governance requirements depending on the number of validators running nodes. But if there’s anything we want to adjust at this time, like adding new allowed denoms to the ecocredit module, would love to hear suggestions!
Looking forward, I would also propose this chain serves as the staging grounds to deploy the upcoming Cosmos SDK 0.53 upgrade such that we don’t have to replicate this process again in a few months time.
If you’re interested in running a validator or contributing to this effort, please comment below. Let’s make sure the Regen ecosystem continues to have a strong testing and experimentation ground moving forward.
– S4mmyb