summaryrefslogtreecommitdiffstats
Commit message (Expand)AuthorAgeFilesLines
...
* access: what a node of a swarm holding a store takes leaves its events soundtv3 days1-0/+143
* federation: a store read from its document holds what one given the events al...tv3 days1-28/+83
* store: a test per attack row marked unittv3 days5-46/+355
* docs: votes a node casts by itself are builttv3 days1-4/+6
* continuum-party: a vote through the node that votes for the partytv3 days1-2/+31
* api: a vote by hand, through the node that votes for its partytv3 days2-22/+73
* node: votes it casts by itself, for its partytv3 days4-7/+394
* federation: what a node voting by itself decidestv3 days2-0/+514
* store: what heads leave outtv3 days1-0/+41
* docs: what of the federation is builttv3 days2-10/+15
* continuum-party: a party's client of a federationtv3 days5-3/+482
* federation: what a party's client decides bytv3 days2-0/+639
* api: what the store refused, by kindtv3 days2-4/+31
* api: what counts names the proposals on the current version, and their votestv3 days3-3/+80
* federation: events made, as a party's client makes themtv3 days2-48/+87
* continuum is a librarytv3 days5-506/+518
* docs: the store at a node's API is builttv3 days1-10/+12
* api: a swarm holding a store at a node's APItv3 days4-1/+510
* federation: events offered to a node's store, and its operator's dropstv3 days2-2/+84
* docs: members by the fold are builttv3 days1-10/+12
* api: in a swarm holding a store, a node takes no token another issuedtv3 days3-2/+50
* topology: neighbours among the members of a node's own party, and of parties ...tv3 days5-1/+105
* topology: in a swarm holding a store, neighbours among its memberstv3 days1-0/+25
* peer: in a swarm holding a store, its members onlytv3 days5-0/+94
* handshake: the party its sender is oftv3 days4-3/+33
* federation: the members a node's store namestv3 days1-2/+34
* members: a node's entry names its partytv3 days1-1/+42
* node: a swarm holding a store has no swarm key, nor protocol writerstv3 days1-0/+24
* node: the party a node of a swarm holding a store is oftv3 days4-17/+95
* access: a put at an event's key held already, judged as made by handtv3 days2-18/+18
* docs: what of the store on Automerge is builttv3 days1-9/+14
* federation: a pinned checkpoint, found in the documenttv3 days4-13/+160
* store: the checkpoint at heads a store holds, as it builds one moving theretv3 days1-10/+33
* federation: events put againtv3 days2-8/+192
* federation: the store read from the documenttv3 days11-4/+425
* store: a store read anew refuses what its node refused of its owntv3 days1-0/+54
* node: a swarm holding a store, started from its root or joined by its IDtv3 days10-4/+326
* access: what a change of a swarm holding a store writestv3 days5-0/+311
* access: the policy of a swarm holding a storetv3 days2-16/+113
* document: a store swarm's genesis change, built byte for byte from its roottv3 days3-0/+181
* store: a fold names itselftv3 days3-0/+8
* docs: the federation's fold is builtdesigns/federation-1-stage-2tv3 days3-19/+21
* federation: fixed bytes of events, versions, roots and sizestv3 days2-0/+127
* federation: properties over generated federationstv3 days2-0/+576
* federation: the model, a second reading of the federationtv3 days2-0/+532
* federation: the JCS test asks escapes JCS doesn't write, as escapestv3 days1-2/+4
* federation: a test for each attack marked unittv3 days2-0/+1184
* federation: the federation as the store's foldtv3 days3-1/+947
* federation: events and checkpoints as bytes, and a harness that signs themtv3 days3-0/+610
* federation: versions, their rules, and the paths they matchtv3 days2-0/+539