aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-15 18:48:10 +0000
committertv <tv@krebsco.de>2026-11-15 18:48:10 +0000
commit036b968712c6c4d5e467de3d1df17ffa538a23c5 (patch)
treeeb14d5690fa8dc93a6008d2aa8c6b61bf3172f8d /docs
parentfe058b3356edcad7f3d069a4e84af1bbedffada6 (diff)
remakes: links replayed in the order their changes were made
Under a strict policy, the links of the chains to signed values were ordered across places by their changes' timestamps. How a link is judged in the new epoch depends on what was replayed before it: a key added to a user's entry, a capability granted. A write signed with a key added a moment before, through a node whose clock is behind, went first, was refused and quarantined, though every node had taken it. The changes replayed (`between`) now come each after those it builds on, clocks deciding only between changes neither of which saw the other, then the lower hash; the links follow that order, and an envelope takes its time from the first change that wrote it there. remakes.md says so, and what becomes of a place where a link is refused. Without a strict policy there are no links, and nothing changes.
Diffstat (limited to 'docs')
-rw-r--r--docs/remakes.md8
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/remakes.md b/docs/remakes.md
index bc53cf2..e33955ea0 100644
--- a/docs/remakes.md
+++ b/docs/remakes.md
@@ -329,8 +329,12 @@ The swarm stays writable throughout.
chain of envelopes that leads to the one the old epoch reads: each one after what the
new epoch holds there, in order, each in a change of its own by its signer, at the
time it was made, so that each replaces the one before as every node checks. Not by
- clocks: a place is carried over only where the new epoch holds a lower `seq` there.
- Where no chain leads from what it holds, the place goes to the quarantine.
+ clocks: a place is carried over only where the new epoch holds a lower `seq` there,
+ and the links of all places in the order their changes were made, each after those it
+ builds on (one may add the key the next is signed with); clocks decide only between
+ changes neither of which saw the other. Where no chain leads from what it holds, the
+ place goes to the quarantine; where a link is refused, the place keeps the last one
+ taken, and the rest goes to the quarantine.
* **Granularity**: map entries are carried over per key. Lists and text are carried
over whole, so concurrent edits of the same list on two nodes around a remake end as
last-writer-wins.