#Gethereum documentation godocs code
A transaction that calls on the smart contract code in a given account will activate the execution of that account’s code in a permissioned virtual machine.
Accounts in Burrow have permissions and either contain smart contract code or correspond to a public-private key pair. The application state consists of all accounts, the validator set and the name registry. Smart Contract Application: Transactions are validated and applied to the application state in the order that the consensus engine has finalised them.The ABCI allows for the consensus engine to remain agnostic from the smart contract application. Application Blockchain Interface (ABCI): The smart contract application interfaces with the consensus engine over the ABCI.The Tendermint protocol provides high transaction throughput over a set of known validators and prevents the blockchain from forking. Consensus Engine: Transactions are ordered and finalised with the Byzantine fault-tolerant Tendermint protocol.
More specifically Burrow consists of the following: Burrow as a node is constructed out of three main components: the consensus engine, the permissioned Ethereum virtual machine and the rpc gateway.
Burrow is built for a multi-chain universe with application specific optimization in mind. Hyperledger Burrow is a permissioned blockchain node that executes smart contract code following the Ethereum specification. Burrow provides transaction finality and high transaction throughput on a proof-of-stake Tendermint consensus engine. It executes Ethereum EVM smart contract code (usually written in Solidity) on a permissioned virtual machine. Hyperledger Burrow is a permissioned Ethereum smart-contract blockchain node.