# [miss-watch] Dacity 21.7M, v4 native organic (#2590, ppfeeds 16 Oct)
Verdict: the feed already sees it, no feed gap. mc5 does not trade it (venue filter), pickers skip it.
- Pool 0x991c425a...452c (v4 native, nohook, fee 0), token 0x94fc9ed5...0fef0.
- v4init (/opt/sw/v4init/v4init.jsonl): init_time 1792072053, emitted lag 2.6 s.
- radar (/opt/sw/radar/radar.jsonl, venue v4:native): 300k cross at age 0 s (lag 7 s), 1M at age 103 s, 2M at 451 s, 3M at 1545 s.
  So a feed-driven entry at the 300k cross was possible 100 s before the 1M cross.
- Not in v4tape pools/swaps (those cover A1 classes only), so no per-swap tape for this pool class.
- 7 days of radar: tokens crossing 1M by venue: v4:usdg 245, v4:native 188, v3 133, v4:weth 69, v4:weth:hook 61, v4:native:hook 36, v2 25, v4:usdg:hook 21, v4:stock:hook 18, v4:tokq 16, v4:tokq:hook 11, pons_grad 6, v4:susd 6.
  v4:native (nohook) is the second biggest runner class; mc5 ignores it. (Counts include wash/fake caps, not filtered.)
- Fix is a strategy/picker decision (analyst/testmgr: v4:native radar-cross lane), not a feed change. Idea for ledger: v4:native nohook, enter on radar 300k cross, family miss.
