GAVELGAVELSCAN

Changelog

Where this was wrong, and when it changed.

A product that judges how honestly other people configure their launches has no standing unless it publishes its own mistakes with the same prominence. Corrections are listed here beside features, not below them. 4 so far.

  1. CORRECTION

    The record blamed neglect for something nobody was neglecting

    This site said that most auctions never became pools because nobody made the permissionless call to migrate them. That was an inference, and it was wrong. The chain emits no event for an auction that draws no bids — it simply sits past its migration block, which looks identical to one that cleared and was left alone. Reading each initializer directly settles it: they revert until a clearing price exists. Of 510 auctions, 384 never cleared at all, and every single auction that did clear was migrated. Not one was left sitting. The record now names the two states separately, because they are two different stories about the same silence.

  2. CORRECTION

    The verdict said FLAG about almost everything, which is the same as saying nothing

    Under the first calibration 87% of the record sat below PASS, and the reason was a single check: paying an ordinary wallet was treated as a warning, when 85% of launches do exactly that. A signal that fires on five launches in six is not a signal. Findings now carry an INFO severity that is published but moves nothing, warnings are reserved for what is actually unusual — a recipient wallet with almost no history, a raise that routes less than half of itself to liquidity — and FAIL for what is structural, like a schedule that sends the money past liquidity entirely. Measured across the whole record of 462 launches the split is now 380 PASS, 72 FLAG and 10 FAIL. A verdict layer should be quiet like a smoke alarm, not loud like a car alarm.

  3. CORRECTION

    The header showed a live block number over a snapshot

    The chip in the header reported the chain's current height, which read as a promise that the record was keeping pace with it. It was not: these pages are rebuilt from a snapshot, and that snapshot can be an hour or more behind. The chip now reports the block the data was actually read at and how far behind the chain that leaves it, and turns amber once the gap is wide enough to matter.

  4. CORRECTION

    A genuine stock token was being called a likely impostor

    Currency authenticity was inferred from the token's name, so an auction priced in a real Robinhood stock token could be labelled a likely impostor purely because nothing verified the claim. The official issuer registry for chain 4663 is now consulted as fact: a registered address is verified, a name that claims the official pattern from an unregistered address is an impostor, and neither can be moved by the judge. Where the registry cannot be read at all, the answer is unknown — an unreachable registry is not evidence of forgery.

  5. COVERAGE

    The archive now covers every launch, not the ones we happened to see

    Server-side topic filtering meant the watcher only ever received the four event types it already knew about, so anything the protocol added would have been invisible while the cursor advanced past it. Filtering now happens after the fact: unknown events are archived as unknown rather than silently excluded. Rebuilding revealed 940 events that had been dropped, all of them belonging to four lifecycle events that now have decoders.

  6. CHECKS

    The judge can no longer author anything you read

    An earlier design let the model write the headline and reasons on a verdict. An adversarial review showed that a token name carrying an injection could steer that copy — the verdict stayed correct while the sentence beside it reassured the reader. The model now returns only a verdict, a subset of our own finding keys, and labels from a closed list. Every published sentence is ours.

  7. CHECKS

    Assessment labels are bounded by the facts

    The classification labels shown next to a verdict were taken from the judge without reconciliation, so a steered model could stamp 'verified official' on an unregistered currency or 'established' on a wallet with no history. Labels the facts decide are now replaced by the facts, labels the facts merely bound are coerced into the allowed set, and any disagreement with the chain is recorded and raises the manipulation flag.

Every entry here corresponds to a commit in the public repository, and every correction has a regression test so the same mistake cannot return quietly.