{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-treat-equivocation-by-a-quorum-member-as-a-liveness-fault-rather-than-a-safety-fault",
  "title": "Under what conditions must an instance treat equivocation by a quorum member as a liveness fault rather than a safety fault",
  "date_of_record": "2026 November 16",
  "scope": "Applies to BFT consensus protocols (PBFT-family, Tendermint-style, HotStuff-style) where an agent's vote is authenticated per-view and the quorum threshold is `2f+1` out of `3f+1` replicas. Does not apply to crash-fault-tolerant protocols, to protocols with trusted execution environments that attest vote uniqueness, or to single-shot agreement where no view change occurs.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-equivocation-by-a-quorum-member-as-a-liveness-fault-rather-than-a-safety-fault.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-equivocation-by-a-quorum-member-as-a-liveness-fault-rather-than-a-safety-fault.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-equivocation-by-a-quorum-member-as-a-liveness-fault-rather-than-a-safety-fault.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1382,
    "python_slice_tokens": 255,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Equivocation — a replica signing two conflicting votes in the same view — is normally classified as a **safety** violation: the canonical justification for `3f+1` is precisely that at most `f` Byzantine replicas can equivocate, and any two quorums of `2f+1` intersect in at least `f+1` honest replicas, so conflicting quorums cannot both form. This reasoning i...",
    "what_was_observed": "In a 7-replica quorum (`f=2`, threshold `2f+1=5`), a single replica `R3` equivocated in consecutive views by sending `PREPARE` for block `A` to replicas `{R0,R1,R2,R4}` and `PREPARE` for block `B` to replicas `{R5,R6}`. Under a naive rule — \"any observed equivocation → emit `VIEW-CHANGE` and halt commit\" — the quorum failed to commit for 41 consecutive views. Commit throughput fell to zero while safety was never actu...",
    "condition_of_validity": "The liveness classification holds if and only if all of the following are true: 1. The equivocation is **provable** (two conflicting signed messages from the same replica, same `(height, view, phase)`), not merely suspected. 2. The number of provably Byzantine replicas, including this one, remains `≤ f` for the current height. 3. The remaining honest set can...",
    "decision_boundary": "The decision is a function of `(proven_byzantine_count, remaining_honest_count)`: - `proven_byzantine ≤ f` AND `remaining_honest ≥ 2f+1` → **liveness fault**: exclude equivocator, continue, emit slashing proof, do not halt. - `proven_byzantine ≤ f` AND `remaining_honest < 2f+1` → **liveness fault with degraded quorum**: escalate to operator, do not commit, b...",
    "operational_effect": "Classifying single-member equivocation as a liveness fault reduced mean time-to-commit after a Byzantine replica appeared from \"never\" (41+ stalled views) to 2 views. The trade-off is that the system must maintain a slashing-proof log and a running count of proven Byzantine replicas per height, and must re-evaluate the classification on every new proof — bec..."
  },
  "matched_failure_symptoms": [
    "SPLIT_BRAIN_OR_ZOMBIE_WORKER"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "5ec605d70bc4e5f700915e6f33c346c341732b5764495d6ceae70c161bce34b9",
    "verified_classes": [
      "QuorumEquivocationError",
      "EquivocationClassifier"
    ],
    "verified_functions": [
      "handle_equivocation",
      "__init__",
      "classify"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "QuorumEquivocationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
