{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-in-a-byzantine-quorum-reconstructs-quorum-certificates-from-stale-view-membership",
  "title": "What happens when an instance in a Byzantine quorum reconstructs quorum certificates from stale view membership",
  "date_of_record": "2026 November 15",
  "scope": "Applies to BFT consensus protocols (PBFT-derived, HotStuff-derived, and Tendermint-style) where quorum certificates (QCs) are aggregated over a view-specific validator set and committed across view changes. Does not apply to protocols with immutable, globally fixed validator sets, nor to crash-fault-tolerant consensus where equivocation is impossible.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-in-a-byzantine-quorum-reconstructs-quorum-certificates-from-stale-view-membership.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-in-a-byzantine-quorum-reconstructs-quorum-certificates-from-stale-view-membership.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-in-a-byzantine-quorum-reconstructs-quorum-certificates-from-stale-view-membership.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1822,
    "python_slice_tokens": 372,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is not \"Byzantine node sends bad messages.\" It is the distinction between **quorum validity** (a QC aggregates signatures from a set that constitutes a quorum under *some* view's membership) and **quorum legitimacy** (that same QC aggregates signatures from a set that constitutes a quorum under the membership *active at the height/ep...",
    "what_was_observed": "In a four-validator deployment (f=1, quorum=3) undergoing a rolling reconfiguration from set {A,B,C,D} to {A,B,C,E}, the following sequence was observed: 1. Set {A,B,C,D} committed height 100 with a QC over {A,B,C}. 2. Reconfiguration to {A,B,C,E} began at height 101. D was removed; E added. 3. A Byzantine node (compromised A) replayed the height-100 QC, re-signed with its retained key, and attached it to a *new* pro...",
    "condition_of_validity": "The invariant that must hold, and that naive verifiers do not enforce: > A QC is legitimate for height h if and only if every constituent signature is over a message binding (chain_id, epoch(h), height h, view, digest), and the signer set constitutes a quorum under the membership defined for epoch(h). The failure requires all of the following to co-occur: - ...",
    "decision_boundary": "The operational decision is where to place the epoch/height binding check. Three options, with distinct tradeoffs: - **Bind in the signed preimage (strongest).** Include `(chain_id, epoch, height, view, digest)` in the message each validator signs. Replay across epochs is cryptographically impossible. Cost: every validator must know the current epoch at sign...",
    "operational_effect": "The observable effect is **commitment divergence under reconfiguration**: two honest agents hold different committed states at the same height, each backed by a locally valid QC. This is not a safety violation in the classical sense (no two conflicting QCs at the *same* epoch), but it is a *cross-epoch* equivocation that classical safety proofs do not cover,..."
  },
  "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": "ef6d5dcbbc63b255f4ab33633c47309a66fcb459b0785f23542978ab36483161",
    "verified_classes": [
      "StaleEpochQuorumError",
      "SignedVote"
    ],
    "verified_functions": [
      "verify_quorum_certificate"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 7,
    "raised_exceptions": [
      "StaleEpochQuorumError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
