aboutsummaryrefslogtreecommitdiffstats
path: root/docs/store.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 17:19:17 +0000
committertv <tv@krebsco.de>2026-11-16 18:30:09 +0100
commit627795d72fedf19725c0d521788260dc63c137eb (patch)
treed1fb382fa2aedddb8963911b946aef93a9c7ca3b /docs/store.md
parent9bc4f99c179eb5c015de2da337ef426c349c72bb (diff)
store: a fork's later change ends once its events reach 1 MiB
An event went into the change being filled unless it would take the events there past 1 MiB: whether a change was full hung on the next event. A node taking the root on its operator's word couldn't tell a change cut short, sent first, from the one every node builds, and by then held a change of that writer and number. Events now go into a change until their bytes there reach 1 MiB, and the next event begins the next change: each change is judged whole by itself.
Diffstat (limited to 'docs/store.md')
-rw-r--r--docs/store.md9
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/store.md b/docs/store.md
index 5a1a9bc..d554a7a 100644
--- a/docs/store.md
+++ b/docs/store.md
@@ -220,10 +220,11 @@ ID, as bytes; each making the maps on its way as continuum writes a path
bytes of the root's ID, time 0, no message. So one root makes one swarm, and a node
joining builds the genesis change and checks it. A fork's genesis change holds its root
alone; the events the root keeps follow in changes of the same writer, built the same
-way and filled in the order of their IDs: an event goes into the change being filled,
-unless its bytes would take the events there past 1 MiB, and then it begins the next.
-Continuum reads the policy as one asking for signed changes, as a strict one does, and
-nothing else of a strict policy: the document holds no values but events.
+way and filled in the order of their IDs: events go into a change until their bytes
+there reach 1 MiB, and the next event begins the next change, so that whether a change
+is whole is a question of that change alone. Continuum reads the policy as one asking
+for signed changes, as a strict one does, and nothing else of a strict policy: the
+document holds no values but events.
### What a change writes