Release Notes
Cosmos SDK enters a new phase. A phase with a more performant core layer, rewritten from the ground up. A phase where modules can remain unchanged and chains can take advantage of those performances and UX improvements at no cost.
Unburdened By What Has Been
How to upgrade
Already Enthousiast? Great!
Upgrade now by following v0.52.0 UPGRADING.md and afterwards the UPGRADING_v2.md (wip).
The documentation at docs.cosmos.network is being updated to reflect the new core design, and the UPGRADING_v2.md is being crafted.
As always, an example application is available: simapp/v2.
Note
Hesitant? Upgrade to Olympus LTS (v0.52), same core as before, improved, with long term support, and ease into v2 later on.
Disambiguation
v2 refers to all the new core components of the SDK:
- cosmossdk.io/runtime/v2 v2.0.0-beta.1
- cosmossdk.io/server/v2 v2.0.0-beta.1
- cosmossdk.io/server/v2/stf v1.0.0-beta.1
- cosmossdk.io/server/v2/appmanager v1.0.0-beta.1
- cosmossdk.io/server/v2/cometbft v1.0.0-beta.1
- cosmossdk.io/store/v2 v2.0.0-beta.1
Official Cosmos SDK modules in this repository are compatible with v2 and v0.52.0. Refer to the version matrix to understand what it means.
Tip
- The v2 core layer only needs cosmossdk.io/core v1.
- Essentially, the core layer of v0.52 (
baseapp&serverpackages) is being replaced by v2 in a v2 chain. - The default consensus server (
server/v2/cometbft) and core v1 compatible modules are using v0.52.
What next?
- v2 has already 98% feature parity with v0.52.x.
- What's missing? Check out our project board.
- v2 is as good as ready for final release
- IAVL v2 integration is coming in a
store v2.0.0-beta.2(review + benchmarks ongoing) - Documentation is being updated.
- IAVL v2 integration is coming in a
- An audit of the v2 components will happen begin next year (Jan/Feb 2025).
Made with ❤️ by
(in alphabetical order)
- Binary Builders @binary_builders
- Decentrio @decentriolabs
- Vitwit @vitwit_
Special thanks to the Cronos & Strangelove team for already testing v2 🫶