The next chapter in the Kusama series.
Three weeks ago, we released Kusama Chain Candidate 1 (CC1). After several key fixes to Polkadot, including the Babe consensus layer, we’re pleased to release the next chapter in Kusama: CC2. Though CC2 is technically a fresh chain and will therefore require all Kusama Node operators to upgrade, the transaction history of Kusama CC1 will be injected into Kusama CC2, making CC2 a not-quite hard fork of CC1. Call it a hard spoon, if you like.
What this means for Kusama users is that nothing has changed. Anything you’ve done on Kusama so far will persist into Kusama CC2. If you have a user account and claimed Kusama or even staked/nominated with it, then it will be in exactly the same state when you come back to it in Kusama CC2.
For those operating Kusama nodes, it means you should upgrade, at your earliest convenience, to the newly released Polkadot v0.6.0, which has inbuilt support for Kusama CC2 including its fresh Babe consensus.
We will continue to monitor the network and once the validator set has grown sufficiently large and we are confident that the underlying consensus algorithms are reasonably stable, then we will initiate the upgrade from PoA to PoS. We’ll keep you posted on any upcoming changes!
Join the Kusama Community
From the blog
Elevating Polkadot's Performance and Scale with Asynchronous Backing
Asynchronous backing is the latest step in the roadmap towards natively scaling Polkadot’s performance and flexibility for Web3 use cases across every industry.