diff options
| author | tv <tv@krebsco.de> | 2026-11-19 14:11:39 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 15:18:45 +0100 |
| commit | 27b76d5748f23a879d9fc82c725a58b514020ef9 (patch) | |
| tree | d0201eed80c9c4a2db3f2e6281cac51dbc126ba6 /docs/openapi.yaml | |
| parent | 8347900a553a3c4c9f9d3fc4a539fd31b41b07d3 (diff) | |
fork: a fork's check says what its version changes, rules among it
A node holding the history up to a fork's heads said whether it builds
the root, what it holds that those heads lack, and which parties' keys
the fork's version gives otherwise. A founder could change the rules, or
only their order, which says who writes where, and nobody joining was
shown it.
The check now says what the fork's version changes of the version
current at those heads, a line each as a proposal's are shown
(`client::changes`): `changes` in POST /events/fork, and
`continuum-party check` prints them. federation.md and the forking
guide say so, and that a fork's ID is compared whole: a founder trying
versions can steer its first few digits.
Diffstat (limited to 'docs/openapi.yaml')
| -rw-r--r-- | docs/openapi.yaml | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/docs/openapi.yaml b/docs/openapi.yaml index 4982cac..6cef2f2 100644 --- a/docs/openapi.yaml +++ b/docs/openapi.yaml @@ -1694,7 +1694,10 @@ paths: byte for byte, and why it builds none where it doesn't (heads it doesn't hold, a version that is no fork); what it holds that those heads lack (`lacking`: events it took that are neither among them, nor in their history, nor above - them); and the parties whose keys the fork's version gives otherwise than they + them); what the fork's version changes of the version current at those heads, a + line each as `field: before -> after`, its rules among them, `keys` and `nodes` + party by party (`changes`); and the parties whose keys the fork's version gives + otherwise than they had at those heads, each with its keys there and in the fork. A node that doesn't hold that history takes a fork's root on its operator's word, who names the fork by its ID (`--store-id`). @@ -1712,7 +1715,7 @@ paths: application/json: schema: type: object - required: [fork, builds, why, lacking, keys] + required: [fork, builds, why, lacking, changes, keys] properties: fork: type: string @@ -1725,6 +1728,10 @@ paths: type: array items: type: string + changes: + type: array + items: + type: string keys: type: object additionalProperties: |
