Clone or download
Latest commit d8fbfb7 Oct 19, 2018
Permalink
Failed to load latest commit information.
.circleci Don't use node-specific KeyClient during GovTx execution. Fix dev Aug 23, 2018
.github Rename to Burrow Apr 4, 2017
acm Fixup for tendermint 0.24 Sep 21, 2018
bcm Fixup for tendermint 0.24 Sep 21, 2018
binary Add test for revert, return nested errors, and convert non-revert errors Aug 7, 2018
cmd/burrow Client constructor Sep 25, 2018
config Expose peers filter provider as an API to allow other project to defi… Oct 1, 2018
consensus [consensus] Expose Tendermint config CreateEmptyBlocks and CreateEmpt… Oct 5, 2018
core Merge branch 'develop' into EXPOSE_TRANSACTOR Oct 5, 2018
crypto Update against breaking Tendermint changes Aug 21, 2018
deploy Save binary at address when deploying bin file Oct 17, 2018
deployment Rationalise GRPC, protobuf, integration testing Jul 18, 2018
docs Merge branch 'develop' into docs-initiate-burrow-improvment-process Oct 10, 2018
event Fix resubscribe test by adding a buffer so that publish doesn't get Aug 20, 2018
execution Save binary at address when deploying bin file Oct 17, 2018
forensics Update dump to use amino codec Aug 23, 2018
genesis Handle sequence number checking and incrementation generically for all Jul 28, 2018
governance GovTx based validator set changes implemented and tested Jul 23, 2018
integration abi: Ensure event signature ID is available as EventID member Oct 5, 2018
keys Don't use node-specific KeyClient during GovTx execution. Fix dev Aug 23, 2018
logging Refactor state into refs and tree. Sep 14, 2018
permission Reenable PublicKey initialisation and allow public keys to be unset Jul 27, 2018
process Remove go-wire from codebase completely Jun 13, 2018
project Update changelog Sep 21, 2018
protobuf Make simulated call use same path as call_context Aug 16, 2018
rpc nil pointer exception when name does not exist Sep 17, 2018
scripts solgo: compiles solidity to go with abi Aug 30, 2018
storage Removed debug statement Sep 19, 2018
sync Release lock earlier in BroadcastTxSync and support mempool signing in Jul 25, 2018
tests Fix issue with burrow killing Oct 16, 2018
txs Merge branch 'develop' into state Sep 19, 2018
util Make snatives solidity use _camelcase parameters Aug 16, 2018
vendor Vendor tendermint 0.24 Sep 20, 2018
.dockerignore Sort out docker and release builds Aug 20, 2018
.gitignore Refactor rpc/tm to rpcinfo changing various names. Aug 15, 2018
.goreleaser.yml Use hyperledger/burrow and release binaries Aug 16, 2018
CHANGELOG.md Update changelog Sep 21, 2018
Dockerfile Incorporate Casey's dockerfile changes Aug 21, 2018
Gopkg.lock Vendor tendermint 0.24 Sep 20, 2018
Gopkg.toml Vendor tendermint 0.24 Sep 20, 2018
LICENSE.md strings.ToUpper(the-license-filename-prefix) Mar 4, 2017
Makefile solgo: compiles solidity to go with abi Aug 30, 2018
NOTES.md Update changelog Sep 21, 2018
README.md [docs] Introduce the Burrow Improvment Proposals (BIPs) Oct 9, 2018

README.md

Hyperledger Burrow

version GoDoc license LoC

Branch Linux
Master Circle CI
Develop Circle CI (develop)

Hyperledger Burrow is a permissioned Ethereum smart-contract blockchain node. It executes Ethereum EVM smart contract code (usually written in Solidity) on a permissioned virtual machine. Burrow provides transaction finality and high transaction throughput on a proof-of-stake Tendermint consensus engine.

burrow logo

What is Burrow

Hyperledger Burrow is a permissioned blockchain node that executes smart contract code following the Ethereum specification. Burrow is built for a multi-chain universe with application specific optimization in mind. Burrow as a node is constructed out of three main components: the consensus engine, the permissioned Ethereum virtual machine and the rpc gateway. More specifically Burrow consists of the following:

  • Consensus Engine: Transactions are ordered and finalised with the Byzantine fault-tolerant Tendermint protocol. The Tendermint protocol provides high transaction throughput over a set of known validators and prevents the blockchain from forking.
  • Application Blockchain Interface (ABCI): The smart contract application interfaces with the consensus engine over the ABCI. The ABCI allows for the consensus engine to remain agnostic from the smart contract application.
  • Smart Contract Application: Transactions are validated and applied to the application state in the order that the consensus engine has finalised them. The application state consists of all accounts, the validator set and the name registry. Accounts in Burrow have permissions and either contain smart contract code or correspond to a public-private key pair. 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.
  • Permissioned Ethereum Virtual Machine: This virtual machine is built to observe the Ethereum operation code specification and additionally asserts the correct permissions have been granted. Permissioning is enforced through secure native functions and underlies all smart contract code. An arbitrary but finite amount of gas is handed out for every execution to ensure a finite execution duration - “You don’t need money to play, when you have permission to play”.
  • Application Binary Interface (ABI): Transactions need to be formulated in a binary format that can be processed by the blockchain node. Current tooling provides functionality to compile, deploy and link solidity smart contracts and formulate transactions to call smart contracts on the chain.
  • API Gateway: Burrow exposes REST and JSON-RPC endpoints to interact with the blockchain network and the application state through broadcasting transactions, or querying the current state of the application. Websockets allow subscribing to events, which is particularly valuable as the consensus engine and smart contract application can give unambiguously finalised results to transactions within one blocktime of about one second.

Project Roadmap

Project information generally updated on a quarterly basis can be found on the Hyperledger Burrow Wiki.

Minimum requirements

Requirement Notes
Go version Go1.10 or higher

Installation

See the install instructions.

Quick Start

  1. Single full node - start your first chain
  2. Send transactions - how to communicate with your Burrow chain
  3. Deploy contracts - interact with the Ethereum Virtual Machine
  4. Multiple validators - advanced consensus setup
  5. Seed nodes - add new node dynamically
  6. Kubernetes - bootstraps a burrow network on a Kubernetes cluster

Project documentation

Burrow getting started documentation is available in the docs directory and in GoDocs.

Contribute

We welcome any and all contributions. Read the contributing file for more information on making your first Pull Request to Burrow!

You can find us on:

Future work

For some (slightly outdated) ideas on future work, see the proposals document.

License

Apache 2.0