59c43cd047
Fix proposal update handling to update the consensus state with the new diversifier and timestamp. Add checks in the proposal update test to ensure the values provided in the header match. Did manual testing to ensure the test additions fails before updating the code to the correct behaviour. Co-authored-by: Christopher Goes <cwgoes@pluranimity.org> |
||
|---|---|---|
| .. | ||
| 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.
- Capability - Object capability implementation.
- Crisis - Halting the blockchain under certain circumstances (e.g. if an invariant is broken).
- Distribution - Fee distribution, and staking token provision distribution.
- Evidence - Evidence handling for double signing, misbehaviour, etc.
- Governance - On-chain proposals and voting.
- IBC - IBC protocol for transport, authentication adn ordering.
- IBC Transfer - Cross-chain fungible token transfer implementation through IBC.
- Mint - Creation of new units of staking token.
- Params - Globally available parameter store.
- Slashing - Validator punishment mechanisms.
- Staking - Proof-of-Stake layer for public blockchains.
- Upgrade - Software upgrades handling and coordination.
To learn more about the process of building modules, visit the building modules reference documentation.