| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
What the docs left unsaid:
* A checkpoint names every event that counts, 32 bytes each, and has no
size limit, unlike an event; nothing bounds what a party writes where
its rules let it, so every node, snapshot and fork's root holds as
much as it writes. A party writing more than the others will hold is
taken out by a version, or the others fork. Row 73 says so, and the
rules guide.
* Before the first checkpoint passed, a node joins from the root and
nobody pins anything: a chain of old keys needs keys a version
replaced, and a node voting by itself proposes a checkpoint after
every version that changes more; until that passes, a joining node
takes the first of two versions it judges, as row 63 has it.
* A `true` binds; what binds nobody is said outside the votes. The
voting guide shows how parties count their support first by plain
writes, at a place a rule gives each (`intents/{party}/**`), read at
`values` in GET /events/counts.
|
| |
|
|
|
|
|
|
| |
Where a document names a section of another after linking to it
("([`store.md`](store.md), Pinned checkpoints)"), the name links to that
section too, by the id both GitHub and cgit's about filter give its
heading; paragraphs that grew past the width are wrapped anew, links and
code kept on one line each.
|
|
|
How rules match, a namespace each, zones and blocks a party holds by its name, shared
places given by rules of their own and kept apart from party names, what rules cost in
votes and size, and the krebs registry's rules as an example.
|