From c61ee56ad0dad9f3c7468616d89d944eda7f5edb Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 14:44:31 +0000 Subject: docs: purges in rounds, a version's size, a thief asking, one spelling What the docs left unsaid, each with a row of the attack table: * two thirds are of the current version's parties, so taking parties out in rounds leaves fewer to decide: of nine, four alone after two rounds; those taken out fork (row 75); * a version is one event, its parties and rules with it, within 256 KiB: a federation giving each name a rule of its own holds a few thousand names (federation.md, the rules guide); * a thief holding a key a version names can ask for the party's keys to be named anew as well as the party, and the others tell them apart by other means than the key (row 76, the keys guide); * rules match spellings, so `7` and `07` are two places, which two rules may give to two parties; the application takes one spelling of each (row 77, the rules guide). --- docs/guides/federation/keys.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'docs/guides/federation/keys.md') diff --git a/docs/guides/federation/keys.md b/docs/guides/federation/keys.md index add7cb3..f21171f 100644 --- a/docs/guides/federation/keys.md +++ b/docs/guides/federation/keys.md @@ -110,7 +110,9 @@ set that party wrote count no more. to pass a version naming the party's keys anew, at once; then write the party's set and node list under it, as a list the thief wrote stays until the party writes one under the version that replaced the key. If the thief voted twice meanwhile, nodes may have - taken two versions: the parties answer that by forking. + taken two versions: the parties answer that by forking. The thief can ask as well, as + the party would, holding the same key: the other parties make sure who asks by other + means (in person, a key of the party's set the thief lacks) before passing it. ## The node key -- cgit v1.3.1