Consensus Committee

Overview

A consensus committee is the participant subset responsible for specific agreement duties in a slot, round, epoch, or shard. Members may attest to blocks, sign checkpoints, sample data, aggregate votes, or form a quorum certificate.

Selection and weighting determine the probability that honest members control the required threshold. Committees reduce communication overhead, but correlated infrastructure, bribery, unavailable members, or biased randomness can weaken their effective independence. Protocols should make committee membership and signatures verifiable while limiting advance predictability where attacks are possible. Operators need timely duty scheduling and secure keys. Integrators should validate the committee period, membership root, signature threshold, and domain before accepting a committee-backed proof. Evaluation should cover the complete decision process: who may propose data, how other participants validate it, how competing histories are ranked, and what evidence makes an outcome difficult or impossible to reverse. A mechanism’s label does not define those details across every implementation.

Safety, liveness, and accountability should be assessed separately under partitions and coordinated failures. Security assumptions depend on the resource or authority used to influence consensus, participant concentration, network timing, client behavior, and the cost of equivocation, censorship, or history revision. Payment applications relying on Consensus Committee need network-specific confirmation and finality policies. Observing a block locally does not establish settlement. The system should confirm canonicality, execution success, and the network’s strongest finality evidence before irreversible fulfillment. Recovery plans must reflect whether the design halts to preserve safety, permits temporary reorganization, or relies on social or governance intervention after exceptional failure. Operations teams should monitor chain progress, competing branches, participation, and protocol-specific fault indicators.