forked from Consensys/quorum
-
Notifications
You must be signed in to change notification settings - Fork 0
Quorum Consensus
chris-j-h edited this page Jul 13, 2018
·
2 revisions
With no need for POW/POS in a permissioned network, Quorum instead offers multiple consensus mechanisms that are more appropriate for consortium chains:
- Raft-based Consensus: A consensus model for faster blocktimes, transaction finality, and on-demand block creation. See Raft-based consensus for Ethereum/Quorum for more information
- Istanbul BFT (Byzantine Fault Tolerance) Consensus: A PBFT-inspired consensus algorithm with transaction finality, by AMIS. See Istanbul BFT Consensus documentation, the RPC API, and this technical web article for more information
-
Getting To Know Quorum
-
Quorum Overview
- What Is Quorum?
- Architecture
- Component Overview
-
Transaction Processing & Privacy
- Public Transactions
- Private Transactions
- Processing Transactions
-
Quorum Consensus
- Raft-based Consensus
- Istanbul BFT Consensus
-
Security & Network Permissioning
- Network Permissioning
- Enclave Encryption Technique
- Private Key Storage Algorithm
-
Quorum Overview
-
Getting Set Up
- Setup Overview & Quickstart
- Building Quorum Node From Source
- Running Tests
- Installing Constellation
- Installing Tessera
-
Using Quorum
- Running Quorum
- Developing Smart Contracts
- Setting up a Permissioned Network
- Quorum API
- Using ZSL
- FAQ
- Product Roadmap