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

推荐订阅源

Microsoft Azure Blog
Microsoft Azure Blog
WordPress大学
WordPress大学
Google DeepMind News
Google DeepMind News
美团技术团队
大猫的无限游戏
大猫的无限游戏
H
Help Net Security
小众软件
小众软件
aimingoo的专栏
aimingoo的专栏
博客园 - 聂微东
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
M
MIT News - Artificial intelligence
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - Franky
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Microsoft Security Blog
Microsoft Security Blog
F
Fortinet All Blogs
A
About on SuperTechFans
Recent Announcements
Recent Announcements
D
Docker
Vercel News
Vercel News
Engineering at Meta
Engineering at Meta
腾讯CDC
Martin Fowler
Martin Fowler
阮一峰的网络日志
阮一峰的网络日志

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
Polymarket CLOB WebSocket in Python — Real-Time Order Boo...
BlueWhale-Quant-Lab · 2026-06-17 · via DEV Community

BlueWhale-Quant-Lab

If your Polymarket bot polls GET /book in a loop, your view of the market is as stale as your interval — and you'll lose to anyone using the WebSocket feed. This tutorial builds a real-time local order book in Python from the CLOB WebSocket stream.

Why WebSocket beats polling

  • Polling: you ask every N ms → your data is up to N ms old, and you burn REST rate-limit budget.
  • WebSocket: the server pushes changes → your information latency drops to roughly your network round-trip.

For a reactive strategy, this is the difference between trading the market that is and the market that was.

Connect and subscribe

import asyncio, json, websockets

WS_URL = "wss://ws-subscriptions-clob.polymarket.com/ws/market"

async def subscribe(token_ids):
    async with websockets.connect(WS_URL, ping_interval=20, ping_timeout=20) as ws:
        await ws.send(json.dumps({"assets_ids": token_ids, "type": "market"}))
        async for raw in ws:
            yield json.loads(raw)

(Confirm the exact URL, subscription payload, and message shapes against current Polymarket docs — they change.)

Maintain a local book from snapshot + deltas

The feed typically sends an initial book snapshot then incremental price-change messages. Apply them to a local structure:

class LocalBook:
    def __init__(self):
        self.bids = {}   # price -> size
        self.asks = {}

    def apply_snapshot(self, msg):
        self.bids = {float(l["price"]): float(l["size"]) for l in msg.get("bids", [])}
        self.asks = {float(l["price"]): float(l["size"]) for l in msg.get("asks", [])}

    def apply_delta(self, msg):
        for ch in msg.get("changes", []):
            side = self.bids if ch["side"] == "BUY" else self.asks
            price, size = float(ch["price"]), float(ch["size"])
            if size == 0:
                side.pop(price, None)
            else:
                side[price] = size

    def best_bid(self): return max(self.bids) if self.bids else None
    def best_ask(self): return min(self.asks) if self.asks else None
    def mid(self):
        b, a = self.best_bid(), self.best_ask()
        return (b + a) / 2 if b and a else None

Wire it together

async def run(token_id):
    book = LocalBook()
    async for msg in subscribe([token_id]):
        t = msg.get("event_type") or msg.get("type")
        if t in ("book", "snapshot"):
            book.apply_snapshot(msg)
        elif t in ("price_change", "delta"):
            book.apply_delta(msg)
        # react immediately on fresh state
        m = book.mid()
        if m is not None:
            on_mid(m, book)

asyncio.run(run(TOKEN_ID))

Measure your information lag

Always know how fresh your book is:

import time
lag_ms = (time.time() - float(msg["timestamp"])) * 1000
if lag_ms > 50:
    print(f"⚠ stale: {lag_ms:.0f}ms behind server")

The ceiling you can't code around

Here's the catch: your information latency can never beat your network round-trip to the server. The CLOB WebSocket terminates in Amsterdam — I measured ~1.2 ms from an AMS box vs ~88 ms from US-East. From the US, even a perfect WebSocket implementation is ~90 ms behind reality, because that's how long the packets take to arrive.

So the prerequisite for a fast feed is a server near the feed. I run mine on an Amsterdam-metro VPS: my Amsterdam VPS
Disclosure: affiliate link, I earn a referral. It's the box behind the 1.2 ms.

Robustness checklist

  • Reconnect with backoff — WebSockets drop; resubscribe and re-snapshot on reconnect.
  • Detect gaps — if deltas reference prices you don't have, request a fresh snapshot.
  • Heartbeat — use ping_interval so dead connections are detected fast.
  • One process, many assets — subscribe to multiple assets_ids on one socket.

Recap

WebSocket + a maintained local book gives you near-real-time perception. But the floor on "real-time" is your distance to Amsterdam. Get the server location right, then this code makes you genuinely fast.

Code is illustrative — verify against current docs. Latency from my own 2026 tests. Not financial advice.