Casey Judice bcc02cac49 Fix HYPE Polymarket discovery: read its event container ...

Polymarket now publishes a HYPE monthly event
(what-price-will-hyperliquid-hit-in-{month}, no year suffix), so the
old strike-probe fallback was both unnecessary and mis-ranged -- its
strikes [24..52] predated HYPE roughly doubling to ~$72, so every
"above" market ($76-92) was invisible and all 8 above rows came back
NO POLY. Point HYPE at its event like every other asset and re-range
the probe fallback to the current band [52..92].

Regenerated June pairs.json: HYPE now 16/16 with a Poly leg (was 8/16),
total 110/126 (every non-ZEC row paired; ZEC stays Kalshi-only). Only
HYPE rows changed; the other 7 assets are byte-identical.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-06-01 17:21:18 -04:00

..

discover_ibkr.py

IBKR daily scanner: correct YES+NO conid schema + discover helper

2026-05-24 10:19:26 -04:00

gha_alerts.py

Static dashboard via GitHub Pages (docs/) + GHA snapshot writes

2026-05-21 22:13:47 -04:00

refresh_pairs.py

Refresh stale Polymarket slugs (BTC dip markets rediscovered)

2026-05-29 17:12:05 -04:00

roll_month.py

Fix HYPE Polymarket discovery: read its event container

2026-06-01 17:21:18 -04:00