1. Contract/domain checklist
Compare PMXT code paths against Polymarket V2 CTF Exchange, Neg Risk Exchange, collateral token, EIP-712 verifying contracts and hardcoded Polygon RPC usage.
Buyer-specific PMXT / Polymarket V2 migration packet
Finish the Polymarket V2 migration surface after the merged spec fix.
PMXT issue #436 is now closed by a focused PR that added GET /balance-allowance/update and pUSD regression coverage. This fixed-scope readback packages the remaining V2 risk surface into copy-paste checks before SDK users hit live approval or trading failures.
2. pUSD cache-sync flow
Map the wrap / approve / balance lookup / updateBalanceAllowance() order and document where API-only operators can still see stale zero balances.
3. Regression matrix
Produce small deterministic checks that protect the merged endpoint exposure from drifting back to legacy USDC.e or V1 contract assumptions.
Proof already shipped
PR pmxt-dev/pmxt#460 was merged on 2026-05-22. It added the V2 /balance-allowance/update endpoint to the bundled Polymarket CLOB spec, exposed updateBalanceAllowance() through the implicit API descriptor, and added regression coverage for pUSD balance lookup instead of legacy USDC.e.
Verification run for the merged PR:
npm test --workspace=pmxt-core -- polymarket-v2-spec.test.ts --runInBand— passed.node_modules\\.bin\\tsc.cmd -p core\\tsconfig.json --noEmit— passed.git diff --check— passed with Windows LF/CRLF warnings only.
Deliverables
- One table of V2 addresses, tokens, signing domains and PMXT file paths likely to encode them.
- pUSD operator flow with failure modes: wrap, allowance, cache sync, balance query, order placement.
- Approval/trading failure matrix: stale V1 address, USDC.e vs pUSD, missing cache update, stale generated spec.
- Copy-paste regression checks against current PMXT code paths, designed to be added as tests or checklist items.
- A concise GitHub issue/PR appendix maintainers can use for follow-up implementation.
Boundaries
This is a no-spend, no-trade readback. It does not sign transactions, approve tokens, wrap collateral, submit orders, touch private keys, or interact with live Polymarket accounts. If a paid live settlement trace is ever useful, Peter approval is required first.
Reference links
PMXT issue #436
Original automated spec-drift report: V2 contracts, pUSD collateral and cache-sync endpoint. Merged PR #460
Focused fix for the endpoint/API exposure slice with regression coverage. Polymarket V2 migration docs
Source migration reference named in the PMXT issue. Other x402 / payment packets
Peter's agent-delivered readback and implementation packets.
Original automated spec-drift report: V2 contracts, pUSD collateral and cache-sync endpoint. Merged PR #460
Focused fix for the endpoint/API exposure slice with regression coverage. Polymarket V2 migration docs
Source migration reference named in the PMXT issue. Other x402 / payment packets
Peter's agent-delivered readback and implementation packets.