Image for post
Image for post

Two weeks ago we started the first vote on the fledgling Polkadot network. That vote has just ended and the results are clear.

With a turnout just shy of one third of the tokens, the recent Polkadot redenomination poll was a major result for stakeholder decision-making. This number is all the more impressive considering that both the Web3 Foundation and Parity Technologies abstained from the voting.

The poll itself was to determine the final “meaning” of the DOT token, specifically how many of the lowest denomination of Polkadot’s balances, the Planck, should constitute a single DOT. …


Unlike any other blockchain to date, Polkadot’s launch process is a multi-stage affair, phased over several weeks, where pieces of new functionality are added, piecemeal, until the initial “production version” is hit. I use quotes here because Polkadot is not designed to be a single blockchain, neither in space nor time. Polkadot is an amorphous multi-chain capable of fussless assimilation of new technologies and features over time, much like a website which evolves and iterates as you visit it day after day.

In case you missed the last episode…

Polkadot began life as a heavily controlled “PoA” (Proof of Authority, namely the authority of the Web3 Foundation) permissioned (with many key operations requiring the permission of said foundation) network, not unlike an enterprise blockchain. Over time, we relaxed the “PoA” and allowed community validators to maintain the nodes which run the network. As of now (which is Phase 2 in our launch process), 197 validators from the Polkadot community — backed by well over half of the DOT in circulation — run the Polkadot network. …


It has been a busy week already, with the first vote started on Polkadot to finally determine how many Planck we shall place in a standard DOT. As that continues, a second feature will be enabled on the Polkadot network’s chain candidate: Council elections. If this all goes to plan, then the following upgrade will be to enable all governance functionality and remove the Web3 Foundation’s administrative (“Sudo”) privileges, phases 3 and 4 in our launch plan. …


Image for post
Image for post

A vote has been started that will alter the course of Polkadot and define the final denomination of its native DOT token. It affects all Polkadot stakeholders. If you have claimed your DOT on the mainnet, or you plan to, then you can — and should! — vote.

Two months ago, a vote was conducted on Polkadot’s “wild cousin” network, Kusama. The vote was over a simple, non-binding declaration that the assembled Kusama community be in favour of changing the denomination of the “DOT” token, essentially multiplying all balances across the system by one hundred. …


As you might know, the launch of the Polkadot network is split over several stages, starting with the most centralised, restrictive and permissioned network based around a proof-of-authority (PoA) consensus. This initial stage has been running (as I write this) for 19 days without a problem, hopefully a sign of things to come. …


Image for post
Image for post

Polkadot’s first chain candidate (“CC1”), which may well become the Polkadot mainnet, has been launched. Here’s what you get now and what’s coming up soon.

As I write this, my laptop node has 12 peers. Barely half an hour ago, it had none. Polkadot CC1 is freshly born; beginning its “life” at 17:36:21, Zug time. We’re now at block #400, with Grandpa and Babe chugging along quite happily. So far so good.

Image for post
Image for post
The first block gets laid and the multichain begins its life.

So what is Polkadot CC1; what does it deliver, what doesn’t it deliver (yet) and what can be expected soon?

What it’s not…

First, what Polkadot CC1 is not. Firstly, it’s not Polkadot, at least not yet. CC1 is our first candidate for the Polkadot mainnet. It is our hope that it is eventually selected as the final Polkadot chain, but there’s always a chance that we will launch a second (or even third) chain candidate if we deem it technically necessary. …


Image for post
Image for post

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: n/a
  • 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. …


Image for post
Image for post

A little chaos ensued on the Kusama network, Polkadot’s canary-net. Here’s a quick summary of the cause and solution.

At around midday UK time on Saturday, a referendum ended on an upgrade proposal (ostensibly meant to update the Kusama blockchain to Kusama runtime version 1034). The associated upgrade happened, switching out the core logic of the Kusama blockchain with the new logic of the upgrade. However, due to a naming issue related to a recent change which split apart the Kusama logic from the provisional Polkadot logic, the upgrade inadvertently updated the chain not to the Kusama runtime but to the provisional Polkadot mainnet runtime! Due to a difference in the parameters of the Babe consensus algorithm between the two, the new runtime was incompatible with the Kusama client code. …


Image for post
Image for post
Happy (Kusama) New Year

I started the last year-end round-up with some statistics, and it seems fitting to continue the trend and report some numbers from this year. In total, the Polkadot project, including Substrate, Grandpa, Cumulus and a few bits of support code, has over three hundred thousand lines of code! That’s three times as much as was done last year, and it includes neither our UI nor much of our smart contract codebase. 121 people made these lines of code happen, around half of whom are Parity employees, with the other half being community contributors. The code was added in a little under 3,000 individual contributions, well over double the amount we had at the end of last year. …


Image for post
Image for post

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. …

Gavin Wood

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store