Repository navigation
Account: tombstones never shrink #2865
Description
Follow-up from #2843 (account linking).
Since #2843, every revoke on the PC (Revoke, Revoke all, a reset relay identity) and every account remove leaves a tombstone in account-tombstones.json, on PCs in no account too. Only a pairing on the PC itself removes one, so the file only grows. As a side effect, pairing a revoked key again with a code started through the relay is refused (tombstoned), which was allowed before.
Expected: bound the file: for example, drop local-revoke tombstones on a PC in no account, or expire tombstones whose key has had no record for a long time. Keep account removals for as long as a replayed add could still arrive (the service keeps mailbox records 30 days).
Activity
fix(account): keep no tombstones on a PC in no account (#2928)
devswha commentedon Nov 5, 2026
Fixed by #2928 (re-pair after a local revoke). Decision on bounding tombstone growth: keep revoke tombstones unbounded. Any cap lets a long-ago revoked key come back through a signed add (reproduced), and the cost is about 200 bytes per revoked key.