diff options
| author | tv <tv@krebsco.de> | 2026-11-15 18:48:10 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-15 18:48:10 +0000 |
| commit | 036b968712c6c4d5e467de3d1df17ffa538a23c5 (patch) | |
| tree | eb14d5690fa8dc93a6008d2aa8c6b61bf3172f8d /src/transport/libp2p/errors.rs | |
| parent | fe058b3356edcad7f3d069a4e84af1bbedffada6 (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 'src/transport/libp2p/errors.rs')
0 files changed, 0 insertions, 0 deletions
