docs: Updates for v9.1.1 and re-arranging roadmap docs #2560
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,66 +1,28 @@ | ||
| # The Cosmos Hub Roadmap | ||
|
|
||
| This Cosmos Hub roadmap serves as a reference for the current planned features of upcoming releases. For past releases, please see the following [document](./README.md). | ||
|
There was a problem hiding this comment. @jtremback There was a problem hiding this comment. Now use the living roadmap google doc link that wasn't available before. |
||
|
|
||
| The Cosmos Hub is decentralized and other teams contribute to it as well. The broad categories are as follows: | ||
|
|
||
| ## Replicated Security v1.1: | ||
|
|
||
| These are the many changes we want to make but could not get to before launch. These include: | ||
|
|
||
| - Random code cleanups and protocol simplifications | ||
| - Untrusted consumer chain protocol: Make it so that there is no way a consumer chain can cause inconvenience or harm to the Cosmos Hub, while bringing back automatic slashing as detailed above. | ||
| - Soft opt-in: Make it so that the bottom 10-20% of validators on the Hub do not need to validate every consumer chain, making things easier for the smaller validators. | ||
|
|
||
| ## Interchain Security future: | ||
|
|
||
| Work on the next versions of ICS. | ||
|
|
||
| - Opt-in security: Make it so that every validator can choose which consumer chains they want to validate. This requires fraud proofs or something similar. | ||
| - Mesh security: Participate in the design and adoption of Mesh security. This likely also requires fraud proofs. We’ll be releasing an analysis soon. | ||
|
|
||
|
|
||
| ## Hub governance improvements: | ||
| There are a lot of improvements to the Cosmos SDK governance system that could make deliberation easier and more constructive, and make community pool funding more accountable. | ||
| - Streaming/vesting funding: Allow a funding recipient to vest their funds over time, subject to claw backs if they don’t perform, or set up a streaming payment of future funds, also subject to clawback. | ||
| - Stabilized funding: Automatically exchange Atoms from the community pool for a stable asset, or adjust streaming funding amounts over time in response to an Atom price feed. | ||
| - Multichoice proposals: Allow voters to choose between several acceptable options- this would make it easier to pass proposals that accurately reflect what voters want. | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jtremback moved the release changelog to here.