Hyperledger Burrow, is a permissioned Ethereum smart-contract blockchain node, which is one of the Hyperledger projects, that is hosted by The Linux Foundation.
The main function of the Hyperledger Burrow is to provide a client looking for a modular blockchain, with a permissioned smart contract interpreter. It executes Ethereum EVM smart contract code (usually written in Solidity) on a permissioned virtual machine.
You May Also Read: How to create smart contract with Solidity?
The Hyperledger Burrow was originally contributed by Monax and co-sponsored by Intel. It is known for the high transaction throughput that it provides on a proof-of- stake Tendermint consensus engine, along with the transaction finality it offers.
To break it down to you, Hyperledger Burrow is essentially a blockchain node, that executes smart contract code following the Ethereum specification.
Burrow is made up of three main components, which are the consensus engine, the permissioned Ethereum virtual machine and the rpc gateway. It has been specifically designed for a multi-chain universe with application specific optimization taken into consideration.
Following are some of the main parts of Burrow:
Consensus Engine: With the help of this, transactions are executed and finalised with the Byzantine fault-tolerant Tendermint protocol. The transaction happens smoothly because of the Tendermint protocol, since it provides high transaction throughput over a set of known validators, thereby preventing a fork in the blockchain.
Smart Contract Application: The smart contract application consists of all accounts, the validator set and the name registry. Whenever a transaction calls on the smart contract code in a given account, the account’s code will get executed in a permissioned virtual machine.
You May Also Read: Blockchain Smart Contracts
Permissioned Ethereum Virtual Machine: The virtual machine’s task is to assert whether or not the correct permissions have been granted. It is built to oversee the Ethereum operation code specification mainly. The permissions are given out through secure native functions and they are present in every smart contract code.
Leave a Comment