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.
I am happy to announce the release of confmgr. You may visit the repo, directly install its NPM package or follow me for a gentle introduction. 1. The problem There are several ways to manage various configurations in your NodeJS App. One of them is about using Environment Variables. Invoking your index.js as follow: MY_VAR1=42 node index.js makes MY_VAR1 available to your script with the following code:
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
The surprise You may read more about Brave in my first article about the Brave browser. After recently visiting one of my own blog post to check the spelling, I got the surprise to be welcomed by a pop proposing me to install a mysterious Crypto Wallet extension. If you are in crypto for a while, all alarms bells should be ringing already. This typically looks like a phishing attempt.
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.
At the launch of the Kusama network, there was no way to identify who the owner of a given account was beside making your own research and adding a name to an account in the PolkadotJS UI. New solutions have been tested and the system is evolving. Background Address book Building your network of trust with the Address book looks like this: This would look as follow: Figure 1.
ssh is the defacto standard to access a remote server. It does not offer much of a point and click GUI but get things done with a fair level of security. ssh shows however a major drawback: it is based on TCP. You will likely never notice any issue until you connect to a server over ssh from a train, a plane or from a mobile device, and briefly lose your connection, or if your device switches network such as going from the Wifi to your Cellphone connection and switching back to Wifi.
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.
A glance at the past Back in 2018, I introduced theCyber with this first article. A second article provided more detailled information about the contracts and what needs to be solved in order to enter the small circle of people who made their way in. After the introduction of the GateKeeperTwo detailled in this article, the readers were left with the challenge to try hacking the contract and save one of the 127 spots available.