| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After a close vote, one key voting twice passes a rival version at a
history from before the version that followed, the votes cast before
counting with its own, any time until a checkpoint above that version:
nodes that took the version refuse it, but one lagging behind, or
joining from the root, may take it. A node voting by itself proposed a
checkpoint after a version only where its operator set
`--store-propose-versions`; now it does unless told otherwise (1 unless
set; 0 never so). Versions that change more than moving to a checkpoint
are rare, so the cost is a checkpoint each.
A default set, store-propose-versions no longer asks for store-vote-key,
as store-held-for and store-back-after don't.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
`--store-propose-versions` counted the versions since the checkpoint's
version, the one current at its heads. The version that moved the store
there is written after its heads, so it counted: with 1, a node proposed
a checkpoint again as soon as it backed one (`--store-back-after` after
the move), and the next one, and so on, every ten minutes for good.
It counts the versions written since that change more than moving to a
checkpoint now (`State::changed_since_checkpoint`): with 1, one
checkpoint after every other version, and none after a checkpoint. The
test goes on past the move.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The votes cast before count at a history from before too: a proposal that died, or a
rival, needs there only the votes it lacked, and after a close vote one key voting twice
is enough, at any time until a checkpoint above the version that followed. Nodes that
took that version refuse it; one lagging behind, or joining from the root, may take it.
`federation.md` said it took the keys of two thirds of the parties.
A node voting by itself proposes a checkpoint once so many versions were written since
its store's (`--store-propose-versions`), as the design lists: with 1, after every
version, so that what keys voting twice grow beside a version ends at a checkpoint above
it. `federation.md` says how little a rival version takes, row 20 too, and the guides the
option.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A node voting by itself proposes no checkpoint beside a proposal that holds it back, as
the checkpoint would lapse it, and a follower backs none so. A proposal held one back
where someone but its proposer backed it: two parties, or one and a stolen key, kept a
junk proposal alive, and no automatic checkpoint came while it lived, ending it taking
nays from more than a third each round. And one new, its proposer alone backing it, was
lapsed at once by a checkpoint its writes brought about.
A proposal that can still pass holds back now where a third of the parties back it,
someone but its proposer among them; or where it is new, held for less than a while
(`--store-held-for`), and its proposer has none older on the version: so it is heard
before a checkpoint lapses it, once a version for each proposer. Row 67 says so, and a
test of nine parties checks it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A node following a party (`--store-follow`) handed it more than the text said:
* it copied the party's `false`: one party's nay freed bound followers, and its `true`
shown to some and its `false` to the rest passed a checkpoint at one history and made it
dead at another. It copies the `true` alone now, on any version too;
* a checkpoint lapses every other proposal: the followed party ended any proposal it
disliked by passing one. A node follows a checkpoint only where no proposal that changes
more can still pass that someone but its proposer backs;
* nothing bounded how often the store moved, so fresh events could be left out of every
checkpoint; and a node just started held nothing for a while, so the voters' rule kept
nothing. A node backs, and proposes, a checkpoint only once its store held its
checkpoint, or ran, for a while (`--store-back-after`, ten minutes unless set), by itself
or by hand.
`federation.md` says what following hands over, and row 58 what a follower on any
version copies; the guides and the example say the rest.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Anyone could propose a checkpoint's version again, by an event beside its heads. A node
voting by itself, and a party's client, built a vote on every event proposing what it
voted on, so every vote was beside the heads, and no version event written on them was
taken: the checkpoint could never move the store. And the voters' rule refused it once
that event was held for a while, as the heads left it out.
They vote on the events proposing it that are above the heads it names
(`State::proposing`), which `GET /events/counts` lists as `proposals`; where there are
none, `none` says so, the node casts nothing and the client says why. The voters' rule
leaves proposals and votes aside, as they lapse with the move.
Row 70 is tested (`federation_attack_70`).
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
Where a document names one of its own sections in parentheses ("(What
counts, 5)", "(Joining, below)"), the name links to the section by its
GitHub-style ID; paragraphs that grew past the width are wrapped anew,
links and code kept on one line each. References to another document's
sections stay as they are.
|
|
|
What a move to a checkpoint keeps and loses, a version only moving the store on and the
heads to name, a node proposing checkpoints by its operator's rules, backing only heads
that leave out nothing held for a while (which a node voting by itself checks and a
party's client doesn't), signing again after a move, and nodes that weren't there.
|