diff options
| author | tv <tv@krebsco.de> | 2026-11-19 03:56:57 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 05:12:15 +0100 |
| commit | efaf79e7fd55db2b9704ccefedde33346f874a1d (patch) | |
| tree | 245bf0812b7cb95b000928a2739e0ff140352818 /docs/guides/federation/checkpoints.md | |
| parent | 5611555bd31e5b05bcee6c6e4450adeffd2e820b (diff) | |
vote: a node proposes a checkpoint at the heads it holds
A node proposed a checkpoint at the heads of what it held for a while: every event
written in that while, and every one built on an event beside those heads, as one party
writing now and then on something old makes them, was beside them, and refused once the
store moved. A voter whose while was shorter backed none, one whose while was longer
backed it and lost those.
It proposes at the heads its store holds, sorted: what was written before is in their
history, and only what is written while the vote takes its course may be beside them. It
proposes none where they are more than an event may name: under a revision with merge
events, it merges them first; otherwise, what is written after does. `--store-held-for`
keeps the voters' rule and how long a new proposal holds back a checkpoint.
`federation.md`, the guides and the options say so.
Diffstat (limited to 'docs/guides/federation/checkpoints.md')
| -rw-r--r-- | docs/guides/federation/checkpoints.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/guides/federation/checkpoints.md b/docs/guides/federation/checkpoints.md index cd77e28..ad468f8 100644 --- a/docs/guides/federation/checkpoints.md +++ b/docs/guides/federation/checkpoints.md @@ -26,9 +26,9 @@ current version's hash as `changes`, and the heads as `checkpoint` ([`proposing-and-voting.md`](proposing-and-voting.md), [Writing a version](proposing-and-voting.md#writing-a-version)). The heads are events after the current checkpoint, at which the current version is current too, none in -another's history, their IDs ascending: heads a node showed (`heads` in `GET /events`) -once the version was written, and that it has held for a while since, so that every node -holds them. Propose it afterwards: the client signs the proposal on the heads its node +another's history, their IDs ascending: the heads a node shows (`heads` in `GET /events`) +as late as you can, so that what was written before is in their history. Propose it +then: the client signs the proposal on the heads its node shows then, above the ones it names, as it must be. Like any version, it lapses the proposals on the version before: propose one where @@ -37,9 +37,9 @@ nothing that can still pass is proposed on the current version. A node voting for its party by itself proposes checkpoints by its operator's rules: once it holds so many events beyond its checkpoint (`--store-propose-events`), so many versions were written since it (`--store-propose-versions`, after every version with 1), -or so long after its store moved there (`--store-propose-every`), at the heads of what it -held for a while (`--store-held-for`, ten minutes unless set), where no proposal holds it -back ([`voting-by-itself.md`](voting-by-itself.md), +or so long after its store moved there (`--store-propose-every`), at the heads it holds, +no more than an event may name (64, which it merges first under a revision with merge +events), where no proposal holds it back ([`voting-by-itself.md`](voting-by-itself.md), [Its rules](voting-by-itself.md#its-rules)); and it backs what it proposes. ## Backing one |
