Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add roadmap items #15110

Merged
merged 7 commits into from
Feb 22, 2023
Merged
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
103 changes: 97 additions & 6 deletions ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Welcome to the Cosmos SDK's team roadmap.

* [Produce a spec for the new store design](https://github.com/cosmos/cosmos-sdk/issues/12986)
* Research a new design for store. This could entail writing some POC's in order to identify design patterns
* Store as its own go module
tac0turtle marked this conversation as resolved.
Show resolved Hide resolved
* Store as its own go module **(Done)**
* Store module should be its own go.mod without a dependency on the Cosmos SDK
* Begin implementation of store v2
tac0turtle marked this conversation as resolved.
Show resolved Hide resolved
* Identify the migration path from store v1 -> store v2
Expand All @@ -23,32 +23,34 @@ Welcome to the Cosmos SDK's team roadmap.

### Client UX

* Release v1 of query support (auto-cli)
* Release v1 of query support (auto-cli) **(Done)**
* A version of query support has been merged, documentation is missing
* Dynamic metadata support
* Dynamic support allows the Cosmos SDK to release a cmd line tool that could work with any chain.
* Add metadata support to latest version of Cosmos SDK and, if possible, backport to older versions
* Multi-chain command
* Multi-chain command **(Done)**
* Release a cmd line tool that can be pointed a grpc endpoint which then can produce cmd lines to interact with the chain
* Auto-cli tx support
* Tx support for auto-cli/hubl
* This would fully remove the need for application developers to write cli commands for their modules
* Consensus Key Rotation


### Dev UX

* [Release collections v1](https://github.com/cosmos/cosmos-sdk/issues/14300)
* Collections is a new abstraction layer similar to the ORM. In the ADR phase it received support from many in the ecosystem.
* V1 release should allow modules to be migrated to collections.
* [Release ORM v1](https://github.com/cosmos/cosmos-sdk/issues/11088)
* Migrate 3 modules to use collections api
* Migrating 3 modules to use collections would help in show users how to migrate users
* [Sign mode textual](https://github.com/cosmos/cosmos-sdk/issues/11970) (75%)
* [Sign mode textual](https://github.com/cosmos/cosmos-sdk/issues/11970)
* Sign mode textual has been under construction for 2 quarters now, this quarter the goal is to move towards v1 and potentially line up a audit before final release.
* Core API
* [Merge ADR for Core API](https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-063-core-module-api.md)
* [Merge ADR for Core API](https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-063-core-module-api.md) **(Done)**
* Migrate three modules to use core api
* Module Dependency
* Give three modules their own go.mods
* Give three modules their own go.mods **(Done)**
* Cleanup dependency graph (dependent on integration testing framework)
* [Metamask signing directly into the sdk](https://github.com/cosmos/cosmos-sdk/discussions/13892)
* [ADR-033 (internal message routing)](https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-033-protobuf-inter-module-comm.md)
Expand Down Expand Up @@ -99,6 +101,95 @@ Issue: https://github.com/cosmos/cosmos-sdk/issues/12272

Issue: https://github.com/cosmos/iavl/issues/548

## Q2

### Storage

* Completion of Storage v2
* Goal is to complete the rewrite storage
* Begin testing the rewrite on mainnets if possible
* External Audit
* Optimistic Execution spec is merged and implementation has begun
* Goal is to have the spec merged and implementation started.
* Store Design should enable parallel execution of transactions.
* Goal is to enable it but it may still require some work to complete it

### Client UX

* Add signing support to hubl
* Signing support is added to hubl
* Potentially integrating keystone (coordinate with Zondax)

### Dev UX

* Toolkit/SDK ADR.
* Come to consensus on how to make the sdk composable
* Adopt core api fully in modules
* Goal is to remove the Cosmos SDK and Comet as a dependency from all modules
* Release v1 of modules that have their dependency graph cleaned up

### ABCI 2.0

**Blocked**:

> once cometBFT has a release candidate of ABCI 2.0 (cmt 0.38)

* Integrate ABCI 2.0

### Modules

* Governance
* Make gov and groups composable with each other, not duplicate
* Staking
* Research a new staking design
* Begin Implementation
* Auth/Accounts v2
* Spec is merged
* Implementation is completed
* External Audit

### Research

* Feemarket Abstractions
* Spec on how to abstract fee markets to allow applications to write complex fee markets

## Q3

### Storage

* Audit & release of storage refactor
* Identify further optimizations for storage
* Goal is to identify the next bottlenecks in storage or the state machine

### Dev UX

* Complete Toolkit/SDK implementation refactor
* Goal is to release the new version of the sdk allowing for further composability
* Implement fee market abstractions
* Goal is to release an alpha version of fee market abstractions

### Modules

* Staking
* Complete staking redesign
* External Audit


### Research

* Nonce Lanes
* Goal is to produce a spec and/or viability of using lanes for nonces instead of a single sequence number.
* Merklization
* Research different trees and commitment structures

## Q4

### Research

* Stateless clients
* research how stateless clients could evolve in cosmos




This document will be updated at the end of the quarter on what was achieved and what was not. Shortly before the quarter concludes a new section will be added for the next quarter. We are working on updating the complete one year roadmap and will be posting it here as well.