diff options
| author | tv <tv@krebsco.de> | 2026-11-18 18:49:50 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-18 20:29:41 +0100 |
| commit | c64fcc05d8c53bee99ab039bd709039afb730cdd (patch) | |
| tree | 45baad78d7b92de42283be2954fc3f9b4dd6129d /docs/guides/federation/writing-and-reading.md | |
| parent | 598366b03679eac9d04f32d9194f3ba4ba9c3da8 (diff) | |
federation: a node stops at a version it doesn't read
A version event writing a proposal passed on the version a node reads, which doesn't
read as a version there (of a later federation, using what a later continuum takes, or
none at all), the node can't judge: `Fold::stops`. The store stops at it: it takes
nothing and refuses nothing from then on, holding back whatever comes, that event first
(`Offered::Stopped`), and keeps none of it across a restart, where it stops there again.
One beside the version the node reads is refused of its own, as any other.
Its operator has it drop that event (`POST /admin/events/drop`), or one it builds on:
it is refused as dropped, or as built on what was, any version event writing that
version with it, kept in the store file; the node judges what it held back and goes on
under the version before. Allowed again, it stops there once more.
The node logs the stop and its end; `GET /events` names the event, why, and how many it
holds back (`stopped`); a put answers `stopped`, written into the document all the same;
a node voting by itself casts nothing while stopped. The test fold's eras tagged `new`
stop a store.
Row 39 is tested (`federation_attack_39`); of rows 9, 10 and 48, a node stops at the
version event.
Diffstat (limited to 'docs/guides/federation/writing-and-reading.md')
| -rw-r--r-- | docs/guides/federation/writing-and-reading.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/guides/federation/writing-and-reading.md b/docs/guides/federation/writing-and-reading.md index 3dd0578..057aad7 100644 --- a/docs/guides/federation/writing-and-reading.md +++ b/docs/guides/federation/writing-and-reading.md @@ -33,7 +33,10 @@ object, the whole event up to 256 KiB. `null` empties the place. The client signs the write with its key (`--key`), on the heads its node shows, which are what the party read; records it (`--record`), to sign it again after a move; and puts it through the node. The node answers what became of it: `taken`, `held` (taken before), -or `waiting` for an event it builds on that the node doesn't hold yet. +`waiting` for an event it builds on that the node doesn't hold yet, or `stopped`: the +node stopped at a version it doesn't read, and holds it back +([`when-things-go-wrong.md`](when-things-go-wrong.md), +[A node stopped](when-things-go-wrong.md#a-node-stopped)). A write counts while the key that signed it is among its party's keys: those of its key set, or, while it has written none, those its version names |
