diff options
| author | tv <tv@krebsco.de> | 2026-11-13 04:58:11 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-13 04:58:11 +0000 |
| commit | 72a769bf3f53fd78206c2948992dd12b18c617f7 (patch) | |
| tree | eee0ea83c8f0ee4572a79e09b4b1c85be0658747 /src/access/policy.rs | |
| parent | ecd2fa64cc4ad4d83dce0b623694d6e12ab58f3a (diff) | |
federation: every base taken up, writers for one user, cuts as unvouches
Remakes. A node took up the first base it saw and no other, beside votes
that name their base and are never released: two remakes proposed at once,
or a base handed first to nodes back from away, split the nodes, and a voter
whose nodes took one base up could vote for no other, ending the epoch's
remakes with nobody malicious. A node now takes up every base that passes,
one record a proposal; records count toward taking a base up however old
without votes, and a remake's record is judged without them (as written, a
record needed votes in its history that come only after it). Clients offer
a vote only for a base whose records count for more than two thirds of the
voters, showing the other remakes under way. The votes alone keep two bases
from both being decided. What votes never released cost is said under what
is not promised: voters who split end the epoch's remakes, and whoever
holds a hanging remake's last record chooses its day; an operator bounds
how late a remake its node follows, and refuses a later one by staying. A
remake's vote runs while the epoch lasts, and the voters don't end it by a
later proposal; said where every vote was said to.
Writers. A node carrying for several users counted its writers for each,
so one user past its limit put off every node that carries for it, for all
their users. A node's writers count for one user now: the first that named
it, as its own changes show.
Names.
- A creation or vouch cut off stops counting as its signer's unvouch would,
from where the cut was set: a user only its creator vouched for is out
from there, its names waiting, final ones too, until it is gone or a vouch
comes. Before, everything it signed stopped counting at once.
- A root releases its own `create` for a user the root change holds: two
roots answering at once contest, and nothing ended it.
- A `create` is refused where a user's claim of its own name holds the name,
and a user has one such claim at a time.
- A root's witness outside a claim's history makes two claims contest only
where it had the other count through its own witness of an unvouch, as
meant: a limit lowered and raised again leaves sight to decide.
- What comes back over a later claim is said for a holder's own release,
limit or cut too.
Attacks: two remakes proposed at once, a remake held by its last record, a
node carrying for a user past its writers, a creator cutting off a user
only it vouched for, a crafted first change of a writer in a batch, a user's
own name claimed again; row 124 with what transactions never write and the
tests that show it. A limit lowered and raised again moves to the stage of
decisions, a witness after an unvouch to unvouching. What was checked: the
committer is named from a change's own history.
Diffstat (limited to 'src/access/policy.rs')
0 files changed, 0 insertions, 0 deletions
