by Oksana Protsukha
This article is aimed at those already familiar with Tezos protocol. If you are new to the ecosystem, I strongly encourage you to go over the Tezos documentation and familiarize yourself with what Tezos is, its design and features.
Tezos latest self-amended upgrade to Edo 2.0 was successfully executed on Feb 13th, 2021. It introduced several long-awaited and important features to Tezos ecosystem unlocking potential for development of the next level applications on top of the protocol. Some of the key features of Edo 2.0 are:
UPDATE: based on further analysis by Nomadic Labs, it is no longer recommended to vote for Baking Accounts as proposed during phase 42. See below.
We still believe Baking Accounts is a needed Tezos feature for the reasons explained below. We hope that Nomadic Labs will propose a newer version at a later date that addresses the issues they found.
Tezos is a self-amending blockchain protocol governed by elections by the validators (or bakers). The voting process has three phases:
Mina is a constant-size blockchain written in OCaml. We were eager to try itprogramatically before their mainnet release.
We decided to give it a try in a Kubernetes cluster on Amazon EKS. Mina already maintains Helm charts, so deployment was easy.
We normally use Terraform, but we recently got familiar with Pulumi, a newer infrastructure-as-code framework. There are key differences with Terraform: while Terraform requires using its own DSL, Pulumi lets you use a variety of programming languages. That being said, the ecosystem seems to be mostly focused on TypeScript, so this is what we will be using.
Tezos is one of the major proof-of-stake cryptocurrencies. Our company, MIDL.dev, offers infrastructure services for Tezos bakers and builders.
We just released version 2.0 of Tezos-on-GKE, an open-source framework that we built and that we are using internally. We announced version 1.0 here in 2019. Several bakers have deployed our framework and are baking succesfully. In this post, we want to cover a new feature of the framework: baker high availability.
Version 1 of Tezos-on-GKE had two public (sentry) nodes and one baking node. This baker was configured as a Kubernetes Deployment, which means that Kubernetes would ensure that there…
by Oksana Protsukha
Tezos is an on-chain governance blockchain protocol built on liquid proof-of-stake (LPoS) algorithm for consensus. Being PoS protocol, it relies on validators (aka “bakers” in Tezos lingo) to ensure network security. You can find detailed description of proof-of-stake consensus here. What differentiates Tezos from the other PoS protocols is its on-chain governance. Specifically, the blockchain was designed as a self-amending blockchain network and allows activating new protocol versions without a need for a hard fork through on-chain voting process. The latest such upgrade took place on November 12th, 2020, when Tezos blockchain self-upgraded to Delphi protocol.
by Nicolas Ochem
When operating a Polkadot validator, it is critical to maximize your uptime in order to avoid being penalized.
Good practices of a node operator incude disaster recovery: the ability to quickly repair your operations in case of failures. For example, if your hard drive dies, you need to recreate your node from scratch. As time passes and the number of historical blocks grow, it can take a prohibitive amount of time to synchronize your node to the head of the chain. During this time, you may be marked offline and lose your rights as a validator.
by Oksana Protsukha
As part of our preparedness for the upgrade we took a comprehensive look at the impact of the previous upgrade to Carthage had on Tezos network performance and Tezos baking community. Carthage upgrade was executed on Mar 5th, 2020 04:38 am UTC before cycle 208.
We aimed to answer the following questions:
We are introducing polkadot-k8s, an open-source project designed to spin up a secure Polkadot or Kusama validator setup in one shot. Polkadot is a sharded proof-of-stake blockchain, and Kusama is Polkadot’s canary network.
We have been successfully operating a Kusama validator for two months using this model. We also operate a Tezos bakery on Kubernetes.
In this tutorial, we will show how to deploy a validator on Google Kubernetes Engine with just a few utilities on your laptop. Everything is automated and specified in code. There’s no need to compile any Rust code or install any startup script.
We offer a non-custodial staking solution for the leading proof-of-stake cryptocurrencies. Keep your assets under your control in a hardware wallet, and let us handle the rest of the job.
Check us out at https://MIDL.dev
Today’s established blockchains establish consensus by wasting energy and resources, and they suffer from heavy centralization. Proof-of-stake opens a greener and safer chapter in cryptocurrency evolution. Tezos, Polkadot, and Ethereum 2.0 are, in our opinion, the most promising networks.
Proof-of-stake cryptocurrencies have inflation. Token holders must take action for their assets to grow: they must put them at stake on the network.
Unlike proof-of-work blockchains…
With the Tezos-on-GKE project, you can deploy a complete baking infrastructure faster than ever before.
Update: we have now launched our staking-as-a-service company, MIDL.dev. We can help you deploy and manage the infrastructure described in this article. Contact us to become a baker !
There are many tools and instructions out here to bake Tezos. We want to take it a step further. In this article, we present a simple way to spin up baking infrastructure in the cloud.