diff options
| author | tv <tv@krebsco.de> | 2026-11-16 21:30:24 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 23:04:45 +0100 |
| commit | 9fa28bb06692cd3e9d06b678d3dfe2595d328a5f (patch) | |
| tree | a4e2959a984f0bd0d416042b9d93e7f2971122aa /src/state/mod.rs | |
| parent | d46368d5ba8d7a12e657b5f293830b6c0d8dce00 (diff) | |
api: a swarm holding a store at a node's API
Behind the `federation` feature, a node of a swarm holding a store has, at its API
(`docs/store.md`, Members; `docs/openapi.yaml`, Events):
* `GET /events`: its store's ID, its checkpoint's, its heads, and how many events it took
after its checkpoint;
* `POST /events`: an event put, whoever signed it, offered to the store and written into
the document at its ID unless the store refuses it (`422`, with why): taken, held, or
waiting for what it builds on;
* `GET /events/{id}`: an event the store holds, or its checkpoint, as its bytes;
* `GET /events/counts`: what counts as the store reads now: the current version, each
party's keys and nodes, the values at places, the members;
* `GET /events/refused`: what the store refused, its own refusals apart, its operator's
drops, and the rest with why;
* `POST /admin/events/drop` and `/admin/events/allow`: its operator has it drop what it
took, and take it back.
The events' endpoints are anyone's this node lets in, as the store's are; dropping and
taking back need `write` on `_continuum`, as what operators do. While a node holds no
store, they answer `404`.
Diffstat (limited to 'src/state/mod.rs')
0 files changed, 0 insertions, 0 deletions
