diff options
| author | tv <tv@krebsco.de> | 2026-11-16 04:11:35 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 04:11:35 +0000 |
| commit | 185fb518c04a048bf02bc3b926149cfeb9af5b4b (patch) | |
| tree | eb26f95adbd18fb41975b10947d449300cf5c6f0 /docs | |
| parent | 61a13f5ba52afcb6bec3534b8d016708c1581a4e (diff) | |
federation: a place's value among the envelopes their party's keys signed
A place's value was the first of all the envelopes it held, by version,
then `seq`, and it counted only while its key was its party's. So a key
the party had dropped, by a member committing at a history from before
the drop, wrote ahead of the party's envelope, replacing it, with a
higher `seq` each time the party wrote again: nothing at the place
counted until a version named the party's keys anew.
A place's value is the first of the envelopes there that a key their
party holds signed; judging, and the envelope a `prev` names, go by all
of them as before. And a party signs again what should stay after the
set that drops a key, not only before: what the dropped key writes at a
history from before can't name that as replaced, and counts no more, so
it takes nothing out.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/federation.md | 39 |
1 files changed, 23 insertions, 16 deletions
diff --git a/docs/federation.md b/docs/federation.md index 7e6d7d3..c385360 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -94,10 +94,13 @@ A change writing an envelope that names another version than the one current at history is refused, but for an epoch's first change (a remake's snapshot, a fork's genesis), which is judged by none, and for the key sets and node lists a version sets, which name the version being written (Keys). Of the envelopes a place holds, written at -once, the one with the highest version number is its value, then the highest `seq`, then -the lower SHA-256. So what a place holds is its party's to say, never the order of -operations, which whoever writes a change steers; and what was signed under a later -version is ahead of anything written at a history from before it. +once, its value is the one with the highest version number, then the highest `seq`, then +the lower SHA-256, among those signed by a key their party holds (Keys); where none is, +nothing there counts. Judging a change goes by all of them, as they stand: its `prev` +names the first of all. So what a place holds is its party's to say, never the order of +operations, which whoever writes a change steers, nor a key the party dropped; and what +was signed under a later version is ahead of anything written at a history from before +it. A swarm under a strict policy reads by `seq` alone, the same way, and replays a value its user signed as the chain of envelopes that leads to it *(checked: @@ -317,9 +320,12 @@ version, and the party's next set replaces it. of its set: votes, proposals, sets and node lists aside, which go by the keys their version names. A party changes its keys by itself: it writes a set with the new keys, signs again with one of them what should stay (a change is judged at its history, - where only the set it replaces is the party's), then writes a set without the old - ones (a client does it all). A key it dropped signs no set, and what it signed counts - no more; a key added back, from a backup say, brings back what it signed. + where only the set it replaces is the party's), writes a set without the old ones, + and signs again after it what should stay (a client does it all). What a key it + dropped signed counts no more; what that key writes at a history from before the drop + can't name what the party signed after it as replaced, and counts no more either, so + it takes nothing out. A key added back, from a backup say, brings back what it signed + where it is still there. * **Only a version revokes a key it names.** One lost or stolen is answered by a version naming the party's keys anew, whose set is ahead of every set before it. What the party then signs names that version, and is ahead of anything the old key writes at a @@ -344,7 +350,7 @@ whole. These count no more, and nothing else does: and node lists aside, which go by the keys their version names; 3. a proposal on a version that isn't current, and the votes on that version; 4. a version behind the current one; -5. an envelope behind another at its place; +5. an envelope behind another at its place, of those 2 leaves; 6. the member entry of a node its own party doesn't list (Nodes). Nothing is deleted within an epoch but by a party at its own place, writing `null`. @@ -529,14 +535,14 @@ long nodes stay together. ## Why it holds 1. **What counts.** A change is judged at its history, which its hash fixes, by the - version current there, which the versions written in that history fix, each judged - by the votes in its own. Every node judges alike, and refuses the change and - everything built on it. What counts is read from what the document holds: the - current version, the highest number; each party's keys, by that version and its - set; each place's value, by version number, then `seq`. None of it depends - on the order of operations, and no key is both a value and the way to places. A copy - of an older envelope is behind; a new one written at a history from before a version - is behind what is written under it. + version current there, which the versions written in that history fix, each judged by + the votes in its own. Every node judges alike, and refuses the change and everything + built on it. What counts is read from what the document holds: the current version, + the highest number; each party's keys, by that version and its set; each place's + value, among the envelopes their party's keys signed, by version number, then `seq`. + None of it depends on the order of operations, and no key is both a value and the way + to places. A copy of an older envelope is behind; a new one written at a history from + before a version is behind what is written under it. 2. **The policy.** A version is written only where, at one history, two thirds of the parties of the version it changes voted `true` for it, and a node takes it only where it changes the version the node reads. An honest party backs one proposal on a @@ -632,6 +638,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 64 | Nodes reinstalled under new IDs, their old entries left behind | Each counts no more, and the next snapshot leaves it out | unit | | 65 | A fork at heads holding a change sent to nobody (a version written without votes, say) | A node holding the old document takes the fork only where it holds the heads' history, each change judged | sim | | 66 | A node away while the others switch | It syncs the rest of the base from a peer that keeps the old epoch, builds, and switches; it stays where none keeps it | sim | +| 67 | A key its party dropped writes, from a history before the drop, ahead of what the party signed | Counts no more, and takes out nothing the party signed again after the drop | unit | ## Roads not taken |
