mirror of
https://github.com/cjudice-commits/prediction-market-arb.git
synced 2026-07-27 21:47:46 +00:00
Refresh stale Polymarket slugs (BTC dip markets rediscovered)
Polymarket appends random hash suffixes when re-publishing markets (e.g. will-bitcoin-dip-to-70k-in-may-2026 → ...-2026-438-356-919). Our static pairs.json had the unsuffixed slugs from the original spreadsheet snapshot, so every BTC 'below' pair silently fell through to NO POLY despite both venues having liquid markets. User flagged this looking at BTC <70k May. - scripts/refresh_pairs.py: walks each asset's 'what-price-will-X- hit-in-may' multi-outcome event on Gamma, rebuilds the (asset, direction, strike) → slug map, rewrites data/pairs.json. Probes HYPE strikes individually since there's no container event for that asset. Has --dry-run. - data/pairs.json: updated to current live slugs. Two BTC arbs that were previously hidden now surface (BTC <65k and <70k both ARB). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
+7
-7
@@ -196,7 +196,7 @@
|
||||
"asset": "BTC",
|
||||
"kalshi_ticker": "KXBTCMINMON-BTC-26MAY31-7250000",
|
||||
"kalshi_strike": 72500.0,
|
||||
"poly_slug": "will-bitcoin-dip-to-70k-in-may-2026",
|
||||
"poly_slug": "will-bitcoin-dip-to-70k-in-may-2026-438-356-919",
|
||||
"poly_strike": 70000.0
|
||||
},
|
||||
{
|
||||
@@ -204,7 +204,7 @@
|
||||
"asset": "BTC",
|
||||
"kalshi_ticker": "KXBTCMINMON-BTC-26MAY31-7000000",
|
||||
"kalshi_strike": 70000.0,
|
||||
"poly_slug": "will-bitcoin-dip-to-70k-in-may-2026",
|
||||
"poly_slug": "will-bitcoin-dip-to-70k-in-may-2026-438-356-919",
|
||||
"poly_strike": 70000.0
|
||||
},
|
||||
{
|
||||
@@ -212,7 +212,7 @@
|
||||
"asset": "BTC",
|
||||
"kalshi_ticker": "KXBTCMINMON-BTC-26MAY31-6750000",
|
||||
"kalshi_strike": 67500.0,
|
||||
"poly_slug": "will-bitcoin-dip-to-65k-in-may-2026",
|
||||
"poly_slug": "will-bitcoin-dip-to-65k-in-may-2026-183-857-425",
|
||||
"poly_strike": 65000.0
|
||||
},
|
||||
{
|
||||
@@ -220,7 +220,7 @@
|
||||
"asset": "BTC",
|
||||
"kalshi_ticker": "KXBTCMINMON-BTC-26MAY31-6500000",
|
||||
"kalshi_strike": 65000.0,
|
||||
"poly_slug": "will-bitcoin-dip-to-65k-in-may-2026",
|
||||
"poly_slug": "will-bitcoin-dip-to-65k-in-may-2026-183-857-425",
|
||||
"poly_strike": 65000.0
|
||||
},
|
||||
{
|
||||
@@ -228,7 +228,7 @@
|
||||
"asset": "BTC",
|
||||
"kalshi_ticker": "KXBTCMINMON-BTC-26MAY31-6250000",
|
||||
"kalshi_strike": 62500.0,
|
||||
"poly_slug": "will-bitcoin-dip-to-60k-in-may-2026",
|
||||
"poly_slug": "will-bitcoin-dip-to-60k-in-may-2026-973-269",
|
||||
"poly_strike": 60000.0
|
||||
},
|
||||
{
|
||||
@@ -236,7 +236,7 @@
|
||||
"asset": "BTC",
|
||||
"kalshi_ticker": "KXBTCMINMON-BTC-26MAY31-6000000",
|
||||
"kalshi_strike": 60000.0,
|
||||
"poly_slug": "will-bitcoin-dip-to-60k-in-may-2026",
|
||||
"poly_slug": "will-bitcoin-dip-to-60k-in-may-2026-973-269",
|
||||
"poly_strike": 60000.0
|
||||
},
|
||||
{
|
||||
@@ -244,7 +244,7 @@
|
||||
"asset": "BTC",
|
||||
"kalshi_ticker": "KXBTCMINMON-BTC-26MAY31-5750000",
|
||||
"kalshi_strike": 57500.0,
|
||||
"poly_slug": "will-bitcoin-dip-to-55k-in-may-2026",
|
||||
"poly_slug": "will-bitcoin-dip-to-55k-in-may-2026-941",
|
||||
"poly_strike": 55000.0
|
||||
},
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user