[S4|I1] PBFT | Def: Three-phase Byzantine agreement for replicated services under partial synchrony | Steps: propose -> pre-prepare -> prepare -> commit | Edge: Fails when over one-third replicas are Byzantine [S4|I2] HotStuff | Def: Leader-based BFT using quorum certificates for linear communication | Steps: propose -> vote -> aggregate certificate -> commit | Edge: Leader bottleneck or view-change delays stall progress [S4|I3] Tendermint | Def: Round-based BFT with voting, locking, and accountable safety | Steps: propose -> prevote -> precommit -> finalize | Edge: Liveness stalls if over one-third validators offline [S4|I4] Nakamoto Consensus | Def: Longest-chain proof-of-work consensus with probabilistic finality | Steps: mine -> broadcast -> extend longest chain -> confirm | Edge: Forks and reorganizations threaten recent block finality [S4|I5] Proof of Stake | Def: Validator selection weighted by bonded economic stake | Steps: stake -> select proposer -> attest -> finalize | Edge: Nothing-at-stake and long-range attacks need mitigations [S4|I6] Finality Gadget | Def: Overlay that finalizes blocks from underlying chain growth | Steps: grow chain -> vote checkpoints -> justify -> finalize | Edge: Conflicting finality indicates at least one-third slashable fault [CP 4/6 | NEXT: S5|I1] [S5|I1] Sharding | Def: Partition state and validators into parallel processing shards | Steps: assign shards -> process locally -> cross-shard commit -> merge | Edge: Cross-shard transactions add latency and complexity [S5|I2] DAG-based Consensus | Def: Concurrent block graph enabling parallel ordering and throughput | Steps: propose vertices -> link parents -> order graph -> commit | Edge: Ordering complexity grows with graph width [S5|I3] Pipelining | Def: Overlap proposal, voting, and execution across consensus rounds | Steps: propose round -> pipeline votes -> overlap execution -> commit | Edge: Pipeline stalls propagate delays to later rounds [S5|I4] Batching | Def: Group many transactions into one consensus proposal | Steps: collect transactions -> form batch -> propose batch -> execute | Edge: Larger batches increase latency for individual transactions [S5|I5] Checkpointing | Def: Snapshot state periodically to prune history and speed recovery | Steps: reach height -> snapshot state -> prune history -> distribute snapshot | Edge: Stale snapshots can hide recent committed state [S5|I6] Performance Tuning | Def: Adjust block size, timeout, batch limits for workload | Steps: measure load -> adjust parameters -> benchmark -> deploy | Edge: Aggressive tuning reduces fault tolerance margins [CP 5/6 | NEXT: S6|I1] [S6|I1] Formal Verification | Def: Prove safety and liveness properties with mathematical methods | Steps: model protocol -> specify properties -> prove invariants -> audit proof | Edge: Models may omit real network behaviors [S6|I2] Model Checking | Def: Exhaustively explore finite states for property violations | Steps: build model -> define properties -> explore states -> inspect counterexamples | Edge: State explosion limits system size checked [S6|I3] Chaos Testing | Def: Inject faults deliberately to validate resilience in production-like environments | Steps: plan faults -> inject failures -> observe recovery -> fix weaknesses | Edge: Poorly scoped tests can disrupt real services [S6|I4] Monitoring and Alerting | Def: Track validator health, latency, forks, and consensus progress | Steps: collect metrics -> set thresholds -> alert anomalies -> investigate | Edge: Alert fatigue hides genuine consensus failures [S6|I5] Incident Response | Def: Coordinated procedures to halt, diagnose, recover failing consensus | Steps: detect incident -> halt safely -> diagnose cause -> recover | Edge: Slow coordination worsens safety incidents [S6|I6] Upgrades and Governance | Def: Coordinate protocol changes through voting and staged activation | Steps: propose change -> vote -> stage activation -> monitor rollout | Edge: Contentious upgrades can split network permanently [CP 6/6 | COMPLETE]