diff options
| author | tv <tv@krebsco.de> | 2026-11-19 14:13:39 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 15:18:52 +0100 |
| commit | 841897b79838f97a809356471baf2f41e186cdfa (patch) | |
| tree | 6fb5e0ac21b69986c87e8d87e87806ff514b451f /src/api/events.rs | |
| parent | 27b76d5748f23a879d9fc82c725a58b514020ef9 (diff) | |
continuum-party: which places a proposal gives another writer
Rules go by first match, and `{party}` matches only the names of the
version's parties: admitting a party named as a segment of a place, or
changing the rules or their order, moves who writes the places below
it, and what their writer wrote there counts no more once the version
passes. Nothing said so: a proposal showed only its fields' changes.
`client::writers` names, of the places holding a value, those whose
writer a version changes, as `place: before -> after` (`nobody` where no
rule gives it one). `continuum-party proposals` prints them under each
proposal's changes (`who writes …`), and a fork's check does for the
fork's version (`writers` in POST /events/fork). The guides and
federation.md say so; row 72 is tested (`federation_attack_72`).
Diffstat (limited to 'src/api/events.rs')
| -rw-r--r-- | src/api/events.rs | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/api/events.rs b/src/api/events.rs index a3781c1..5182c23 100644 --- a/src/api/events.rs +++ b/src/api/events.rs @@ -400,7 +400,8 @@ async fn make_fork(State(state): State<AppState>, Json(forking): Json<Forking>) /// `POST /events/fork`: what this node finds of the fork whose root is the body's first /// line, as the file its founders start from holds it: whether it builds that root at /// its heads, and why not; what it holds that those heads lack; what the fork's version -/// changes of the one current there, a line each; and the parties whose keys the fork's +/// changes of the one current there, a line each, and the places holding a value whose +/// writer it changes; and the parties whose keys the fork's /// version gives otherwise than they had there, each with its keys there and in the fork. async fn check_fork(State(state): State<AppState>, body: Bytes) -> Response { let (root, _) = fork::read_root_file(&body); @@ -419,6 +420,7 @@ async fn check_fork(State(state): State<AppState>, body: Bytes) -> Response { "why": check.why, "lacking": ids(check.lacking), "changes": check.changes, + "writers": check.writers, "keys": keys, })) .into_response() |
