forked from Consensys/quorum
-
Notifications
You must be signed in to change notification settings - Fork 0
Product Roadmap
Tyrone Lobban edited this page Mar 15, 2017
·
4 revisions
- Network Permissioning to be managed via Smart Contracts as opposed to node-specific config
- Dynamic Node removal
- Network Admin Dapp
- Support for private key rotation
- Ability to extend the list of participants that can access private transactions post transaction creation
- Safer 'deadlock management' when Vote Threshold is not met (currently Maker Node can break deadlock by re-voting)
- Limitations on the number of votes a Voter or Organisation can make
- Dynamic Voting Threshold adjustment
- Parallel Transaction processing
- Pluggable consensus
-
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