ABROWNFOX001

Posted on Sep 7

CLOB V2, Rate Tiers, and the SDK Cutover

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 covered the number the market pays: 60s Chainlink TWAP.

Part 3 is the access layer. A correct P(up) still dies if you sign V1 orders, ignore volume tiers, or parse rate-limit errors like it is 2025.

1. CLOB V2 Is Not Optional

CLOB V2 has been production since April 28, 2026.

V1 SDKs and V1-signed orders are done.

	V1 leftover	V2 now
TS package	`@polymarket/clob-client`	`@polymarket/clob-client-v2`
Python package	`py-clob-client`	`py-clob-client-v2`
Host	old V1 assumptions	`https://clob.polymarket.com`
Order fields	`nonce`, embedded fee assumptions	`timestamp`, `metadata`, `builder`
Fees	baked into signed order	operator-set at match
Collateral	USDC.e era	pUSD
Builder auth	separate HMAC header stack	`builderCode` on the order
EIP-712 domain	version 1	version 2

If your 5m bot still imports the old client, the strategy post is irrelevant. The order never becomes a live fill.

The public engine talks to this layer in src/clob.ts.

2. Volume-Tiered Rate Limits Are the Second Gate

Volume-based CLOB tiers went live around August 6.

They replaced the old “everyone gets the same burst until they don’t” feeling.

Practical meaning for a 5m specialist:

order + cancel traffic is metered per signer
higher trailing 30-day volume unlocks higher rates
spam cancel/replace loops get clipped first
Retry-After on 429s is now a first-class field in current SDKs

A mid-band engine that re-scores every 10–30s does not need a cancel storm.

It needs:

idempotent client order ids
batched cancels when flattening
backoff that honors Retry-After
a kill switch when the bucket is empty

If you copy-trade a 99¢ farmer’s replace cadence onto a 50¢ specialist, the limiter will educate you.

3. Unified SDKs Are Still Moving

Official repos are not frozen. As of early September 2026:

Polymarket/ts-sdk and Polymarket/py-sdk were still receiving updates
recent Python changelog items include Poly V2 identifiers, combo status fields, protocol versions
older CLOB-only tutorials drift from the unified DeFi API surface

Expect these client-side changes to keep landing:

prepare-order / gateway assembly for typed data
builder-attributed trades
combo and protocol-version fields on market models
retry behavior on 503s

Pin versions. Do not assume last month’s example still compiles against production.

4. Order Response Assumptions Also Moved

Earlier this summer, successful FAK/FOK matches stopped returning inline transactionHashes and started returning tradeIDs. Websocket fills stayed the source of truth for many live loops.

If your reconciler still blocks on an immediate hash from POST /order, it will look like fills vanished.

Correct pattern:

submit V2 order
key the in-flight object by client order id / trade id
confirm on user channel / trades poll
only then mark scratch vs hold

5-minute bots feel this immediately because the slot ends before a confused reconciler finishes guessing.

5. What a 5m Engine Should Change in Code

old:
  poll REST hard
  cancel/replace every tick
  assume V1 order fields
  ignore Retry-After

now:
  CLOB V2 client
  WS user channel + book
  idempotent orders
  honor rate tiers
  log 429s / 503s with backoff
  never mix perps gateway rules into CLOB

Perps got its own September changes (concurrent WS posts, HTTP overload shedding). That stack is not your 5m Up/Down path. Keep the adapters separate.

6. Mapping Onto abrownfox001

The public lifecycle is still:

discover btc-updown-5m-*
score TWAP60
taker clips in 45–55¢
scratch or redeem

The access-layer update is not a new strategy. It is survival:

V2 signing in clob.ts
fewer wasteful replaces
dry-run default via npm start
Windows binary still wraps the same shell

If rate-limit errors start dominating logs, cut cadence before you touch the private signal.

7. Checklist Before You Touch Alpha

[ ] Latest V2 CLOB client, not V1
[ ] pUSD / V2 collateral assumptions
[ ] builderCode only if you actually have one
[ ] Retry-After honored
[ ] tradeID reconciliation, not missing-hash panic
[ ] per-signer volume tier known
[ ] cancel batching on scratch
[ ] no perps endpoint copied into the 5m loop

8. What Part 4 Covers

Orders are only half of ops.

Part 4 is the data and product layer sitting around the CLOB:

Data API / Gamma serving changes
Combos + collateral return
indexer / PnL display fixes
why reconciliation breaks even when the strategy is unchanged

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. Pin current docs and SDK versions before you ship.

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 #TradingBot #SDK #BTC #AlgoTrading #RateLimits #PredictionMarkets

DEV Community