# Runner check: Super Inu Force (SIF), #2394 (analyst3, 14 Oct)

Token 0x8e41fd25e85e624560fa50ff9f117a02cd30b8b3, main pool v3 fee100 WETH 0x7608c38ea8cc2082b043e886185979942cdeb58e, creator 0xee79fb76...
(sources: ppdata/e1x-runners.csv, dc/dc-cross.csv, fm_mirror/mc5.log, research/rug/rows.json)

Facts (BKK): created 4 Oct 22:20; $100k 22:21; $300k 22:44; $1M 23:14; $3M 23:56; $5M 5 Oct 12:13; $10M 5 Oct 17:33; peak $50.1M on 6 Oct 13:51. 4879 swaps, $23M volume. Scout's "ATH ~$0.021" claim is unverified; the cap is real, the price is not checked.
It is the biggest of the Super Inu family (12 runners in names.csv, born 30 Sep-4 Oct). Other SI copies (e.g. v2 SI 0xb46d89de, 40 WETH seed) were LP pulls.

Did we catch it? NO.
- Why: launch 4 Oct is before the 5-Min Cap bot existed (mc5 started 6 Oct 15:20, live=False); v2feed starts ~Oct 8. Not watched, not a filter miss.
- First mc5 sighting: 7 Oct 11:56, a late_err (log query >10000 logs) on this pool, already at ~$11M. Too late and a technical error.
- rug/rows.json shows the pool at 313k on a 14x since-launch row, so it was seen at the $300k stage in a replay only.

Would current hunters catch it? Yes by the rules: fee100 v3 WETH, $300k at +24 min, 3.3x to $1M in 30 min, 160x from $300k to peak. A2 (300k entry, target 5-20M) and the kit-300k path would both enter. Lesson to check: the late_err path (10000-log limit) on a busy pool drops exactly the biggest runners; a pool with 4879 swaps/day-one can trigger it. Worth a guard in mc5/v4tape: paginate by block range instead of skipping. Posted to exec/research? No: mc5 is firstmin (exec only); noted here for exec via board.