diff options
| author | tv <tv@krebsco.de> | 2026-11-16 19:44:37 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 21:25:59 +0100 |
| commit | 0ba4c7363cfa2a9963ecd6a06392ea5c4dac3ad1 (patch) | |
| tree | fa40cfbfda010601eff9f9db148c5aa793aca0b2 /src/remake/coordinator.rs | |
| parent | 3fccc4f6859cf0b4d93e7d166142e1ab9255723f (diff) | |
node: a swarm holding a store, started from its root or joined by its ID
Behind the `federation` feature, two options:
* `--store-root PATH` starts a swarm holding a store, or goes on with one, from the
store's root, as bytes in the file, which the federation must take as a root. With no
document to start on, the node builds the genesis change from it, as every node given
the root does, and is ready at once; a document to start on must be of the root's
swarm.
* `--store-id ID` joins one through seeds by its ID, the root's SHA-256 in hex. An empty
document of the first epoch takes as its root only that store's genesis change, built
again from the root it holds (`document::events::is_genesis`), whatever peers name:
the root pin doesn't wait for seeds, nor is disputed.
Either names the swarm the node joins, which a state file must remember too, and can't
be combined with the other, nor with what makes a new swarm's first change (`--genesis`,
`--bootstrap-users`, `--bootstrap-keys`, `--bootstrap-policy`, `--remake`,
`--genesis-root`). The root is read as a file of its own kind (`store`), counted among
the node's files.
Diffstat (limited to 'src/remake/coordinator.rs')
0 files changed, 0 insertions, 0 deletions
