aboutsummaryrefslogtreecommitdiffstats
path: root/docs/architecture.md
Commit message (Collapse)AuthorAgeFilesLines
* store: a signed value chosen by seq is named sotv42 hours1-1/+2
| | | | | | | | Where the policy asks for signed values, a place's value is chosen by `seq`, but conflict reports still called the choice `newestWins`, and the code and the architecture still said "newest" of what a read shows. A report names it `highestSeq`; the rest says "the one a read shows".
* swarm: no SIGNATUREStv8 days1-2/+1
| | | | | | | | | | | | | | Signatures sent on their own (SIGNATURES, every second, to each peer not sent them yet) flooded every link: a signature made after its change left, or one that came with changes, went to every neighbour, whether or not it got the change along with its signature elsewhere. With every change of a node signed as it leaves (1217) and signatures going where their changes go (1218), none is left for them to carry: the message, its task and its traffic counter go (wire version 46). Signatures waiting for their changes are offered as before when sync messages bring them, and the changes waiting for signatures judged again with the next batch.
* swarm: changes taken unjudged, dropped (REFUSALS)tv10 days1-1/+1
| | | | | | | | | A node refusing changes a peer brought tells it which broke a rule; the peer judges them itself, and if its rules refuse them too, drops them with all built on them (its document forked without them, a fresh actor), quarantining its own writes among them. Wire version 42. Auth plan M6 (rejoin on taint).
* signatures: on their own (SIGNATURES)tv10 days1-1/+2
| | | | | | | Signatures no sync message took go on their own within a second, to each peer not sent them yet (wire version bumped). Auth plan M5.
* dashboard: without LINKS; LINKS removedtv10 days1-3/+1
| | | | | | | | | The dashboard reads every member's links from the members themselves; LINKS and LINKS_REPLY, swarm::links and their wire tags go (wire version bumped). Nodes the browser can't reach are drawn from what the reachable ones measure. Auth plan M3.
* indirect probestv11 days1-1/+1
|
* slow round back offtv13 days1-1/+2
|
* announcements answered when lackingtv13 days1-1/+1
| | | | | | | A neighbour now answers an announcement only if it lacks some of the announced heads. Heads that merely differ are no longer enough, since they do while writes go on. The check reads the document, so it runs off the message consumer, as the pull check already does.
* update architecture doctv2026-11-031-4/+7
|
* announcements answered only if heads differtv2026-11-031-1/+1
|
* always announce new headstv2026-11-031-2/+2
|
* swarm: relay links messagestv2026-11-021-1/+1
|
* swarm: announce to whom writers can't reachtv2026-11-021-1/+2
|
* add documentationtv2026-11-021-0/+306