Rust

srtool now showing Substrate proposal hashes

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

Cargo Remote: Speed up your Rust builds

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.

Substrate Runtime Toolbox (srtool)

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.