This is a software upgrade proposal for the upgrade to Regen Ledger v4.1. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v4.0 at approximately XX:XX UTC on September XX and starting the application binary for Regen Ledger v4.1.
Recently the core developers of Regen Ledger were made aware of two bugs in Regen Ledger v4.0 that we deemed important to fix before the previously anticipated Regen Ledger v5.0. Both of these bugs required consensus-breaking changes to Regen Ledger. The developers have prepared a single upgrade (Regen Ledger v4.1) which contains both fixes, to ease the burdon on validators and not have to do two separate consecutive upgrades.
As of Regen Ledger v4.0, Tendermint has not been receiving validator updates from the application state. This was initially reported by a member of our validator community. What resulted is that the actual block-signing validator set (managed by Tendermint) essentially froze as of the upgrade to Regen Ledger v4.0.
Validators who had been jailed or otherwise unbonded were not actually removed from the validator set managed by Tendermint. Any new validators who were supposed to be promoted to the active validator set were not actually admitted into the block-producing validator set managed by Tendermint.
Upon being notified of the issue, the dev team analyzed the situation and determined that there was no risk of consensus failure and that it was safe to proceed with a software upgrade proposal (1-week voting time), as opposed to requiring an emergency rolling-upgrade.
A fix for this issue has been implemented in Regen v4.1. It will, at the scheduled upgrade height, update Tendermint's validator set to the correct active set (as managed by the application). In other words, all validators who should have been jailed since the upgrade to v4.0 will be immediately removed from Tendermint's validator set, and any new validators waiting to be admitted into the active set will be immediately added to tendermint's block-producing validator set.
No user funds were lost in this process. However, it is important to point out that validators who were supposed to be jailed were not actually jailed, but remained in Tendermint's active set and continued to receive rewards (delegators who staked with these validators also still received rewards) as these validator continued to produce blocks. Slashing still occurred exactly as expected and these validators were still slashed for their behavior. We invite the validator community to independently evaluate whether it is necessary to redistribute rewards that may have been affected by this bug. If necessary, the core devs will plan a second upgrade that redistributes rewards accordingly after this upgrade.
Recently a bug was identified in how regen ledger serializes ecocredit transactions for Amino signing. When signing ecocredit transactions with a hardware wallet regen ledger mis-implements amino serialization, deviating from the behavior expected by javascript clients (namely Keplr wallet and CosmJS). As a result, hardware wallets could not be used for signing transactions initiated from a browser based application. (note: hardware wallet signing using the regen CLI was unaffected, and worked as expected).
A fix for this issue has been implemented in v4.1. It fixes amino serialization such that Keplr and CosmJS can now be used to generate, sign, and broadcast transactions involving ecocredit functionality on Regen Network.