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
The last series covered the August–early September patch: TWAP60, 150ms taker delay, rate tiers, Combos, APIs.
This new 5-part series is the next layer. The venue did not freeze after that patch. It is now talking about rebuilding the matching stack itself.
- Part 1 — Rails are moving under live 5m bots (this post)
- Part 2 — Settlement is still TWAP60; do not un-pin it
- Part 3 — Delay, CLOB rewrite, and what latency will mean in Q4
- Part 4 — Product split: 5m crypto vs Combos vs US rails
- Part 5 — What stays in abrownfox001 while the exchange is rebuilt
The New Fact Pattern
By mid-September 2026, a 5-minute BTC bot has to hold two thoughts at once.
Already live
- 5m / 15m / 4h crypto Up/Down settle on 60s Chainlink TWAP
- RTDS is the public live path
- volume-tier CLOB limits
- crypto taker delay was raised to 150ms on Sept 4
- Combos exist as an RFQ product, not a 5m CLOB clone
Now incoming / adjacent
- DeFi/onchain product push after the US business took attention
- public comments that the current CLOB is tech-debt
- a matching-engine rewrite in Rust, targeted mid-to-late Q4
- claimed early benchmarks: much faster p99, far higher order/sec capacity
- more builder-surface noise (grants, pitch days, agent connectors)
The bot you run today is still on the old rails.
The bot you want in December may be talking to a different engine.
Why This Matters More Than Another Feature Launch
Combos and agent APIs are optional.
A matching-engine rewrite is not optional if you live on the CLOB.
Expected side effects when that lands:
- order ack / fill timing distributions change
- websocket and open-order semantics can change
- rate-limit headers and reject codes can change
- “150ms delay” may be re-specified, not just left as folklore
- fill-quality notebooks from August become stale overnight
A 5m specialist that logs nothing except PnL will not know whether a bad week was signal decay or a new matching path.
What I Am Not Doing
I am not:
- pausing BTC 5m because a Q4 rewrite was mentioned
- porting the engine into Combos
- treating builder-pitch week as alpha
- rewriting
P(up)because the venue hired for DeFi product
I am:
- keeping the specialist loop
- pinning TWAP60
- measuring delay and fill slippage
- isolating adapters so a CLOB cutover does not require a strategy rewrite
The Durable Core
@abrownfox001 is still:
BTC 5m
→ official TWAP path vs open
→ 45–55¢ only
→ re-score
→ scratch decay / redeem strength
Public shell: the GitHub TypeScript engine.
Private layer: the calibrated 5m read.
Public proof surface: the profile, wallet, and walkthrough video.
That core survives a venue rebuild only if settlement pinning and execution logs are clean.
The Operator Question for This Series
If Polymarket replaces the CLOB in Q4, which parts of a 5m bot are strategy and which parts are just yesterday’s matching quirks?
Part 2 starts with the part that should not change: the official 60s TWAP series.
Links
- Repo: https://github.com/abrownfox0/abrownfox001-twap60-prediction-trigger-system
- Video: https://www.youtube.com/watch?v=XzhugRL6BV4
- Live activity: https://polymarket.com/@abrownfox001?tab=activity
Not financial advice. Roadmaps slip. Confirm live market rules and @PolymarketDevs before you retune production.
If you have more questions, please feel free to contact me at any time: https://t.me/abrownfox001
My Polymarket Activity: https://polymarket.com/@abrownfox001?tab=activity
#Polymarket #TWAP #TradingBot #BTC #CLOB #AlgoTrading #PredictionMarkets
Top comments (0)