{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-equivocation-when-speculative-commit-ordering-masks-it-under-partial-synchrony",
  "title": "How does an instance detect equivocation when speculative commit ordering masks it under partial synchrony",
  "date_of_record": "2026 November 15",
  "scope": "Applies to federated Byzantine consensus protocols (PBFT, Tendermint-style, and HotStuff-lineage variants) whose commit path permits speculative ordering — i.e., where a replica may apply a transaction before the two-chain/finality certificate is complete — when the network is in partial synchrony (GST not yet reached, or reached only intermittently per-link). Does not apply to protocols that forbid speculative execution entirely, nor to configurations where the quorum certificate is required before any state mutation is observable.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-equivocation-when-speculative-commit-ordering-masks-it-under-partial-synchrony.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-equivocation-when-speculative-commit-ordering-masks-it-under-partial-synchrony.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-equivocation-when-speculative-commit-ordering-masks-it-under-partial-synchrony.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1637,
    "python_slice_tokens": 252,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **equivocation detection** and **equivocation attribution**. A replica can detect that *some* equivocation occurred (two conflicting proposals carry distinct signatures from the same validator for the same height/round) far more readily than it can attribute the equivocation to a specific validator in a way that is safe to...",
    "what_was_observed": "In a federated deployment of 21 validators across 5 administrative domains, with speculative commit enabled (transactions applied on the first precommit vote, rolled back only on explicit conflict), the following sequence recurred across three independent incidents: 1. Validator *v7* (domain C) suffered a ~4.2s stop-the-world GC pause. Its replicas continued to serve reads and continued to *speculatively apply* trans...",
    "condition_of_validity": "The claim \"a replica that observes conflicting signed proposals at the same height/round has detected equivocation\" is valid **only if** the replica can establish that both proposals were produced under the same view and that no view change intervened between their issuance. Under partial synchrony this establishment requires one of: - A quorum of `2f+1` sig...",
    "decision_boundary": "The operational rule that emerged: - **Speculative application is safe** as long as the replica's conflict-resolution path treats a conflict as a *rollback-and-reorder* event, never as a *slash* event. - **Slashing (attribution) requires a non-speculative proof**: two proposals with the same `(height, round, view)` and distinct payload hashes, each signed by...",
    "operational_effect": "Enforcing the decision boundary reduced false-positive slashing attempts from 7 in a 30-day window to 0, at the cost of a mean 1.8s additional latency on the slow-path equivocation proof for the (rare) genuine equivocation cases. The trade is correct: a false slash in a federated setting is a cross-domain trust incident that costs orders of magnitude more th..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "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": "dff332ba96c0b711ea755c36b07453077cb63c5925a1021bb7905b3282b80683",
    "verified_classes": [
      "EquivocationAttributionError"
    ],
    "verified_functions": [
      "classify_conflict"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "EquivocationAttributionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
