diff options
| author | tv <tv@krebsco.de> | 2026-11-16 10:39:19 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 10:39:19 +0000 |
| commit | e4e24cad0c65bbf0bb0cdbb8d1fe1b5b36ad94a2 (patch) | |
| tree | ed27c8b38f3d5ded5b6b01c83b28596324a923a6 /docs | |
| parent | 023487227a61d4dfab0ddb01b80bf7c095c801fd (diff) | |
federation: a snapshot keeps each place's value as the federation reads it
A place's value is read among the envelopes a key their party holds
signed, but a remake's snapshot, a fork's genesis and the replay held
what the old document "read as", which continuum's merged view has as
the first of all the envelopes there, by `seq`: a builder reusing it
would keep a dropped key's envelope ahead of the party's, and nothing at
the place would count in the new epoch. Each holds, and replays to, the
place's value as the federation reads it.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/federation.md | 70 |
1 files changed, 36 insertions, 34 deletions
diff --git a/docs/federation.md b/docs/federation.md index 16b3d3c..9cca39b 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -420,20 +420,20 @@ the group won't follow passed, the parties can't agree, or it leaves the federat **forks**: it starts a swarm of its own from the document. 1. One of the group starts the new swarm. Its genesis change holds what the old document - read as at heads it names, built byte for byte from the fork's first version and - those heads alone, with the swarm's Automerge version: its writer from the fork's - name, time 0, no message, nothing of a remake's metadata but what the heads fix; so - one version and one set of heads make one swarm, and a node with an empty document - takes it on its peers' word, as it takes an epoch. It holds all of it but for what a - snapshot leaves out, by the version current at those heads (Remakes), the - federation's versions, and continuum's own data (member entries, remake records and - acks, earlier epochs' metadata, the swarm's name): of versions, only the group's own, - the fork's first. It names the highest version at those heads as the one it changes, - is numbered one past it, and names anew the node lists of the parties that start it, - and the keys of any party whose keys it changes; judged by none, as an epoch's first - change is. Every proposal is a chance to fork: the version is usually one that didn't - pass. To leave the federation, the genesis holds another policy instead, and what it - needs. + read as at heads it names, each place's value as the federation reads it (The + design), built byte for byte from the fork's first version and those heads alone, + with the swarm's Automerge version: its writer from the fork's name, time 0, no + message, nothing of a remake's metadata but what the heads fix; so one version and + one set of heads make one swarm, and a node with an empty document takes it on its + peers' word, as it takes an epoch. It holds all of it but for what a snapshot leaves + out, by the version current at those heads (Remakes), the federation's versions, and + continuum's own data (member entries, remake records and acks, earlier epochs' + metadata, the swarm's name): of versions, only the group's own, the fork's first. It + names the highest version at those heads as the one it changes, is numbered one past + it, and names anew the node lists of the parties that start it, and the keys of any + party whose keys it changes; judged by none, as an epoch's first change is. Every + proposal is a chance to fork: the version is usually one that didn't pass. To leave + the federation, the genesis holds another policy instead, and what it needs. 2. A fork is named by the hash of its first version together with the heads it names, which nobody can steer to a given name, the old swarm's least of all: its genesis change writes it at `_continuum/swarm`, as every node checks, and an envelope's meta @@ -520,27 +520,28 @@ asks of a remake: epoch before its own, from the old document it keeps, as it builds any, and switches, what it wrote since replayed: so nodes that followed different decisions come together where their operators choose. -* **The snapshot** holds what the old document read as at the base, but for what counts - no more by the version current there and is or names a version before it, a party's - `null` naming a version before it, and the member entry of a node its party doesn't - list there: nothing naming an earlier version can be written in the new epoch, an - empty place reads as one holding `null` does, and a node listed again registers - again. +* **The snapshot** holds what the old document read as at the base, each place's value + as the federation reads it (The design), not the first of all its envelopes as + continuum's merged view has it, but for what counts no more by the version current + there and is or names a version before it, a party's `null` naming a version before + it, and the member entry of a node its party doesn't list there: nothing naming an + earlier version can be written in the new epoch, an empty place reads as one holding + `null` does, and a node listed again registers again. * **Writes after the base** are replayed as the policy shapes them: at each place, the - chain of envelopes that leads from what the new document holds there to what the old - one reads, each in a change of its own, judged again in the new epoch, the other - writes with them, each after those its change builds on, clocks only between changes - neither of which saw the other, as continuum replays under a strict policy *(checked: - `remake::delta`)*. No version is among them: a node that took one written after the - base doesn't switch, so what it replays names the version current at the base, or one - before. Votes and proposals go by the keys their version names, which the snapshot - holds, so they count as cast in the new epoch too, whatever key sets of their party - are replayed around them. Whether a place is held already goes by version number, then - `seq`. What the new epoch refuses is tried again once the rest is replayed, as the - clocks may have put it before what it builds on (a vote committed again at another - history, before the nays that freed its party); what it refuses then (its key was - dropped, its place given to another) goes to the quarantine of the node that holds it, - and its party signs it again if it still may. + chain of envelopes that leads from what the new document holds there to the old one's + value there, as the federation reads it, each in a change of its own, judged again in + the new epoch, the other writes with them, each after those its change builds on, + clocks only between changes neither of which saw the other, as continuum replays under + a strict policy *(checked: `remake::delta`)*. No version is among them: a node that + took one written after the base doesn't switch, so what it replays names the version + current at the base, or one before. Votes and proposals go by the keys their version + names, which the snapshot holds, so they count as cast in the new epoch too, whatever + key sets of their party are replayed around them. Whether a place is held already goes + by version number, then `seq`. What the new epoch refuses is tried again once the rest + is replayed, as the clocks may have put it before what it builds on (a vote committed + again at another history, before the nays that freed its party); what it refuses then + (its key was dropped, its place given to another) goes to the quarantine of the node + that holds it, and its party signs it again if it still may. So a remake decides nothing that counts, but what it can't hold: of two envelopes of one version and `seq` at a place at the base, the snapshot keeps one, and a write after the @@ -710,6 +711,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 79 | Keys voting twice, or a writer forked, part honest nodes | An operator has its node drop what it took and take the other side's; no fork | sim | | 80 | An honest party backs a second proposal once its first is dead; another party later signs `true` on the first too | It isn't named: its first proposal is dead by all the votes; the party with `true` and `false` on one is | unit | | 81 | A node whose operator had it drop a version is sent it again, or holds the votes that passed it | It refuses those changes and writes the version no more, in that epoch, until its operator says otherwise | unit | +| 82 | A key its party dropped wrote, from a history before the drop, ahead of the party's envelope; then a remake or a fork | The snapshot or genesis keeps the party's value, as the federation reads it | unit | ## Roads not taken |
