{
  "slug": "fork-consistency",
  "term": "Fork consistency",
  "aliases": [],
  "definition": "Fork consistency allows an untrusted server to split clients' histories but prevents silently rejoining those histories after they diverge.",
  "note": "In SUNDR, honest clients retain their own last operation and authenticate accepted histories; seeing another branch or communicating can expose divergence, but detection need not be immediate. Moving between clients requires the retained state as well as the key. [fork-sundr]\n\nLocal signature validity, payload equality, extension of a remembered checkpoint and cross-observer agreement are separate checks. RFC 9162 illustrates the distinction for transparency logs; it is not a storage protocol. [fork-ct]\n\nDepot uses Fork-Join-Causal consistency and additional protocols to support progress after divergence, rather than the same permanent no-join condition. A read still needs a correct reachable holder. [fork-depot]\n\nHesela's deterministic illustration explicitly restores an old in-memory checkpoint: a previously rejected branch becomes acceptable while a separately retained newer checkpoint still rejects it. Equal final payloads also coexist with incompatible histories. These controls do not test backup software or crashes. [hesela-example]",
  "status": "research",
  "advantages": [],
  "limitations": [
    {
      "text": "The retained-state assumption excludes silently restoring an older checkpoint; a recovered signing key alone does not establish freshness.",
      "citationIds": [
        "fork-sundr",
        "hesela-example"
      ]
    },
    {
      "text": "The no-wait impossibility result is scoped to asynchronous server-mediated access to at least two single-writer/multi-reader registers, not all authenticated storage.",
      "citationIds": [
        "fork-blocking"
      ]
    }
  ],
  "related": [
    "linearizability",
    "merkle-tree",
    "replay-attack",
    "session-guarantees"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-20",
  "citations": [
    {
      "id": "fork-sundr",
      "title": "Li et al. Secure Untrusted Data Repository (SUNDR). OSDI 2004; sections 2 and 3.1-3.2.",
      "url": "https://www.scs.stanford.edu/~dm/home/papers/li:sundr.pdf",
      "accessed": "2026-11-11"
    },
    {
      "id": "fork-depot",
      "title": "Mahajan et al. Depot: Cloud storage with minimal trust. OSDI 2010; section 1.",
      "url": "https://www.cs.cornell.edu/lorenzo/papers/Mahajan10Depot.pdf",
      "accessed": "2026-11-11"
    },
    {
      "id": "fork-ct",
      "title": "RFC 9162: Certificate Transparency Version 2.0. Experimental, 2021; sections 8.3 and 11.3.",
      "url": "https://www.rfc-editor.org/rfc/rfc9162.html",
      "accessed": "2026-11-11"
    },
    {
      "id": "fork-blocking",
      "title": "Cachin, Keidar and Shraer. Fork Sequential Consistency is Blocking. arXiv:0805.2068v1, 2008; section 2 and Theorem 1.",
      "url": "https://arxiv.org/html/0805.2068",
      "accessed": "2026-11-11"
    },
    {
      "id": "hesela-example",
      "title": "Hesela: frozen signed-history results, source revision, SHA-256 hashes and offline replay.",
      "url": "https://hesela.dev/research/fork-consistency/publication.json",
      "accessed": "2026-11-11"
    },
    {
      "id": "hesela-consistency",
      "title": "Hesela: Valid signatures do not establish a shared history.",
      "url": "https://hesela.com/analyses/storage-consistency-ordering/#fork-consistency",
      "accessed": "2026-11-11"
    }
  ],
  "provenance": [
    "Definition scoped to SUNDR; no claim that every signed history implements its protocol. [fork-sundr]",
    "Seven original cases plus six checkpoint/offer controls and encoding/equal-payload checks use real Ed25519 with public fixture keys. No network, durable checkpoint, hardware or deployed-service experiment. [hesela-example]",
    "The baseline in the replay ZIP is explicitly defective historical code; the corrected verifier rejects noncanonical signature text. [hesela-example]",
    "RFC 9162 is Experimental and does not specify a gossip protocol. [fork-ct]"
  ]
}
