aboutsummaryrefslogtreecommitdiffstats
path: root/docs/openapi.yaml
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 01:48:57 +0000
committertv <tv@krebsco.de>2026-11-19 03:18:59 +0100
commit31d41eb1c902c907a5c6e5608510f96c4b1bc864 (patch)
tree5a1a38166c6b22312b4d1eb02adc5dc5f12bce95 /docs/openapi.yaml
parent03744437a5ffc36fbb5e973a0ddfd6b91945b212 (diff)
store: a new event builds on as many heads as an event may name
A party's client builds on the heads its node shows (`GET /events`), and a node on its own heads; an event names at most 64 dependencies. With more heads than that, where many write at once and nothing merges, every event built on them was none. `Store::building_on` gives the heads, as many as an event may name (`Fold::DEPENDENCIES`, the federation's 64), the earliest taken first, so that what is written merges what stayed apart the longest; `GET /events` shows those, and a node voting by itself builds on them.
Diffstat (limited to 'docs/openapi.yaml')
-rw-r--r--docs/openapi.yaml17
1 files changed, 9 insertions, 8 deletions
diff --git a/docs/openapi.yaml b/docs/openapi.yaml
index 349f943..5c90037 100644
--- a/docs/openapi.yaml
+++ b/docs/openapi.yaml
@@ -1417,14 +1417,15 @@ paths:
tags: [Events]
summary: The store
description: |
- The store's ID (its root's), its checkpoint's ID, its heads (what a new event
- builds on) and how many events it took after its checkpoint, as this node reads
- it now; the event it stopped at, if any (`stopped`: a version event writing a
- version that passed, which this continuum doesn't read), why, and how many
- events it holds back since, that one among them, taking nothing and refusing
- nothing until upgraded or told to drop it (`/admin/events/drop`); the party this
- node is of (`party`, `--store-party`), and whether it votes for it by itself
- (`votesByItself`), and so casts votes by hand (`POST /admin/events/vote`).
+ The store's ID (its root's), its checkpoint's ID, its heads, as many as an event
+ may name (64), the earliest taken first (what a new event builds on), and how many
+ events it took after its checkpoint, as this node reads it now; the event it
+ stopped at, if any (`stopped`: a version event writing a version that passed,
+ which this continuum doesn't read), why, and how many events it holds back since,
+ that one among them, taking nothing and refusing nothing until upgraded or told to
+ drop it (`/admin/events/drop`); the party this node is of (`party`,
+ `--store-party`), and whether it votes for it by itself (`votesByItself`), and so
+ casts votes by hand (`POST /admin/events/vote`).
responses:
'200':
description: The store.