5bd93bfe7b
* -added consensus version tracking to x/upgrade * -added interface to module manager -added e2e test for migrations using consensus version store in x/upgrade -cleaned up x/upgrade Keeper -handler in apply upgrade now handles errors and setting consensus versions -cleaned up migration map keys -removed init chainer method -simapp now implements GetConsensusVersions to assist with testing * Changed MigrationMap identifier to VersionMap removed module_test * updated docs * forgot this * added line to changelog for this PR * Change set consensus version function to match adr 041 spec * add documentation * remove newline from changelog unnecessary newline removed * updated example in simapp for RunMigrations, SetCurrentConsensusVersions now returns an error * switch TestMigrations to use Require instead of t.Fatal * Update CHANGELOG.md Co-authored-by: Aaron Craelius <aaron@regen.network> * docs for SetVersionManager * -init genesis method added -removed panics/fails from setting consensus versions * update identifiers to be more go-like * update docs and UpgradeHandler fnc sig * Upgrade Keeper now takes a VersionMap instead of a VersionManager interface * upgrade keeper transition to Version Map * cleanup, added versionmap return to RunMigrations * quick fix * Update docs/architecture/adr-041-in-place-store-migrations.md Co-authored-by: Amaury <1293565+amaurym@users.noreply.github.com> * remove support for versionmap field on upgrade keeper * cleanup * rename get/set version map keeper functions * update adr doc to match name changes * remove redudant line Co-authored-by: technicallyty <48813565+tytech3@users.noreply.github.com> Co-authored-by: Aaron Craelius <aaron@regen.network> Co-authored-by: Amaury <1293565+amaurym@users.noreply.github.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| .vuepress | ||
| architecture | ||
| basics | ||
| building-modules | ||
| cn | ||
| core | ||
| ibc | ||
| intro | ||
| kr | ||
| migrations | ||
| ru | ||
| run-node | ||
| spec | ||
| using-the-sdk | ||
| cosmos-sdk-image.jpg | ||
| DOCS_README.md | ||
| package-lock.json | ||
| package.json | ||
| post.sh | ||
| pre.sh | ||
| protodoc-markdown.tmpl | ||
| README.md | ||
| versions | ||
Cosmos SDK Documentation
Get Started
- SDK Intro: High-level overview of the Cosmos SDK.
- Quick Start Guide: Scaffold a standard Cosmos SDK app and run a node.
- SDK Application Tutorial: A tutorial that showcases how to build an SDK-based blockchain from scratch and explains the basic principles of the SDK in the process.
Reference
- Basics: Documentation on the basic concepts of the Cosmos SDK, like the standard anatomy of an application, the transaction lifecycle and accounts management.
- Core: Documentation on the core concepts of the Cosmos SDK, like
baseapp, thestoreor theserver. - Building Modules: Important concepts for module developers like
messages,keepers,handlers andqueriers. - IBC: Documentation for the IBC protocol integration and concepts.
- Running a Node, API, CLI: Documentation on how to run a node, and how to interact with it using the CLI and the API.
- Migrations: Migration guides for updating to Stargate.
Other Resources
- Module Directory: Module implementations and their respective documentation.
- Specifications: Specifications of modules and other parts of the Cosmos SDK.
- SDK API Reference: Godocs of the Cosmos SDK.
- REST API spec: List of endpoints to interact with a
gaiafull-node through REST.
Cosmos Hub
The Cosmos Hub (gaia) docs have moved here.
Languages
The Cosmos-SDK is currently written in Golang, though the framework could be implemented similarly in other languages. Contact us for information about funding an implementation in another language.
Contribute
See this file for details of the build process and considerations when making changes.