DEV Community

ABROWNFOX001
ABROWNFOX001

Posted on

Freeze the Strategy, Swap Only the Rails

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

Parts 1–4 said the venue is moving: TWAP60 is live, taker delay is 150ms, Combos are a different machine, and a CLOB rewrite is on the Q4 radar.

Part 5 is the operating plan for @abrownfox001 while that happens.

Wallet: 0x12b712029efeee7efc4066e98e4e1b6beb8b1b0b

1. Freeze This

The specialist loop does not get rewritten because the exchange is rewriting itself.

BTC 5m
→ 60s Chainlink TWAP vs open
→ enter only in 45–55¢
→ re-score
→ scratch decay / redeem strength
Enter fullscreen mode Exit fullscreen mode

Public shell stays in the repo.

Calibrated P(up) stays private.

Style checks stay on the activity tab: BTC, 5m, mid-band, later sells than buys.

2. Patch These

Layer Keep doing
Settlement Same-series 60s pin; log resolution_src
Feed RTDS freshness hard-fail; no CEX-last substitute
Execution taker_delay_ms = 150 in config
Metrics t_signal, t_submit, t_ack, t_fill, fill vs ask
Quotas Retry-After, idempotent ids, per-slot caps
Adapters 5m CLOB isolated from Combos / agents

When a new matching engine goes live, swap the CLOB adapter first.

Do not retune signal weights on day one of a rail change.

3. Cutover Protocol

If Q4 CLOB rewrite lands:

  1. Freeze P(up) thresholds
  2. Paper or micro-size only
  3. Compare the measurement row to the September baseline
  4. Ask which number moved: signal, delay, stale TWAP, or new p99
  5. Only then touch scratch / size

If you change strategy and rails in the same week, you will not know what broke.

4. What I Will Not Ship

  • Combos inside engine.ts
  • agent auto-trade as production
  • 15m / Kalshi weights reused on 5m labels
  • snapshot-close revival
  • “add more coins” as a hedge against matching uncertainty
  • scale-up off one clean week after a cutover

New surface is optional.

A contaminated target is not.

5. How to Keep Auditing the Account 

curl "https://gamma-api.polymarket.com/public-profile?address=0x12b712029efeee7efc4066e98e4e1b6beb8b1b0b"
curl "https://data-api.polymarket.com/trades?user=0x12b712029efeee7efc4066e98e4e1b6beb8b1b0b&limit=1000"
Enter fullscreen mode Exit fullscreen mode

Re-run the outsider checks:

  • still BTC 5m?
  • still 45–55¢?
  • still later sells than buys?
  • still same-market flat exits?
  • still not only clustering at the bell?

If those break, the machine changed. The README would be late news.

6. Honest Limit

Public sample stats (150 markets near 50¢, ~60.7% held-side) describe a filtered settlement book from an earlier window. They are not a Q4 forecast and not a promise that cloning src/ reproduces the live read.

The edge is still the unpublished signal plus fill quality under the current delay.

A faster CLOB does not mint that edge. A slower official TWAP path does not either.

7. Series Recap

  • Part 1: Rails are being rebuilt under live 5m bots
  • Part 2: Keep TWAP60 pinned while that happens
  • Part 3: Measure 150ms delay now; expect a different p99 later
  • Part 4: Combos and US rails are other machines
  • Part 5: Freeze strategy, swap adapters, log the split

One line:

Forecast the official TWAP path, buy it only near fair value, refuse weak tickets — and treat the next CLOB as a new pipe, not a new thesis.

Links

Not financial advice. Paper or micro-size first. Rules, delays, and matching engines can move again.

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 #BTC #TradingBot #CLOB #AlgoTrading #PredictionMarkets #QuantTrading
Enter fullscreen mode Exit fullscreen mode

Top comments (0)