Dot Leap 10

Polkadot becomes decentralized, new Parachain demos, Telegram network-tracker bots, and so many awesome tools!

Thank you for taking the Dot Leap!

We cover Polkadot, Kusama, Substrate, and all related and unrelated Web 3.0 projects!

For the Ethereum side of Web 3.0, please subscribe to Evan's newsletter.

The content in this newsletter is the author’s own opinion and not in any way endorsed by the Web3 Foundation. This is an independent and unaffiliated effort.

Polkadot (v 0.8.10)

🎉🎉🎉🎉 PoS launch!

The network is starting with 20 validators to keep the lowest-backed one reasonably economically involved (no sense in validating if you have only 1 DOT behind your account) and this number will be increased through governance as more nominations come in. Annoucement post here.

The current state of staking is visualized on this dashboard from

A demo of tokens being sent to the Relay Chain from a Parachain and back

A demo of message sending between two parachains


  • If you specify sentry nodes with --sentry-nodes <sentry node multiaddr> and --sentry <validtor node multiaddr> you do not need to duplicate the --reserved-nodes flag

A new runtime was Sudo-ed into Polkadot. This update contains the following new features:

  • Generalized proxies: you can set a proxy type (Any, NonTransfer, Governance, Staking) and each one is allowed to perform some subset of calls on behalf of the primary account. So if you set a staking proxy for your stash account, it could call bondbondExtrasetController, basically the stash account calls, but could not call the controller account calls like validatesetKeynominate.

    For the technically-minded, here’s the mapping of allowed calls per proxy type.

  • Identities pallet has been enabled, allowing anyone to register an on-chain identity for a deposit of around 0.2 DOT. Feeling lost? This guide on setting up an identity will be helpful. Additionally, the first registrar was sudo-ed into Polkadot and you can now have Chevdor/Will verify your identity.

  • Once Governance launches on Polkadot, the Council will have the ability to move people’s DOT claims. This is already happening on Kusama - see Motion 160.

🚨 Something I didn’t know

  • To connect to multimple telemetry servers at once, use the flag multiple times:  --telemetry-url 'wss:// 1' --telemetry-url 'wss:// 1'

  • If person A bids on a parachain slot in an auction for year 1, and person B for that same slot on year 2, person A has their tokens locked for 1 year only, but person B for the full two years. It makes sense, I just never thought about it too much.

Kusama (v 0.8.10)

⚠ Updates

  • The referendum to update the validator count to 350 has been enacted - Kusama is operating at 350 validators.

🏛 Kusama Governance

A more detailed digest of the governance during last week of May is here and the week of June 8 is documented here.

  • Referendum 56 to add a new registrar into Kusama has failed due to some last minute high-convinction nay-sayers! Referendum 58 to add Council Member Kevin Li as a registrar shared its fate.

  • Referendum 59 was hastened into the runtime by the Council and Technical Committee. It was not verified by a tool like srtool, nor was it adequately explained.

    The update was a companion upgrade for Polkadot - in this edge case Polkadot got these features before Kusama - but in my opinion this approach does not cast a good light on Kusama’s governance process. With that in mind, I will be creating a Polkadot Standards Proposal for runtime upgrade submission guidelines - stay tuned for next Dot Leap.

  • Referendum 61 passed, expedited by council and technical committee, modifying deposit values from runtime v2008, making Multi-sigs cheaper to use. Typically, multi-sig accounts need a deposit per pending operation because storing operations on chains costs storage. Once a multi-sig operation clears, the deposit is returned. This upgrade makes these deposits palatable again (used to be 9KSM for 2/3 multisig).

  • Referendum 62 is being voted on to increase the number of validator slots on Kusama to 400.

  • Polkawallet submitted a treasury proposal to further improve their amazing mobile Flutter-based wallet. The proposal has passed.

  • After the successful completion of Milestone 2, the LocalCoinSwap team has submitted a new Treasury Proposal for funding the next one. This has already been approved.

  • On Treasury-pallet Bounty Extension: the community has been working on a specification of the open questions for this extension after the last summary on Polkassembly - here is the current specification [google doc]. Bryan Chen implemented all of the open points and it's ready for initial review before diving into benchmarks and weights.

  • A new Treasury proposal is being prepared by Forgingblock for developing a decentralized payment gateway for Kusama.

  • Council Motion 160 moves a KSM allocation to a new address as requested by the owner. The entity contacted the Web3 Foundation for not being able to claim their KSM allocation due to using a Gnosis Multisig wallet back in 2017 for the crowdsale: the problem was they were unable to sign messages from the Multisig in order to claim the allocation. The council has approved this motion.

🔩 Core Stack (v2.0.0-rc3)

( ͡✧ ͜ʖ ͡✧)

Substrate v.2.0.0-rc3 is out!


  • Introduce stacked filtering (#6273)

  • Allow "anonymous" proxied accounts (#6236)

  • Allow over-weight collective proposals to be closed (#6163)

  • Fix Election when ForceNone V1 (#6166)


  • Make transaction pool prune transactions only of canonical blocks (#6123)

  • Rename all the election operations (#6245)

  • Sentry nodes and validator nodes also imply reserved (#6251)

  • Fix peerset not filtering incoming connections in reserved-only (#6249)

  • Use Subscription Manager from jsonrpc-pubsub (#6208)

  • Add a Substrate networking Grafana dashboard template (#6171)

  • Add subkey inspect-node-key (#6153)

( ͡✧ ͜ʖ ͡✧)

🛠 Tools

👨‍🎓 Education

🤝 Ecosystem

That's it for this week - I hope this was as useful for you to read as it was for me to write! Special thanks to Bill for his Daily Digest!

The Dot Leap is put together by Bruno Škvorc. Got any links for me for the next edition? Find me on Riot at, on Twitter, or via email at