Everything You Must Know About Key
Blockchain Protocols

An open source blockchain platform that combines the innovation of the public Ethereum community with enhancements to support enterprise needs.

ConsensusRaft, IBFT
Public / Private / PermissionedPrivate, Permissioned
Smart contractsYes
Smart contract language(s) supportedSolidity
Transaction privacyYes
Transaction visibilityPrivate transactions between participants are hidden from all others.
Transaction orderingIn Raft, a synchronization between the leader and other nodes is made to ensure that the order of transactions is the same for all nodes before executing them. In IBFT, there is a single, agreed-upon ordering for transactions in the blockchain.

Fault tolerance

Raft

If there are 2n+1 nodes, then up to n can fail without the network losing its consistency. If the leader crashes, the remainder of the network will automatically elect a new leader after a set period of timeout, and the network will continue to function.

IBFT

The system can tolerate at most F faulty nodes in a network with N validator nodes, where N = 3F + 1.

Performance

Raft

Fast blocktimes, transaction finality, and on-demand block creation

IBFT

IBFT is an implementation of the Practical Byzantine Fault Tolerance algorithm with modifications.

The main difference from Raft, or any other Crash Fault Tolerance algorithm, is that Raft followers blindly trust their leader.

In IBFT, however, each block requires multiple rounds of voting by the set of validators to arrive at a mutual agreement, which is recorded as a collection of signatures on the block content. IBFT is, therefore, a lot slower than Raft.

Suggestions for use with consortiums

Raft

With Raft-based consensus where BFT is not a requirement, allow member organizations to add as many nodes as they wish to a network. Any node can be a leader (minter) or follower (verifier). Choose Raft when speed is a priority and threat of malicious activity from any member is low. Use when native privacy of transactions and smart contracts is required.

IBFT

Controls need to be put in place to limit any member organization from running 2/3 of the nodes in the networks. Choose when there is a risk of malicious activity from members, at the expense of speed. Use when native privacy of transactions and smart contracts is required.

Industry use case

Tokenization, copyright protection, supply chain, energy and commodity trading, provenance.

Learn more

What’s next?

Quorum deployment is already supported on Chainstack. Learn more about the free trial plan to get started right away.

Keen to learn more about deploying, managing, and scaling your blockchain project?

Complete the form below, and our experts will get in touch with you.

Chainstack uses cookies to provide you with a secure and
personalized experience on its website. Learn more.