https://store-images.s-microsoft.com/image/apps.14993.ce6b206a-16fb-4277-a099-fb1e80357560.e584780a-0112-4957-b8f4-5292dafa064f.9a523351-bab2-41d9-8243-95572dee8d65

Quorum Dev Quickstart

ConsenSys

Quorum Dev Quickstart

ConsenSys

Deploy a single-VM enterprise blockchain network with monitoring and dashboards in minutes

ConsenSys Quorum is an open-source protocol layer that provides developers with the flexibility and reliability needed to make their blockchain applications successful. ConsenSys Quorum comprises a suite of configurable components and APIs, enabling you to customize your use case and production environment. Hyperledger Besu is an open source Ethereum client maintained by the Hyperledger community, including ConsenSys. Besu is Mainnet compatible, Java-based, Apache 2.0 licensed, and extensible through its Java plugin framework. GoQuorum is an open-source Ethereum client maintained by ConsenSys. GoQuorum is Go-based and GPL licensed.

Both are compatible with Solidity smart contracts, and are well suited well for enterprise use cases that require privacy, high throughput, finality such as settlement, digital assets issuance and payments. Both clients support enterprise features including privacy & permissioning and you can use them to develop enterprise applications requiring secure, high-performance transaction processing in a private network. This deployment gives you what our Quickstart offers on a single Azure VM, i.e a private network comprising 4 validators, rpcnode, private transaction nodes (if selected), monitoring (block explorer, prometheus, grafana, ELK, cakeshop (goQuorum only)).


To get Started:

- ssh in to the VM with credentials selected at creation

- Run the command below at the user's home directory:

 ./run.sh


The account keys for Smart Contract and/or DApp development are in Github. Please note that because the private keys are available to the public, they are for dev & test use only. Do not use them on any public network such as mainnet except to test.

After the deployment completes, you should be able to monitor the various services below using the public IP or the FQDN of the VM like so: