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 1 said the patch window is over. 60s Chainlink TWAP is the floor.
Part 2 is what still breaks after people think they “already switched to TWAP.”
1. The Rule Is Stable. The Implementations Are Not.
Live 5-minute crypto Up/Down pays 60-second Chainlink TWAP.
Open reference and final score should be the same family.
That sentence has been true since the mid-August 5m cutover.
The bugs I still see are not “is TWAP live?” They are:
- wrong window
- wrong open pin
- stale socket treated as a live price
- research labels from a retired series
A month is long enough for those bugs to look like “the strategy stopped working.”
2. The Leftover 30s Problem
5m markets first settled on 30s TWAP, then moved to 60s for markets deployed since August 14.
Public repos and notebooks still mix the two.
| Code thinks | Live market pays | What you get |
|---|---|---|
| Snapshot / CEX close | 60s TWAP | Obsolete target |
| 30s TWAP | 60s TWAP | Smoother series, wrong features |
| 60s live, snapshot open | 60s vs 60s | Silent third market |
| 60s open + 60s live | 60s TWAP | The only coherent book |
If twapFeed.ts can still subscribe to thirty, that is a research toggle. It is not a production path for new 5m slots.
3. The Slot Record That Has to Exist
After a month of production, every completed slot should have:
slot_id
twap_open
twap_now_at_decision
twap_end
t_left
resolution_src # rtds_twap | gamma
feed_age_ms
window_seconds # must be 60
If those fields are missing, you cannot debug:
- mixed-window contamination
- RTDS gaps
- “model was right, feed was stale”
- gamma fallback vs live path disagreement
Hope is not a resolution source.
4. Stale RTDS Is Still the Quiet Killer
RTDS made official TWAP easy to consume. It did not make the socket immortal.
September operating rule:
- connected ≠ fresh
- heartbeat ≠ a new TWAP observation
- CEX mid is lead-lag, not a backup settlement feed
- if
feed_age_msblows the budget, skip the slot
The public engine already treats the feed as a first-class module. Production has to treat freshness as a hard fail.
5. Why CEX Last Still Sneaks Back In
After TWAP, last-tick sniping died as a settlement exploit.
It did not die as a coding habit.
Typical sneak paths:
- label builder still uses Binance close
- dashboard plots spot and the model trains on the plot
- open pin taken from CEX mid “because it is faster”
- one missing RTDS tick replaced with last trade
Those shortcuts recreate the snapshot bot inside a TWAP repo.
Measure it instead:
disagree_rate = P(sign(cex_last - open) != sign(twap_end - twap_open))
If that rate is high and your model still keys off cex_last, the patch window did not include you.
6. Expected Tech Work on This Layer
Not a new strategy. Hygiene:
- Force
window_seconds = 60in production config - Pin open only from the 60s series
- Drop 30s from the live path
- Hard-fail on stale TWAP
- Keep gamma as post-slot scoring fallback, not a live substitute
- Retune path features on post-Aug 14 data only
The private P(up) can stay closed. The pin cannot.
7. How This Shows Up on @abrownfox001
The live account should still look like a path process:
- mid-band fills
- buys after the first thin seconds
- later scratches
- not a close-bell cluster
If the footprint flips back to last-second bursts, the settlement story and the fills have diverged. Watch the activity tab for that before you trust a changelog.
8. What Part 3 Covers
Settlement hygiene is necessary. It is not sufficient.
Part 3 is the other half of the new floor: 150ms taker delay, volume-tier limits, and whether mid-band 50¢ clips still fill well enough to scratch.
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. Confirm the live market’s resolution source before you trade it.
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 #Chainlink #BTC #TradingBot #AlgoTrading #PredictionMarkets
Top comments (0)