Kusama Upgrade Bulletin (1030)
Kusama is about to get a new logic core; here’s the details.
Details
- Runtime version: 1030
- Supported natively by Polkadot v0.7.9
- Polkadot Git commit hash: f23ce3e
- Substrate Git commit hash: c6fc2e6
Key changes
- Revamp reaping rules (#4371): When reaping a proposal preimage, it is now possible for the original submitter of the preimage to reap (i.e. to remove the preimage and have their deposit returned) before the public at large get a chance to claim the deposit. This makes it much less likely that a preimage submitter will lose their deposit. To prevent the possibility of a yank-attack, where the preimage owner removes the preimage and reclaims their deposit just before it is to be used by the chain (and therefore effectively cancels the upgrade), it is no longer permitted to reap preimages that are about to be claimed. This required altering the
DispatchQueueimplementation. - Allow referendums to begin out of order (#4345): It was not possible to place a referendum to end before any pre-existing referendum, thereby severely reducing the utility of the fast-track rescue feature. There was no particular reason for this requirement, so it has been lifted.
- Including runners-up in check for defunct Phragmen voter (#4349): A simple bug fix; runners-up in the council were identified as being defunct, when they should have been considered still active.
- More comprehensive identity system (#4326): The Nicks identity system is rather problematic. This introduces a standardised and federated system for identity attestations, allowing for anyone to submit their identity information and pay one or more registrars to verify and attest to its legitimacy. There is no limit to the number of registrars that the system supports but they must be approved by council mandate. Registrars may specify which identity fields that they bother to verify. Each attestation they make can take one of several values according to the degree to which the registrar believes the information is accurate. Identities may be removed or withdrawn for a refund of any deposits placed. It is written to be extensible and allow for addition of new identity fields as time goes on.
Timeline
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