Ac Byzantine Consensus

Agreement when some participants may be malicious or arbitrarily broken: the Byzantine failure model and how it differs from crash faults, the 3f+1 replica arithmetic that makes it survivable, three-phase commit and the prepare and commit rounds PBFT runs, view changes when the primary itself is the fault, client quorums and how a reply is trusted, signed versus MAC-based message authentication, and the written Byzantine record. It explains the model and its arithmetic; it never recommends a protocol. Use when asking "byzantine fault", "byzantine agreement", "PBFT", "3f plus 1", "view change", "byzantine generals", "malicious replica", "signed messages versus MACs", "why do byzantine systems need more replicas". Not for crash-fault consensus of the Raft or Paxos family (ac-consensus-protocols), not for quorum intersection in majority systems (ac-consensus-protocols), not for security hardening of the endpoints themselves (ac-security-engineer).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit 23019056b9

Frequently asked questions

npx get-skill add jiayaoqijia/ac-byzantine-consensus