- Product
- Chains
- Core
- Appchains
- Data
- Storage
- Hosting
- Use cases
- Pricing
- Enterprise
- Customers
- Blog
- Developers
- Get started
- Guides
- Resources
Discover key facts and figures about major blockchain protocols that are empowering transformations across industries.
An open-source blockchain platform that combines the innovation of the public Ethereum community with enhancements to support enterprise needs.
| Consensus | Raft, IBFT |
| Public / Private / Permissioned | Private, Permissioned |
| Smart contracts | Yes |
| Smart contract language(s) supported | Solidity, Vyper |
| Transaction privacy | Yes |
| Transaction visibility | Private transactions between participants are hidden from all others. |
| Transaction ordering | In 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. |
| Version | Peer: 2.7.0; Transaction manager: Tessera 0.10.6 |
| Explorer | Epirus |
Raft can tolerate an f number of faulty nodes in n=2f+1, where n is the total number of nodes.
IBFT can tolerate an f number of faulty nodes in n=3f+1, where n is the total number of nodes.
Fast block times, transaction finality, and on-demand block creation.
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, slower than 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), learner, 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.
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.
Tokenization, copyright protection, supply chain, energy and commodity trading, provenance.
Learn more about the free usage period to get started right away.
Complete the form below, and our experts will get in touch with you.
Ethereum
BNB Smart Chain
Polygon
Arbitrum
Optimism
Avalanche
zkSync Era
Starknet
Scroll
Aptos
Fantom
Cronos
Gnosis Chain
Klaytn
Moonbeam
Celo
Aurora
Oasis Sapphire
Polygon zkEVM
Bitcoin
Tezos
Harmony
