Substrate Tendermint

Welcome to the code library for the Substrate-based Tendermint Consensus!

Introduction

This repository implements the Tendermint Consensus algorithm for the substrate blockchain framework.

This repository includes:

• The main implementation of Tendermint Consensus in tendermint/consensus and tendermint/finality-tendermint/.
• And an Intergration example of node with Tendermint Consensus.

You can find more detailed descriptions in their individual READMEs.

Build

Setting Up the Stable Toolchain

rustup default stable
rustup update

Adding the Nightly Toolchain and wasm Target

rustup update nightly
rustup target add wasm32-unknown-unknown --toolchain nightly

Compile the node template

cargo build --release

Single-Node Development Chain

./target/release/node-template --dev

Project Structure

This project is divided into two parts first is node and other is tendermint. Node includes runtime and node in it and Tendermint include consensus specific logic.

Node

A blockchain node is an application that allows users to participate in a blockchain network. Substrate-based blockchain nodes expose a number of capabilities:

• Networking: Substrate nodes use the libp2p networking stack to allow the nodes in the network to communicate with one another.
• Consensus: Blockchains must have a way to come to consensus on the state of the network. Substrate makes it possible to supply custom consensus engines and also ships with several consensus mechanisms that have been built on top of Web3 Foundation research.
• RPC Server: A remote procedure call (RPC) server is used to interact with Substrate nodes.

There are several files in the node directory. Take special note of the following:

• chain_spec.rs: A chain specification is a source code file that defines a Substrate chain's initial (genesis) state. Chain specifications are useful for development and testing, and critical when architecting the launch of a production chain. Take note of the development_config and testnet_genesis functions,. These functions are used to define the genesis state for the local development chain configuration. These functions identify some well-known accounts and use them to configure the blockchain's initial state.
• service.rs: This file defines the node implementation. Take note of the libraries that this file imports and the names of the functions it invokes. In particular, there are references to consensus-related topics, such as the block finalization and forks and other consensus mechanisms such as Aura for block authoring and Tendermint for finality.

Runtime

In Substrate, the concepts of "runtime" and "state transition function" are used interchangeably. These terms describe the fundamental mechanism of the blockchain that validates blocks and implements the state modifications they prescribe.

This project uses FRAME to construct a blockchain runtime. Also tendermint pallet is added into the runtime.

Review the FRAME runtime implementation included in this node and note the following:

• This file configures several pallets to include in the runtime. Each pallet configuration is defined by a code block that begins with impl $PALLET_NAME::Config for Runtime.
• The pallets are composed into a single runtime by way of the construct_runtime! macro, which is part of the core FRAME pallet library.

Pallets

The runtime in this project is constructed using many FRAME pallets that ship with the Substrate repository and a tendermint pallet that is defined in the pallets directory.

A FRAME pallet is comprised of a number of blockchain primitives, including:

• Storage: FRAME defines a rich set of powerful storage abstractions that makes it easy to use Substrate's efficient key-value database to manage the evolving state of a blockchain.
• Dispatchables: FRAME pallets define special types of functions that can be invoked (dispatched) from outside of the runtime in order to update its state.
• Events: Substrate uses events to notify users of significant state changes.
• Errors: When a dispatchable fails, it returns an error.

Each pallet has its own Config trait which serves as a configuration interface to generically define the types and parameters it depends on.

References

• Substrate-hotstuff
• Substrate-MCA
• Polkadot-SDK