Releases: regen-network/regen-ledger
v1.1.0-alpha1
v1.1.0-alpha0
This alpha pre-release updates regen-ledger to the Cosmos SDK v0.43. It is not meant to be used in production, but in intermediary testnets before the next software upgrade.
v1.0.0
This release is the version of regen-ledger that will be used for the mainnet launch of Regen Network's blockchain (chain-id: regen-1
).
It enables configurable builds for regen ledger (by building with an EXPERIMENTAL=true/false
build flag). With this new configuration, we've made the following delineation.
- Stable build (EXPERIMENTAL=false) is intended for Regen Network's mainnet, and any testing networks aiming to replicate the mainnet configuration.
- Includes all standard modules from the Cosmos SDK (bank/staking/gov/etc.), as well as IBC
- Experimental builds, are intended to have more experimental features which have not gone through a full internal audit and are intended for devnets and 3rd party developers who want to work on integrating with future features of regen ledger.
- In addition to stable build modules, experimental build includes:
- Regen specific modules (x/ecocredit, x/data)
- CosmWasm
- x/group
- In addition to stable build modules, experimental build includes:
It is not guaranteed that APIs of features in the experimental build will remain consistent until they are migrated to the stable configuration.
Added
Changed
- upgrade to Cosmos SDK v0.42.4
- update group tx commands
- remove colon from regen addresses
v1.0.0-rc0
First Release Candidate for the v1.0.0
version of Regen Ledger. The v1.0.0
marks the target release for Mainnet Launch. Subsequent RC's will be issued as necessary for bug fixes and documentation, but the featureset is intended to remain unchanged.
v0.6.2
v0.6.1
v0.6.0
v0.6.0-alpha6
Fix version in Makefile (#239)
v0.6.0-alpha5
Add logs to rootCmd (#238)
v0.6.0-alpha4
Update to SDK v0.40.0 (#219) * Update to SDK v0.40.0 * Fix test * Update app/app.go Co-authored-by: Robert Zaremba <[email protected]> Co-authored-by: Robert Zaremba <[email protected]>