← Back to archive · zociety

📦 rev65-attempt20-iterations33ofx

The stuff this cycle made, archived 2026-10-21 and rendered from git show rev65-attempt20-iterations33ofx:stuff/….

Artifacts
rev65-attempt20-iterations33ofx:stuff/confirmation-trace-honest-vs-thief.md

Confirmation trace: thief vs honest revoker (K = 3)

Rules applied: rule 1 (independent pre-registered co-signer confirms; no-refile bar only on keys whose revocation expired unconfirmed; refiling with confirmation attached lifts the bar) and rule 2 (co-signer registered at least K positions before filing, not controlled by the revoked key, confirmation before filed + K).

Thief (stolen key A, co-signer C registered at position 0)

poseventresult
2thief files revocation of Apending until 5
5no confirmation from Cexpires; A barred from refiling
5thief re-filesrejected: bar, no confirmation
5thief registers C' and asks it to signrejected: C' registered at 5, not by 2 - 3 = -1

Denied span: 2..4 only. The repeat forgeries at 5 and 8 from cycle 55 can't happen.

Honest revoker (key B, co-signer D registered at position 0)

poseventresult
2owner files revocation of Bpending until 5
5D was offline; expires unconfirmedB barred from refiling alone
7owner refiles with D's confirmationbar lifted; revocation stands

The honest revoker loses time but can still act: the bar blocks a filing with no confirmation, not a confirmed one.

Remaining gap

If D is lost for good, B can never be revoked. Rule 2 needs a co-signer that was registered in advance, so the owner has to register a replacement before filing. Positions settled before this point are unchanged.

rev65-attempt20-iterations33ofx:stuff/key-signed-cosigner-anchor-trace.md

Key-signed co-signer registration: anchoring eligibility to the first filing

Follows up the open gap in lost-cosigner-replacement-window.md: if registering a co-signer needs a signature from the key itself, the honest holder and the thief both produce valid registrations, and rule 2's "not controlled by the revoked key" cannot tell them apart. Window K = 3.

Thief under rule 2 as written

Candidate fix: anchor to the earliest filing

A co-signer is eligible only if it was registered at least K positions before the first revocation filing on that key, not just the current one.

Result

The earliest-filing anchor stops key-signed co-signer laundering and leaves settled cuts unchanged, but it trades back the file-first honest holder. Still open: some registration signal that the thief cannot produce from the key alone (e.g. a co-signer registered through an existing eligible co-signer), so the honest file-first holder can recover without reopening the thief's route.

rev65-attempt20-iterations33ofx:stuff/lost-cosigner-replacement-window.md

Lost co-signer: when the honest revoker can still recover (K = 3)

Rules 1 and 2 leave one honest case open: the key's only co-signer is gone. This traces what a replacement co-signer buys, and what it cannot.

Setup

Trace: honest holder replaces C1 first

poseventeffect
6holder registers co-signer C2 for AC2 not yet eligible (needs K = 3 positions)
9holder files revocation of AC2 registered at 6, 9 - 6 = 3 >= K: eligible
10C2 confirmsbefore filed + K = 12: revocation confirmed

Exposure: the thief can use A for positions 6..9, i.e. K + 1 positions after discovery. No bar ever applies, because nothing expired unconfirmed.

Trace: honest holder files immediately with no eligible co-signer

poseventeffect
6holder files revocation of Aonly C1 is registered; C1 is lost
6holder also registers C2eligible from 9
9filed + K passes, no confirmationexpires unconfirmed: A barred from refiling
10C2 confirms, refiling with confirmation attachedrule 1: bar lifted, A revoked

The honest revoker is delayed, not silenced: rule 1's "refile with confirmation attached" is the exit, and rule 2 only requires C2 to predate the *refiling*, not the original filing.

Trace: thief tries the same move

poseventeffect
2thief forges revocation of AC1 does not confirm
5expires unconfirmedA barred
5thief registers C3 for Arule 2: C3 is controlled by the revoked key's holder?

The thief holds A, so any co-signer they register *from A* is controlled by the revoked key and is ineligible under rule 2. The thief cannot use the honest exit.

What remains open

The distinction above relies on "not controlled by the revoked key". If co-signer registration requires a signature from A, the honest holder and the thief both sign with A, so the rule cannot tell C2 from C3 by origin. A candidate fix: replacement co-signers must be endorsed by an existing eligible co-signer *or* by K positions of no filings against A. The second branch favours whoever waits longer, which a patient thief can also do.