The engineering team at RND is preparing for a minor software upgrade (v5.1).
This upgrade includes a few fixes, improvements, and migrations related to the ecocredit module as well as an update to the latest patch release of Cosmos SDK (v0.46.11).
Cosmos SDK Update
Regen Ledger v5.0 included an update to the latest version of Cosmos SDK (v0.46.7) using a forked version of Cosmos SDK that adds amino support for the new gov and group modules (a fix that was officially made available in v0.47).
Since the release of Regen Ledger v5.0, several patch releases have been made available. In particular, the v0.46.8 patch release included improvements to the store and therefore a coordinated upgrade is recommended.
At the time of the proposed upgrade, Cosmos SDK will be updated to the latest patch release (v0.46.11) using a forked version with amino support for the gov and group modules.
Credit Batch Metadata
The schema for metadata referenced within a credit batch has been updated. This is part of a larger effort to provide a consistent standard for all credit batches issued through Regen Registry and to clearly distinguish between data that needs to be anchored on chain and data that is specific to our web application.
Updating to the new schema requires updating the metadata field within each credit batch. Credit batches on Regen Ledger are sealed by default and cannot be updated via state transition functions. This means that an on-chain governance process is required to update the metadata of credits that have already been issued.
At the time of the proposed upgrade, the metadata field within each credit batch will be updated to a new IRI referencing the data stored using the updated schema. The state migration for these changes can be viewed here.
Basket Fixes / NCT Basket
In preparation for the launch of the NCT liquidity pool on Osmosis, the N
Adding one update here for the community about the NCT Basket.
One important goal while bringing NCT into the cosmos ecosystem (and the reason for us building a bi-directional bridge between Polygon as opposed to a one-direction bridge first) is to have an open market that allows for price parity between the NCT available on Osmosis and the NCT available on Polygon (via Sushiswap). Technically, this actually becomes much more challenging to hold true with a rolling date criteria for baskets, as assets can enter one pool on a given date, but not be able to be moved into the other pool at a later date if the rolling date criteria window shifts past the assets’ vintage start date.
The Toucan team is currently in the process of evaluating a change to the NCT evaluation criteria that involves a non-rolling date criteria, in part to remedy these concerns. The RND team is staying close to these conversations so we can make sure the Regen Ledger v5.1 implements the correct date criteria filter for NCT assets if and when this changes.
I’m writing this here so that community members aren’t surprised if when looking at any tagged release candidate binaries for v5.1, they might not see the “10 years in the past” rolling date window as Ryan described above.
We’ll post a link to the Toucan’s announcement in this thread as soon as that’s made public so folks can have visibility to the decision.
Credit Batch Metadata: “The state migration for these changes can be viewed here.” --404
With upgrade, will an on-chain governance process still be required to change ecocredit metadata when at an IRI? Or will the data at an IRI location now be editable through the Data module?
Basket Fixes / NCT Basket: “The state migration for these changes can be viewed here.” – migration looks good.
Updated Bridge Events: Where does the actual Toucan-Regen bridge reside on chain? Is it a Solidity SC / Regen module combo?
We currently do not have any objections to the upgrade, looks good! Great work! Thanks
Quick reminder and update. The governance proposal is live and has reached quorum. Please vote if you have not already done so. Also, we have successfully upgraded to v5.1 on redwood testnet with no issues. Thanks all!