aboutsummaryrefslogtreecommitdiffstats
path: root/src/federation/party.rs
Commit message (Expand)AuthorAgeFilesLines
* continuum-party status: everything but the values, in colour, and as JSONtv2 days1-323/+20
* continuum-party status: IDs and hashes wholetv2 days1-14/+5
* continuum-party: a record held against the node's votes, a wait, restoretv2 days1-5/+307
* continuum-party get: what counts, as JSON, a path at a timetv2 days1-0/+127
* continuum-party status: a key, a node, a party a line, nodes by their namestv2 days1-56/+120
* continuum-party --party: the party it reads as, without a recordtv2 days1-23/+93
* continuum-party: logs in as its party by its key, with no user of the nodetv2 days1-10/+74
* party: the change test without the rule the harness gives alreadytv2 days1-5/+2
* continuum-party keys: files of keys tootv2 days1-19/+17
* continuum-party found: a federation's first version from its partiestv2 days1-13/+216
* continuum-party: status and valuestv2 days1-29/+268
* continuum-party: forks by what they are for, by a proposal, at the node's headstv2 days1-18/+223
* continuum-party: propose admit, remove, give, take, keys, nodes, checkpoint, ...tv2 days1-34/+519
* continuum-party: show, a proposal in words before a votetv2 days1-56/+167
* continuum-party: a directory for each federation, the only one used unaskedtv2 days1-2/+168
* continuum-party: hashes named by their prefixes, the shortest markedtv2 days1-7/+58
* vote: a second `true` builds on the nays that freed its partytv3 days1-3/+17
* continuum-party: which places a proposal gives another writertv3 days1-0/+15
* fork: a fork's check says what its version changes, rules among ittv3 days1-0/+12
* release: --version says what decides which builds work togethertv3 days1-0/+2
* federation: which nodes know a revision, in counts and before a `true`tv3 days1-8/+34
* federation: continuum-party judge, a store's verdicts in a format releases keeptv3 days1-0/+12
* federation: revisions shown, named, and moved to by handtv3 days1-9/+108
* federation: merge events, the first revisiontv3 days1-1/+1
* continuum-party: warns before a true that only every nay left endstv3 days1-0/+14
* federation: votes on the events proposing a checkpoint above its headstv3 days1-2/+8
* events: why no party's client backs a proposaltv3 days1-0/+3
* continuum-party: proposes only what a party may backtv4 days1-8/+5
* continuum-party keys, nodes: shown given no change, --set, --forcetv4 days1-46/+110
* continuum-party: votes and proposals checked for the key a version namestv4 days1-11/+16
* continuum-party keys, nodes: --add and --remove, and the key they needtv4 days1-18/+198
* continuum-party propose: the proposal's hash, and --yestv4 days1-6/+18
* continuum-party propose: only a version changing the current onetv4 days1-1/+8
* continuum-party next: the version after the current one, to changetv4 days1-0/+44
* continuum-party: why waiting for the ssh-agent may blockecdsatv4 days1-0/+4
* continuum-party: a key the ssh-agent holds, given itselftv4 days1-18/+105
* continuum-party: signing through an ssh-agentslopulus4 days1-14/+41
* keys: a party's key may be ecdsa-sha2-nistp256, its signature low-S onlyslopulus4 days1-1/+2
* continuum-party: options from configuration files, as the node'stv4 days1-44/+70
* continuum-party proposals: where each proposal stands, and what it changestv4 days1-0/+58
* continuum-party keys: a key set from authorized_keys lines, comments left outtv5 days1-3/+11
* client: a record begun from the store's root casts on its first versiontv5 days1-5/+25
* federation: votes build on the events proposing what they vote ontv5 days1-3/+5
* continuum-party: a federation's root, a fork's made through a node, and checkedtv5 days1-6/+110
* continuum-party: a vote through the node that votes for the partytv5 days1-2/+31
* continuum-party: a party's client of a federationtv5 days1-0/+459