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
Part 2 was settlement hygiene: pin 60s TWAP or stop calling it a 5m engine.
Part 3 is the matching floor that has now had time to show up in fills: 150ms crypto taker delay plus volume-tier rate limits.
1. The Execution Floor Is Also Old News
| Rule | Status in late September |
|---|---|
| Volume-tier CLOB buckets | live since early August |
| Crypto taker delay 50ms → 150ms | live since Sept 4 |
| Cancel-during-delay is not a free undo | still the right assumption |
These are no longer “watch the changelog.”
They are the reason July fill stats should not be copied into October config.
2. What Production Actually Measures
After two+ weeks on 150ms, the only honest question is fill quality.
Log per decision:
t_signal
t_submit
t_ack
t_fill
ask_at_signal
fill_price
delay_ms
retry_after_hits
scratch_spread
twap_move_during_delay
If you only log “order sent,” you cannot tell whether a bad clip was:
- late signal
- delay
- thin book
- 429 backoff
- TWAP path moving while the order was pending
3. What 150ms Did to the Old Taker Reflex
The old reflex:
tick → lift → cancel if next tick disagrees
That reflex is worse now for two independent reasons:
- TWAP60 already made last-tick identity the wrong target
- a longer taker delay makes the lift less reversible
A mid-band specialist can live with that. It has to change how it enters:
- wait for 45–55¢, not t=0
- assume the order may still be pending after the decision
- do not schedule a scratch that depends on canceling inside the delay
- stagger clips so one delayed fill is not the whole slot
Speed still matters for getting the fair 50¢.
Speed no longer substitutes for a TWAP-aligned thesis.
4. What Rate Tiers Did to Panic Cancels
Volume buckets turn cancel storms into self-inflicted downtime.
September operating rules:
- honor
Retry-After - idempotent client order ids
- cap orders and cancels per slot
- never use spam-cancel as a kill switch
- if you hit the bucket, flatten risk by not sending, not by sending more
A 5m bot that places small clips and scratches selectively can stay inside a usable tier.
A spray loop will spend the slot in 429s and call it “the market got worse.”
5. Scratch Quality Is the Hidden Cost
The public abrownfox001 footprint depends on near-flat scratches (sample path ~0.504 → 0.503).
That only works if the 50¢ book is still there when conviction dies.
After the delay change, re-measure:
- can you still exit near entry?
- how often is “breakeven” actually 1–2¢ of spread?
- do late-slot scratches get worse than mid-slot scratches?
If scratch tax ate the mid-band edge, the fix is not more cancels.
The fix is fewer weak entries.
6. Expected Code Changes in clob.ts / engine.ts
Keep the state machine. Change the timing contract:
enter only after edge + 45–55¢
assume delay_ms = 150
do not plan delay-window cancels
backoff on Retry-After
hard-cap slot inventory
skip scratch if depth is gone
Re-fit thresholds on post-Sept 4 slots only.
Pre-delay notebooks are a different venue.
7. What This Does Not Mean
It does not mean 5m BTC is dead.
It does not mean you should become a Combo RFQ bot.
It does not mean makers automatically inherited the edge.
It means last-look taker theater got more expensive, and fill logs have to prove the mid-band clip is still worth sending.
8. What Part 4 Covers
Settlement and matching are the core.
Part 4 is everything around the core that still tries to hijack the roadmap: Combos, agent connectors, extra APIs, and why most of them should stay outside engine.ts.
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. Delay values and tiers can move — confirm live docs.
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 #CLOB #TWAP #BTC #TradingBot #AlgoTrading #PredictionMarkets
Top comments (0)