aboutsummaryrefslogtreecommitdiffstats
path: root/core/module-save.h
diff options
context:
space:
mode:
authoreunhhu <[email protected]>2026-09-29 16:55:04 +0100
committereunhhu <[email protected]>2026-09-29 16:55:04 +0100
commitc494ec7a37ff4863d420b4a9ccbe1df93e88de2d (patch)
tree5d0ef99f9368fdabfb48c34e322d881010a06dbc /core/module-save.h
parent2a9960f086eeccf2ee58decc11b6d3f2de13699e (diff)
downloadpure-c494ec7a37ff4863d420b4a9ccbe1df93e88de2d.tar.gz
pure-c494ec7a37ff4863d420b4a9ccbe1df93e88de2d.zip
Remember the epoch of each of a peer's runs that send, not one
A receiver's memo kept one run's epoch a peer. A node whose outputs send to this one sends in a run each, so after the receiver started again (or let the peer rest) all runs but the last accepted were told LOST and began their epochs again: records under the static keys for a round trip, and an X25519 each. Now a run whose peer's place holds another run still sending keeps its epoch beside, in one of two of 1,024 places its peer and run find (160 KiB at the file's head: the memo is PLM3, and a PLM2 one is begun again). A run's place beside goes once its peer's place has it, so an epoch's secrets stay only until the next one's are. test-link's three outputs of one node, each in epoch 1, go on after the receiver starts again: no LOST, no X25519 (before: two LOSTs, an accept). 012 says so.
Diffstat (limited to 'core/module-save.h')
0 files changed, 0 insertions, 0 deletions