Consensus Overview
Scope
- Consensus crate
- Artifact pool
- Chain key technology
- Ingress manager
- Orchestrator
- Ic-replay
- Upgrades
- Subnet recovery
- Subnet backup
- Subnet splitting
Summary
- The consensus layer receives unordered messages from the P2P layer.
- Consensus achieves agreement as to which messages and in which order the IC should execute.
- It can do this as long as more than ⅔ of the nodes are honest and functioning well.
Resources
- Consensus
- Chain Key Cryptography
- Non-Interactive Distributed Key Generation (NIDKG)
- GitHub: Orchestrator Docs
Codebase
- Testnet
- Artifact Pool
- Backup
- Consensus
- Canister HTTP
- DKG Interface
- Ingress Manager
- Canister HTTP Interface
- Orchestrator
- Recovery
- Registry (NNS) Subnet Helper
- Registry (NNS) Unassigned Nodes helper
- Replay
- Tests