why join the navy.
This is just something I did for my intern, it’s probably not error-free, I have searched through the Internet for some exact answers though, it seems that there are still ongoing topics remained. I have also listed the references where I concluded the results.
In general, Quorum is an enterprise-focused blockchain platform based on Ethereum. It provides a layer on top of Ethereum which enables it to perform private transactions and makes it more robust by using different consensus algorithms. Quorum is developed by J.P.Morgan, which plans to implement a Global Network Payments initiative to help banks use distributed networks.
It is a Permissioned Blockchain developed by Linux Foundation with support from IBM and many large enterprises as members. HyperLedger Fabric is designed as a plug for implementation of blockchain technology to develop high-scaling blockchain applications with various level of permissions.
Hyperledger, Ethereum, and Quorum have emerged as some of the most popular blockchain development platforms. Here I will compare the major points of distinction between the Hyperledger and Quorum platforms.
The architecture of Hyperledger Fabric comprises of the following components:
As the purpose of Quorum is to be designed as a lightweight fork so that it can take advantage of the Ethereum implementation. It is updated regularly such that it is in line with the future geth releases. The architecture of Quorum comprises of the following components:
Hyperledger Fabric offers the ability to set up shared channels (each one a ledger) between parties, with the transaction within the channel being private to outside parties. It avoids that channel-level account balances can be viewed by channel participants.
Quorum achieves privacy via public and individual private state trees, with the public state tree storing vanilla Ethereum transactions and hashes of encrypted private smart contract changes. Quorum thus offers and requires both private and public smart contract transactions. The private contracts enable private transactions between two parties, while public transactions are used to distribute zero-knowledge proofs for verification on the Quorum network.
In Hyperledger Fabric, the network complexity rises with each new participant, and participants need to maintain and move funds between individual channel-level accounts for each channel.
Quorum offers significantly higher performance than public geth(ethereum) as it is more robust and has the capability to process more than 100 transactions per second which is much more than that of Bitcoin and Ethereum.
Consensus in Hyperledger Fabric
In the case of Hyperledger Fabric, the understanding of consensus is broad, and it encircles the entire transaction flow beginning with initiating a transaction to the network and then committing it in the ledger. There are two kinds of consensus. One is lottery-based and the other is voting-based. Lottery-based refers to algorithms such as Proof-of-Work (PoW) and Proof-of-Elapsed Time (PoET).
Hyperledger Fabric v1.4.1 introduced Raft as a crash fault tolerance consensus. Raft follows a “leader and follower” model wherein a leader node is elected for every channel and the decision taken by the leader node is replicated by the follower nodes. In case of failure, Raft ensures that the system is able to take decisions and process client requests.
Consensus in Quorum
Quorum uses a consensus protocol called “QuorumChain”. The consensus here is relatively straightforward and a consensus is reached by simple majority voting. A certain number of nodes are relegated with voting rights. These nodes only verify the transaction. The two consensus algorithms used by Quorum are:
Raft is a consensus algorithm with Crash Fault Tolerance (CFT). It helps perform transactions faster as the block minting process is 50ms. It helps save storage space by mining only the proper blocks and not the empty blocks. Its other significant features are transaction finality and on-demand block creation.
This is a consensus algorithm which is based on Byzantine Fault Tolerance. It helps protect the blockchain. It provides protection for the blocks generated in the blockchain.
Hyperledger Fabric uses “Chaincode” as the business logic of the technology. Chaincode takes leverage from the in-built trust of blockchain technology and underlying consensus from the peers. Hyperledger also allows you to write the ‘Chaincode’ in any standard programming language. ‘‘Chaincode’’ can be written in either Node.js, Go, and Java.
Quorum, soft forked from Ethereum supports both public and private contracts. The public contracts are built with Solidity whereas the private contracts which allow specifying which nodes in the network have the access to execute the contract. What’s more, to understand here is that Quorum privacy design imposes constraints, a private contract cannot be updated to a public contract and vice-versa.
Use cases of Hyperledger Fabric
Use cases of Quorum
|Architecture||Enormous technology stack including membership services, blockchain services and chaincode services||The blockchain platform on Ethereum with modified services|
|Privacy||Achieved by setting up shared channels (each one a ledger) between parties||Achieved by public and individual private state trees|
|Performance||Maximum TPS is around 500 in v1.0||Able to process more than 100 transactions per second|
|Consensus||Uses permissioned voting-based consensus from the pool of other consensus named the lottery-based consensus, uses Raft as a crash fault tolerance consensus||Uses a consensus protocol called “QuorumChain”,uses Raft-based and Istanbul BFT for better fault tolerance|
|Smart Contracts||Uses “Chaincode” as the business logic of the technology||Use soft forked version from Ethereum supports both public and private contracts|
|Use Cases||Enterprise-focused in broad fields||Enterprise-focused in the financial field|