aboutsummaryrefslogtreecommitdiffstats
path: root/docs
Commit message (Expand)AuthorAgeFilesLines
* model: stops at a version it doesn't readtv40 hours1-5/+6
* events: why no party's client backs a proposaltv40 hours3-10/+19
* version: say why a version is nonetv40 hours1-2/+8
* store: a stopped node leaves out none of what it holds backtv40 hours3-17/+27
* federation: a joining node takes the first of two versions, as any nodetv41 hours3-13/+17
* dashboard: the event a federation's store stopped attv41 hours2-3/+6
* federation: a node stops at a version it doesn't readtv41 hours9-45/+142
* store: a drop refuses whatever writes what a dropped event writestv43 hours3-16/+29
* docs: references to another document's section linked to ittv47 hours31-374/+437
* docs: references to a section of the same document linked to ittv47 hours11-302/+326
* continuum-party: proposes only what a party may backtv47 hours1-3/+6
* continuum-party keys, nodes: shown given no change, --set, --forcetv47 hours4-15/+18
* continuum-party: votes and proposals checked for the key a version namestv48 hours1-1/+2
* continuum-party keys, nodes: --add and --remove, and the key they needtv48 hours2-6/+15
* continuum-party propose: the proposal's hash, and --yestv48 hours2-7/+12
* continuum-party propose: only a version changing the current onetv48 hours1-2/+4
* continuum-party next: the version after the current one, to changetv2 days3-9/+14
* guides: a party writes its node list without a votetv2 days3-7/+19
* continuum-party: a key the ssh-agent holds, given itselftv2 days2-7/+14
* keys: signing through an ssh-agent tested wherever tests runtv2 days1-1/+1
* guides: which keys an ssh-agent signs a party's events withtv2 days1-4/+10
* attacks: row 62 with an ECDSA signature spelled otherwisetv2 days1-1/+1
* federation.md, guides: a change taking what was refused keeps the numbertv2 days2-0/+14
* guides: keys in an ssh-agentslopulus3 days3-6/+30
* federation.md, federation-tests.md: ecdsa-sha2-nistp256 keys, their signature...slopulus3 days2-17/+28
* dashboard: the federation, in a swarm holding a storetv3 days4-2/+52
* events: the store's summary names the node's party, and whether it votes for ittv3 days3-9/+16
* continuum-party: options from configuration files, as the node'stv3 days2-1/+24
* continuum-party proposals: where each proposal stands, and what it changestv3 days1-0/+11
* events: counts names who voted what, and whether a proposal passed or is deadtv3 days4-7/+38
* guides: designing a federation's rulestv3 days2-0/+91
* guides: building on a federated swarm's APItv3 days2-0/+91
* guides: what to watch in a federated swarmtv3 days2-0/+47
* guides: upgrades and the federation's numbertv3 days2-0/+36
* guides: remakes under a federationtv3 days2-0/+64
* guides: refusals and dropstv3 days2-0/+73
* guides: a drop's answer as the node writes ittv3 days1-1/+1
* guides: a node voting by itselftv3 days2-0/+77
* guides: a version begun from the current one leaves out its checkpointtv3 days1-1/+3
* guides: common changes to a federation's versiontv3 days2-0/+111
* guides: what a federation promisestv3 days2-0/+63
* guides: forking and following in a federationtv3 days2-0/+80
* guides: when things go wrong in a federationtv3 days2-0/+83
* guides: checkpoints in a federationtv3 days2-0/+80
* guides: a federated party's keystv3 days2-0/+87
* guides: proposing and voting in a federationtv3 days2-0/+118
* guides: writing and reading in a federationtv3 days2-0/+114
* guides: running a node of a federationtv3 days2-0/+111
* guides: getting started with a federationtv3 days2-0/+197
* federation.md, federation-tests.md: the stages end with remakesdesigns/federation-1-stage-5tv3 days2-4/+1