Kusama Upgrade Bulletin (1032-1037)
Kusama is about to get a new logic core; here’s the details of this and a few earlier ones.
Details
- Runtime version: 1037
- Supported natively by Polkadot v0.7.17
- Polkadot Git commit hash: f570356
- Substrate Git commit hash: 860b79b
- Council motion: #85
Key changes
- Multisig accounts and pseudonymous sub-accounts (#4462): Support for stateful threshold multisig transactions/accounts/wallets and pseudonymous “sub” accounts (accounts controlled by other accounts).
- Indirectly slashed nominators stay nominating (#4553): If a validator is slashed (e.g. for being offline), their nominators were all forced to chill, depriving other, unrelated, validators of nominations. This logic is removed.
- Rebonding (#4374): Unbond operations can now be cancelled before completed and the funds returned to staking operations.
- Structured Tipping (#4480): The treasury now has a threshold-median-timeout tipping scheme allowing a much more agile means of doling out funds. Public “scouts” can find things worth tipping and claim a finders fee (if a majority of the council tips).
Additional changes
- Fix fees in Substrate (#4421): There have been issues regarding transaction fee calculation and in particular how the fee multiplier changed according to transaction volume. This is now fixed.
- Additional events (#4468, #4459): Several additional events for tracking certain changes have been added.
- Twitter field in identity info (#4476): The identity system now includes the Twitter account identity field.
- Multisigner uses compressed ECDSA public key (#4502): Multisigner is corrected to use a hash of the compressed public key. This enables ECDSA (SECP256k1) controlled accounts in Kusama.
- Facilitate cancelation of slashes (#744): To cancel a slash, only one-half of council approvals are required rather than three-quarters.
- Fix transaction fees (#736): Transaction fees were accidentally 1/100th of their correct cost. This fixes it.
Timeline (1037)
- Submitted as a council proposal at: ~#562,400
- Accepted as a council proposal at: n/a
- Preimage noted at: ~#567,500
- Referendum end block: #569,326
- Activation block: #569,326
From the blog
JAM Session: Gavin Wood Reveals Bold Vision for Polkadot's Next Revolution
Yesterday at Token 2049 Dubai, Gavin Wood announced a bold vision for the next generation of Polkadot technology. In line with the other groundbreaking firsts that Polkadot has brought to the market, this new vision is set to revolutionize the future of Web3. It will provide the speed, scale, full decentralization, and ease of use needed to drive forward deep innovation across not just Web3, but the entire tech landscape. At the heart of this vision is JAM, a new version of the Polkadot chain t
The landscape of trustless bridges on Polkadot
With research and writing from Oliver Brett, Adrian Catangiu, and Aidan Musnitzky, this article explores the rich environment of bridge building, both within Polkadot and to external ecosystems. Any Web3 protocol with true aspirations of interoperability needs to consider the development and deployment of bridges to external networks, and in this sense Polkadot is no different. Blockchain bridges are, in essence, mechanisms for two sovereign chains with different technological foundations to o
Unleashing the Potential of AI with Polkadot: the Blockchain Powered Revolution
Blockchain technology has opened up a world of possibilities, and nowhere is this more evident than in the emerging field of artificial intelligence (AI). The Polkadot network is at the forefront of this revolution, serving as a powerful platform for innovative AI projects that are pushing the boundaries of what's possible. In this blog, we'll dive into some of the most exciting AI initiatives within the Polkadot ecosystem, exploring how these projects are leveraging Polkadot's advanced capabili