You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 13, 2022. It is now read-only.
Hyperledger Burrow has been moved to End of Life status by the original project maintainers. Although Hyperledger Burrow is not currently being developed or maintained, the code is still available under an open source license so you would be welcome to reactivate this project. If you are interested in continuing development of this code, please consider submitting a PR at https://github.com/hyperledger/hyperledger-hip and sending and email to tsc@lists.hyperledger.org. See more details about project proposals at: https://hyperledger.github.io/hyperledger-hip/
If you wish to contribute, please reach out to the TSC mailing list
⚠️⚠️⚠️
Hyperledger Burrow is a permissioned Ethereum smart-contract blockchain node. It executes Ethereum EVM and WASM 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.
What is Burrow
Burrow was a fully fledged blockchain node and smart contract execution engine -- a distributed database that executes code. Burrow runs Ethereum Virtual Machine (EVM) and Web Assembly (WASM) smart contracts. Burrow networks are synchronised using the Tendermint consensus algorithm.
Highlights include:
Tamper-resistant merkle state - a node can detect if its state is corrupted or if a validator is dishonestly executing the protocol.
Proof-of-stake support - run a private or public permissioned network.
On-chain governance primitives - stakeholders may vote for autonomous smart contract upgrades.
Ethereum account world-view - state and code is organised into cryptographically-addressable accounts.
Low-level permissioning - code execution permissions can be set on a per-account basis.
Event streaming - application state is organised in an event stream and can drive external systems.
SQL mapping layer - map smart contract event emissions to SQL tables using a projection specification.
GRPC interfaces - all RPC calls can be accessed from any language with GRPC support. Protobuf is used extensively for core objects.
Javascript client library - client library uses code generation to provide access to contracts via statically Typescript objects.
Keys service - provides optional delegating signing at the server or via a local proxy
Web3 RPC - provides compatibility for mainnet Ethereum tooling such as Truffle and Metamask
What it is not
An Ethereum mainnet client - we do not speak devp2p and various implementation details are different. We are Ethereum-derived but exploit greater freedom than mainnet compatibility would allow.
Project information generally updated on a quarterly basis can be found on the Hyperledger Burrow Wiki.
Documentation
Burrow getting started documentation is available on the documentation site (source markdown files can be found in docs) and programmatic API in GoDocs.
