aboutsummaryrefslogtreecommitdiffstats
path: root/src/locks.rs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-13 01:57:42 +0000
committertv <tv@krebsco.de>2026-11-13 01:57:42 +0000
commitea51966a949831b0809544d38bcefe9d540b9e93 (patch)
tree705c6d915d1f350d70eed4797997d37a237f8ee3 /src/locks.rs
parent95560fa7680c99f5c37359364b6a1413a5f9d6fc (diff)
federation: what a cut brings back, what `prev` names
The questions the design left: * A cut that takes back an unvouch brings its user in again. Its claims from before stood all along; what it signed while out comes to count later than it was signed, and gives way to what was claimed in sight of it. Gone stays gone. * A creation taken back by a cut is taken back as a vouch and as the claim of the user's name, not as the user: a vouch names a user by its ID, so with another vouch the user stays in, keys and claims, without a name. * `prev` names the value that shows where the envelope is signed; where several count there, any one of them, and the write replaces them all. * A carry record needs telling from no other change: it witnesses by what it names. A remake's proposal isn't carried over.
Diffstat (limited to 'src/locks.rs')
0 files changed, 0 insertions, 0 deletions