Table of Contents 1. Intro 2. Install 2.1. Pull image 2.2. Using an alias 2.3. Power users 3. Use 4. Proposal field 5. Build the Docker image 1. Intro srtool is a collection of dockerized tools helping with Substrate & Polkadot Runtime development.
It especially helps with building and verifying Wasm Runtime Blobs.
The Docker image is chevdor/srtool. You can find it at https://hub.docker.com/r/chevdor/srtool.
In a previous article, I submitted a motion to the Kusama Council proposing the registration of a new registrar on Kusama: Registrar #1.
Unlike the name suggests, this is not the first registrar on Kusama. It brings a second registrar on the chain as we can see by querying the chain state of the identity module:
1. TLDR If you only want to jump to practical todos ignore the explanations, you may directly go to Certification process.
I introduced srtool in a previous article. While the first implementation filled a gap and allowed for the first time users to verify substrate runtime wasm blobs, there was still work to do to improve the user’s experience.
1. Current verification process Up to now, the verification process looked like:
a runtime dev works on some changes
he builds the new runtime locally, preferably using srtool in order to get the SHA256 of the new wasm blob right away
There is no question that Rust is one of the, if not THE, best language of the decade.
Rust allows us writting safe code while doing most of the safety checks at compile time. That means that we no longer need to bloat the binary that is produced with extra checks to safeguard against developer mistakes such as null and dangling pointers or overflows to mention just a few.
Unlike all other Blockchains, Polkadot (based on Substrate) allows on-chain protocol upgrades without requiring the node operators to do anything but to keep their node up and running.
If you know everything about Substrate Runtime, you may jump to the Installation section.
In order to achieve this, Polkadot stores its runtime executable as a WASM blob in its own storage. If the WASM blob is replaced, the new runtime kicks in and all the nodes start using it, altogether.