diff options
| author | tv <tv@krebsco.de> | 2026-11-13 17:08:00 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-13 17:08:00 +0000 |
| commit | 87bd6390687f3ae5af9588b5f7bc7be7d97bf40e (patch) | |
| tree | bcfe8f8bad1ba9d49fd0eddfb0a28d9fb9732448 /docs/trust.md | |
| parent | cd40fbc7ecc71ecf5497e1164826231378b9c4a4 (diff) | |
federation: how late a remake a node follows, a number of the policy
How late a remake its node follows was each operator's bound, by its own
clock: operators set different bounds, and nodes take a base up at
different times, so a remake shown when some honest nodes are past their
bound and some aren't splits them between two epochs, those that stayed
with their remake votes spent.
It is a number of the policy now, `remakeAge` (30 days recommended): how
long after taking its base up a node still follows a remake. The bounds
no longer differ by operator; that nodes take a base up and get the
decision at different times remains, and with it the split, said under
what is not promised and in an attack row. The bound isn't read from the
changes, and a remake past it doesn't free its votes: a deciding change
built on old dependencies always looks in time, so the remake could still
be decided beside the one its voters then voted for.
Diffstat (limited to 'docs/trust.md')
0 files changed, 0 insertions, 0 deletions
