* enforce spec ordering * modify clients to pass in specs to verify functions * start fixing tests * Apply suggestions from code review * enforce spec length and proof length match * fix all tests * add argument to constructor: * fixed msg client and tests * appease linter * Apply suggestions from code review Co-authored-by: Federico Kunze <31522760+fedekunze@users.noreply.github.com> * finish fixes from review * add back proof-specific checks * Apply suggestions from code review * more robust proof spec checks * add CHANGELOG entries * do not hardcode proofspecs in 23-commitment * fix client modules * fix tests * appease linter Co-authored-by: Federico Kunze <31522760+fedekunze@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| auth | ||
| bank | ||
| capability | ||
| crisis | ||
| distribution | ||
| evidence | ||
| genaccounts | ||
| genutil | ||
| gov | ||
| ibc | ||
| ibc-transfer | ||
| mint | ||
| params | ||
| simulation | ||
| slashing | ||
| staking | ||
| upgrade | ||
| README.md | ||
List of Modules
Here are some production-grade modules that can be used in Cosmos SDK applications, along with their respective documentation:
- Auth - Authentication of accounts and transactions for Cosmos SDK application.
- Bank - Token transfer functionalities.
- Governance - On-chain proposals and voting.
- Staking - Proof-of-stake layer for public blockchains.
- Slashing - Validator punishment mechanisms.
- Distribution - Fee distribution, and staking token provision distribution.
- Crisis - Halting the blockchain under certain circumstances (e.g. if an invariant is broken).
- Mint - Creation of new units of staking token.
- Params - Globally available parameter store.
- Supply - Total token supply of the chain.
To learn more about the process of building modules, visit the building modules reference documentation.