aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 03:11:22 +0000
committertv <tv@krebsco.de>2026-11-16 03:11:22 +0000
commita26ae757f6ec7c86940233e2e4492e11bf443012 (patch)
tree1aee52c49230a43eeabb88a0f4be817206534ea1 /docs/federation.md
parenta2738ee8600f36ef4ab924cd0e69cd74a484d359 (diff)
federation: a snapshot leaves out the entries of nodes no longer listed
Nothing is deleted within an epoch, and a snapshot left out only what is or names a version before the current one, which no member entry does: the entry of every node its party stopped listing, every node reinstalled under a new ID among them, stayed for good. A snapshot leaves out the entry of a node its party doesn't list at the base; a node listed again registers again. A fork's genesis holds no member entries already.
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md12
1 files changed, 8 insertions, 4 deletions
diff --git a/docs/federation.md b/docs/federation.md
index d7ee8be..6c7d9ba 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -350,7 +350,8 @@ whole. These count no more, and nothing else does:
Nothing is deleted within an epoch but by a party at its own place, writing `null`.
Automerge keeps every operation, so a deletion shrinks nothing: only a remake shrinks
the document. What counts no more stays until a remake's snapshot or a fork's genesis
-leaves it out, where it is or names a version before the one current there (Remakes).
+leaves it out, where it is or names a version before the one current there, or is a
+member entry (Remakes).
Until then, a place given back to its party, or a key added back, shows what the party
signed before, until the party writes there again.
@@ -462,9 +463,11 @@ snapshot is a function of its base. What a federated node asks of a remake:
never rejoins an epoch it refused. A remake's decision is its coordinator's alone, and
how long a node keeps the old document is its own setting, not the remake's.
* **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, and a
- party's `null` naming a version before it: nothing naming an earlier version can be
- written in the new epoch, and an empty place reads as one holding `null` does.
+ 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
@@ -620,6 +623,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang
| 61 | A version written again late, at a history from before the next, by a member that was away | Taken: it is one every node took | unit |
| 62 | A proposal whose text doesn't hash to its place | Refused | unit |
| 63 | An honest member writes a version valid where it is written, on the side a node doesn't read | Refused, and reported apart; its committer isn't refused as a whole | unit |
+| 64 | Nodes reinstalled under new IDs, their old entries left behind | Each counts no more, and the next snapshot leaves it out | unit |
## Roads not taken