With IPFS, you can share files without the need for a centralized product such as Dropbox, Google Drive and Co. That means that you need no account, you have no size or bandwidth limits…
It makes sharing files convenient and very secure. Indeed users cannot modify a file after submitting it. This is due to the fact that IPFS references content using hashes of the content itself and not urls.
Docker is a powerful virtualization tool. While this is not the only virtualization solution available today, it remains one of the simplest to use. Let’s see if and how it plays a critical role in decentralized systems.
Figure 1. Polkadot Runtime Not using Docker Before going any further, it is probably worth mentioning that many people are using Docker to run nodes and validator nodes. The option is totally valid and (I may argue) even better.
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.
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
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.
chevdor/polkadot is a Docker image allowing user to run a Polkadot node without having to build it themselves or build Polkadot without any Rust environment installed locally on their machine.
You can read the full article here.
This artcile is about using the new Polkadot Docker image to get started with PoC-2.
Note Read this article in German on Base58.de. Exciting times The Polkadot PoC testnet has been up and running for a while, but for newcomers who want to jump in the level of technical detail may seem a little daunting. Don’t let that stop you!