惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

H
Help Net Security
腾讯CDC
爱范儿
爱范儿
Google DeepMind News
Google DeepMind News
V
V2EX
Blog — PlanetScale
Blog — PlanetScale
Engineering at Meta
Engineering at Meta
GbyAI
GbyAI
量子位
F
Fortinet All Blogs
G
Google Developers Blog
T
The Blog of Author Tim Ferriss
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Hugging Face - Blog
Hugging Face - Blog
Last Week in AI
Last Week in AI
T
Tailwind CSS Blog
J
Java Code Geeks
S
SegmentFault 最新的问题
D
Docker
博客园 - 司徒正美
The GitHub Blog
The GitHub Blog
Jina AI
Jina AI
M
MIT News - Artificial intelligence
博客园 - 【当耐特】

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
How Real 5-Minute BTC Scalpers Work on Polymarket: Stale ...
FatherSon · 2026-05-27 · via DEV Community

FatherSon

Most Polymarket 5-minute BTC Up/Down bots don’t predict price — they exploit latency.

The core edge is simple but ruthless: Binance spot moves faster than Polymarket’s order book. When BTC has already moved significantly, stale limit orders remain on the book, creating mispricings that disappear in seconds.

Core Architecture

Dual WebSocket Streams:

  • Binance: wss://stream.binance.com:9443/ws/btcusdt@aggTrade (or @trade)

    • Real-time last price + short-term momentum (last 10–15s in basis points)
  • Polymarket CLOB: wss://ws-subscriptions-clob.polymarket.com/ws/market

    • Subscribe to active Up/Down token IDs
    • Maintain local order book from book snapshot + price_change events
    • Send PING every 10s (critical for connection stability)

Probability Engine (The Math)

The bot calculates true probability (not market price) using three inputs:

  1. Distance from reference price (in bp) — how far current BTC is from the 5-min window open price
  2. Momentum — direction and strength over last 15 seconds
  3. Time remaining — heavily weighted (log scale), becomes dominant in final 60 seconds

These are fed into a logistic function to output a clean probability [0,1].

Entry Rule: Trade only when:

  • Estimated prob > Best Ask + Edge Threshold (e.g. 4–8¢)
  • Spread ≤ 4¢
  • Sufficient liquidity at top of book
  • 5–60 seconds remaining in cycle

Execution Details

  • Order Type: Immediate-Or-Cancel (IOC) at best ask
  • Re-validate best ask immediately before submission (fight stale-fill risk)
  • Position size scaled by edge magnitude (larger edge = larger size, capped)
  • Strict daily loss limit + cooldown after losses

Why Most Bots Fail

  • Poor WebSocket reconnection logic
  • Not maintaining full local order book (relying only on best_bid_ask)
  • Weak time-weighting in probability model
  • No hard risk limits
  • Running from home internet (latency + packet loss kills it)

This strategy is pure execution speed + microstructure exploitation, not directional prediction. The bot isn’t smarter — it’s just faster at reacting to reality while the order book is still catching up.


Tags: #Polymarket #TradingBots #CryptoTrading #AlgorithmicTrading #WebSocket #PredictionMarkets #QuantitativeTrading #DeFi #BTC #Fintech