Kusama Upgrade Bulletin (1031)

2019-12-20 in  Upgrade Bulletin, Kusama
Avatar by Gavin Wood
Image

Kusama is about to get a new logic core; here’s the details.

Details

  • Runtime version: 1031
  • Supported natively by Polkadot v0.7.10
  • Polkadot Git commit hash: f76665b
  • Substrate Git commit hash: ab4aca3

Key changes

  • Increase the minimum treasury bond (#701): There have been several small, anonymous and effectively garbage proposals submitted to the treasury. The minimum deposit (which is slashable if the proposal is not accepted) has therefore been raised from 1 KSM to 20 KSM in an effort to reduce this.
  • Remove incorrect assumption that runners-up were sorted by account (#4429): A bug fix to the council elections module that ensures runners-up can voluntarily remove themselves in all circumstances.
  • Update Balances Pallet events to help block explorers (#4389): This is designed to help ensure that the total balance of an account will not change except with an event. It avoids burning balances early, instead moving dust balances between free and reserved to ensure that the total balances adds up. When a dust balance is burned in the reaping of an account, then an event is emitted.
  • Use decl_error in various modules (various): Errors were generally passed back as fixed strings; this passes them as proper error codes, allowing developers and users to understand better what went wrong if/when a transaction fails.
  • Remove proposal when it is refused (#4399): A refused council proposal was not removed when rejected, which meant it could never be resubmitted as a proposal. This fixes it.
  • Identity module enhancements (#4401): Two enhancements to the identity module. One allows the registrars to change their associated account IDs. Secondly, registered sub-accounts are now stored in state under their own address, thereby allowing their efficient querying without need for a large index that would be impractical for the UI and light clients.

Timeline

  • Submitted as a council proposal at: #292,427
  • Accepted as a council proposal at: #292,751
  • Preimage noted at: #294,167
  • Referendum end block: #295,787
  • Activation block: #295,787
arrow_upward
Related articles
Polkadot
Writing History: The First Teams Submit Their Proposal to the Polkadot Treasury

To make sure the teams building on Polkadot have all the support they need, it is paramount that they understand the funding alternatives available. One good funding option is the Polkadot Treasury, which is already supporting a wide range of projects....

Kusama
Swisscom Blockchain to develop Kubernetes Operator for Kusama and Polkadot

Swisscom Blockchain AG has received a Wave 5 grant from Web3 Foundation to develop a Kubernetes Operator for sentry nodes and validators for both Kusama and Polkadot....

Kusama
GRANDPA Equivocation and sysinfo Process Collection Results In Slashing on Kusama Network: a Post-Mortem.

Multiple bugs in code resulted in nodes dropping out from Kusama network and losing the database that stores which blocks they validated. Consequently, the same nodes double-signed those blocks on restart. The slashes caused by this issue have been reverted via Kusama Council motions....

Subscribe to the newsletter to hear about updates and events.
mail_outline
* To see how we use your information, please see our privacy policy.