aboutsummaryrefslogtreecommitdiffstats
path: root/src/testrand.rs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 02:27:38 +0000
committertv <tv@krebsco.de>2026-11-16 02:27:38 +0000
commitb348f95f24ec7afb0e766c6571c7c963eb6f9c8b (patch)
tree228f5c41c4a42f03f492b879d8bef9f2cde4a128 /src/testrand.rs
parentf2861e1ff33e335f4fd49b94a75a1a7442854b30 (diff)
federation: versions a node takes, epochs it builds, values in `@`
What the design leaned on that didn't hold, and what it can do without: * A vote counts as cast wherever its version is current, so the keys an earlier version named could pass another proposal on it at a history from before the version that followed, raise its number alone, and be read by every node. A node takes a version only where it changes the one it reads; another it refuses, reports, and leaves to its operator. Two that change one are written only where keys voted twice: each node keeps the one it took, and the parties fork. The lower hash goes. * A node left its epoch on its peers' word (catching up), or for a remake at any base its coordinator named. It leaves an epoch only for a compaction it built itself, from a base it holds, a member there, the version it reads written there; the decision is the coordinator's alone, and how long the old document is kept the node's own setting. The check that a remake reads as the old document goes, with remakes of other kinds. * Housekeeping within an epoch shrank nothing (Automerge keeps every operation), and an emptied place read whatever anyone put back. Nothing is deleted in an epoch but by a party's own `null`; a snapshot and a fork's genesis leave out what counts no more and is or names a version before the current one. Rule 7, putting back and the replay's deletions go. * A key could hold an envelope and a map at once. A place's value is in its `@` key, which never holds a map, so no key is both; `**` stays. * A key set dropping the key that signed it counted no more by the rule for values. Sets are checked only where written, and signed, as node lists are, only by keys the version names, so a party revokes a key of its set by itself. What a version sets for a party (keys, and now node lists, as the first version and a fork's do, so that a group without listed nodes can fork) is one envelope, `prev` empty, `seq` 0. * The federation's envelope is `cv3.`, so that swarms that aren't federated read nothing new; neighbours are kept partly by party; the krebs users who will vote are the parties, the others in a group. * The share is two thirds, the field gone; `went/` goes. And what two builders would decide apart: a version's bytes its JCS encoding, validity asked where it is written as a version, the rule grammar's edges, keys holding `/`, the double-vote report against a vote committed again elsewhere, one list of the protocol data a federated swarm takes, the Automerge version a rule, releases working together, the swarm key, a yes that can't be taken back, what stage 1 covers and that its swarms are for tests.
Diffstat (limited to 'src/testrand.rs')
0 files changed, 0 insertions, 0 deletions