aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation-tests.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 20:14:00 +0000
committertv <tv@krebsco.de>2026-11-18 21:18:01 +0100
commit5d26bfd64ee01ad921daf56005641518d398cb4b (patch)
tree2db60a8fa55718a92e1ec480b567e0ba10915b67 /docs/federation-tests.md
parent7404dcef34dbad11a5ac2a6b8a27836b01c82635 (diff)
model: stops at a version it doesn't read
The model stops where `federation.md` says a node does: at a version event whose proposal passed at its history, isn't a version as this continuum reads it, and changes the version the model reads, it takes and refuses nothing more (`Verdict::Stopped`); beside that version, such an event is refused, as the node refuses it of its own. The property checking the store against the model runs on histories where parties propose such versions too (a field this continuum doesn't know): written in order, events come after what they build on, so both must stop at the same event, having taken the same before it, the adversary's two versions changing one among them. A check that some history stopped keeps the property from passing vacuously.
Diffstat (limited to 'docs/federation-tests.md')
-rw-r--r--docs/federation-tests.md11
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/federation-tests.md b/docs/federation-tests.md
index dfa9ca0..d902c36 100644
--- a/docs/federation-tests.md
+++ b/docs/federation-tests.md
@@ -42,10 +42,10 @@ to: a stage is done when its tests are.
members). It prints as the builder calls that make it, so a failure found by
generating pastes in as a test.
* **The model.** A second fold, written from `federation.md` as plainly as it can be: it
- reads every history by adding all of its events anew, keeps no state, makes no
- checkpoint. It is slow and short, and it is what the store is checked against: both
- given the same events in the same order must give the same verdicts and the same
- state.
+ reads every history by adding all of its events anew, keeps no state but whether it
+ stopped, makes no checkpoint. It is slow and short, and it is what the store is
+ checked against: both given the same events in the same order must give the same
+ verdicts and the same state.
## The fold and the store, by example
@@ -67,7 +67,8 @@ every order of every history small enough (up to some 8 events, every order that
each after its dependencies), and for seeded histories and orders beyond that.
1. **Order.** The same events give the same state, in every order, on every node.
-2. **History.** Judging at a history gives what the model gives.
+2. **History.** Judging at a history gives what the model gives; where parties propose
+ versions this continuum doesn't read, both stop at the same event.
3. **Refusal.** What is refused is refused with everything built on it.
4. **What counts.** Every value that counts is signed by a key among its party's keys,
at a place the current version gives its party.