Building Software for a Modular Future
summary
Roadmap commits to evolving the Cosmos SDK into a true toolkit rather than a single monolith: keep Go, avoid a full rewrite, and ship SDK v1 target H1 2025. Work already ties Cosmos components to CometBFT, IBC and Rollkit migrations (Pocket project experimenting) while pushing experiments where execution is faster than consensus. Plans include abstracting consensus/mempool control, multiple VM and language support (RISC‑V, WASM, ZK integration), swappable commitment structures, and measurable multi‑order performance gains.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:55Monoliths vs modular software
- 4:45Cosmos identity today
- 7:35Rollups and blockchain gap
- 10:03Cosmos SDK roadmap
- 12:12Interchain stack toolkit
- 13:36Preparing for rollups
- 14:18ZK and cross-language modules
- 16:06Commitment structures challenge
- 17:30Cosmos SDK 1.0 goals
- 20:43Cosmos SDK V1 meaning
- 21:03Q&A
related talks
18mThe Cosmos-SDK
20mModular Blockchain Stack: The ENDGAME of Cosmos
18mThe Cosmos Stack: The Road Ahead, and the Opportunity for Builders
12mCØSMOS
32mBuilding on CØSMOS! ALPHA LEAKS!
18mCosmology's New Consumer Chain
11mBeyond the EVM: How the Cosmos SDK Brings New Features to Ethereum
28mCosmos Hub in 2025