ABROWNFOX001

Posted on Sep 10

What Actually Changed for Bots

#api #automation #crypto #web3

GitHub: https://github.com/abrownfox0/abrownfox001-twap60-prediction-trigger-system

YouTube walkthrough: https://www.youtube.com/watch?v=XzhugRL6BV4

Live profile: https://polymarket.com/@abrownfox001

This is part 1 of a 5-part series on the latest Polymarket platform changes and the tech work they force on short-horizon bots.

Part 1 — The change map (this post)
Part 2 — TWAP60 settlement: what a 5m engine must pin
Part 3 — Taker delay, rate limits, and execution reality
Part 4 — Combos, APIs, and the new product surface
Part 5 — What I am changing in the abrownfox001 stack

The Last 60 Days Were Not Cosmetic

If your mental model of Polymarket is still “5-minute BTC, last tick, spray taker orders,” the platform has moved.

The updates that matter for builders, from late July through early September 2026:

Date	Change	Why bots care
Aug 4	RTDS delivers Chainlink TWAP over public WebSocket	Official live series without separate Chainlink creds
Aug 6	Volume-based CLOB rate tiers live	Order/cancel spam is now a quota problem
Aug 7	Snapshot settlement replaced by TWAP	Last-tick models die
Aug 14	5m crypto TWAP 30s → 60s	The 5m target series changed again
Aug 21	Combos public on Polymarket US	New multi-leg product, RFQ not CLOB
Sep 3	Short trading/API incident (open-order reads / DB lag)	Need reconnect + stale-data guards
Sep 4	Crypto taker delay 50ms → 150ms	Latency edge compressed on purpose
Sep 7	Polymarket live on Exa Connect	New agent/tooling access path

Same venue. Different machine.

Three Layers Moved at Once

Most writeups isolate one headline. Bots break when three layers move together.

1. Settlement layer

5-minute crypto Up/Down now pays a 60-second Chainlink TWAP, not a snapshot and not the first 30s window. Open and close must come from that family.

2. Matching layer

Taker delay on crypto markets was raised to 150ms on September 4. Combined with earlier delay-lock behavior, “see tick, lift immediately, cancel if wrong” is a worse job.

3. Access layer

Volume-tiered rate limits, unified gateway/API work, RTDS, SDK Retry-After headers, Combos RFQ, and now Exa Connect change how you subscribe, place, cancel, and observe.

A 5m directional engine has to survive all three. Changing only the feed name is not an update.

What Did Not Change

For @abrownfox001 the product choice is the same:

BTC
5-minute clock
mid-band 45–55¢
scratch decaying tickets
redeem the filtered book

The public shell is still the TypeScript engine in the repo.

The live calibrated read stays private.

What changed is the environment that shell runs inside.

The Operator Question This Series Is Built Around

Do not start with “is Polymarket still tradeable?”

Start with:

Which official series does a live 5m market pay?
Can I stream that series with freshness checks?
After a 150ms taker delay and volume-tier limits, is mid-band entry still viable?
Which new products (Combos, perps, agent APIs) are distractions versus infrastructure?
What must be forked in code this month versus next quarter?

Parts 2–5 answer those in order.

Expected Tech Work, Compressed

If you run a short-horizon crypto bot, the checklist is no longer optional:

[ ] Subscribe to 60s TWAP, not 30s leftovers
[ ] Pin open and score close on the same series
[ ] Treat RTDS disconnects as stale, not “still connected”
[ ] Respect volume-tier token buckets and Retry-After
[ ] Re-measure fill quality after the 150ms delay
[ ] Keep Combos/RFQ in a separate adapter if you touch them at all
[ ] Log resolution_src, delay assumptions, and rate-limit hits per slot

That is the map. The next posts unpack each layer.

What Part 2 Covers

Settlement first.

How 60s Chainlink TWAP actually works on 5-minute markets, why mixing windows creates silent label error, and what twapFeed.ts has to do in September 2026.

Polymarket #TWAP #TradingBot #BTC #AlgoTrading #PredictionMarkets #Chainlink

DEV Community