Every release, and the Polymarket change behind it.

Chainlink TWAP settlement

Polymarket stopped settling its short crypto Up or Down markets on one price tick. Since August 7 the price to beat and the close are both Chainlink time-weighted averages, and since August 14 the 5-minute markets average the last 60 seconds like the 15-minute ones do. This release makes that official for both window lengths. Because the bot has always taken the result from Polymarket and priced off the live book, nothing in the strategy had to change and your existing config keeps working.

# Up or Down settlement, 5m and 15m
# Chainlink TWAP, 60-second lookback

# price to beat  = average of the 60 s before the open
# closing price  = average of the window's last 60 s
# Up wins when close >= price to beat

# Nothing to change in .env

CLOB v2, WebSocket quoting and live safety rails

Polymarket retired the original order book API, so live orders now go through the v2 client. We used the occasion for the biggest execution upgrade so far: a WebSocket engine that re-quotes on every book update rather than once per cycle, paper fills that queue behind real liquidity, and hard live caps that check positions on the exchange instead of trusting local bookkeeping.

# Live safety rails, USDC defaults
LIVE_MAX_DAILY_LOSS=25     # halt once realized loss passes this
LIVE_MAX_EXPOSURE=50       # freeze new buys at this exposure
LIVE_CANCEL_SEC=3          # seconds between cancel and replace

# CLOB v2 signing wallet: 1 = email / Magic proxy, 2 = browser wallet
POLYMARKET_SIG_TYPE=1

# WebSocket engine, same .env:   python ws_engine.py
# live data, log orders, post nothing:
WS_LIVE_SHADOW=true

Small-capital runs and clearer sizing

For people starting with a modest balance. One parameter now scales every position, the log shows what a cycle is about to risk before it commits, and a thin balance skips a window rather than guessing.

Unattended VPS runs

Everything in this release is about leaving the bot on a server and forgetting it: connections come back on their own after a blip, the process recovers from transient failures, and memory stays flat across days.

Faster starts, steadier bursts

Startup and busy-API behaviour: fewer round trips before the first cycle and smoother handling when many orders go out in a short span. Budgets and mode switches behave exactly as before.

Settlement pass, CSV export and the P&L ledger

Once windows resolve, the bot pulls the official outcomes into a local ledger, appends a running P&L log and exports spreadsheet-ready rows, without leaking strategy detail into the CSV headers.

# Simulation needs no signing keys (default)
POLYMARKET_DRY_RUN=true

# Live mode, only when you're ready
# POLYMARKET_PRIVATE_KEY=
# POLYMARKET_FUNDER=

More short windows, and rails for the operator

More short-term crypto Up or Down markets in the rotation, separate defaults for 5- and 15-minute windows, and settings that stop quoting as a window winds down.

Readable logs, quiet idle cycles

Terminal housekeeping: cycles are easier to scan, idle loops stop repeating themselves, and a failed API call states the problem once instead of dumping a traceback. Order logic and sizing are untouched.

First release: safe by default

The first build you could run end to end on your own machine. Signing keys stay optional until you add them, hosts come from config, and the loop targets the short crypto windows from day one.