Kusama CC2

2019-09-26 in  Kusama
Avatar by Gavin Wood
Image

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!

For more information on Kusama and Polkadot, visit kusama.network and polkadot.network.

Join the Kusama Community

Kusama Email Newsletter

Kusama Twitter

Kusama Telegram

Kusama Riot Chat

Join the Polkadot Ambassadors

Kusama & Polkadot Webinars

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.