From 59d8d6f9c4f539ac9392872026d99a93f66102ee Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 14:05:19 +0000 Subject: federation.md: a client builds on the heads it holds, a proposal or not federation.md said a client writing once a checkpoint is proposed builds only on what is above its heads. No client does: a party's client builds on the heads its node shows, and a node voting by itself on its own, whatever is proposed. Doing so would let any proposal, which costs one signature and binds nobody, steer where honest clients build: heads that never pass, or two proposals beside each other that can't both be obeyed. A proposer names the heads it holds as it proposes, so what is written after is above them unless built on an event beside them: written as it proposed, or on old history; the move refuses that, and its party's client signs it again. --- docs/federation.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'docs/federation.md') diff --git a/docs/federation.md b/docs/federation.md index 615bc05..e8eea8c 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -500,10 +500,11 @@ a version behind it shows only in the votes kept outside the store: a client kee own votes and the nays that freed it, not another party's two, so where keys voted twice, whoever saw it keeps the votes naming the party (`GET /events/{id}`) before a checkpoint leaves them out; and what isn't above its heads, which its party signs again. Few are: the -heads are those its proposer held as it proposed, no voter backs heads that leave out what -it held for a while, nodes build on them while the vote takes its course, a client writing -once a checkpoint is proposed builds only on what is above its heads, and a party's client -signs again what a move refused. +heads are those its proposer held as it proposed, and no voter backs heads that leave out +what it held for a while. What is written while the vote takes its course builds on the +heads its writer holds, a proposal or not, and so is above the checkpoint's heads unless +one of those is beside them: written as the proposer proposed, or built on old history. A +party's client signs again what a move refused. **Joining.** Once a checkpoint passed, a node joins from a checkpoint its operator pins, not from the root ([`store.md`](store.md), -- cgit v1.3.1