Polymarket CLOB V2 and pUSD: A Dated Timeline

Polymarket's pages use "V2" for several things, so this post goes back to the primary sources and builds the timeline from them (CLOB is Polymarket's central limit order book). We read every page cited here on Oct 19, 2026. Each row below comes from the official predictions changelog; to check a row yourself, open the changelog and find the entry with the same date.

The dated entries

Dated changelog entries on CLOB V2, pUSD and Protocol V2 objects. Source: docs.polymarket.com/changelog/predictions, checked Oct 19, 2026.

The migration guide confirms the go-live and adds the time of day, about 11:00 UTC, with trading paused for about 1 hour. The pUSD and Protocol V2 guide explains the first two rows. The last two are developer-facing Data API entries, and the resolution guide covers the resolutions route from the Sep 28 entry. One more developer-facing entry, dated Jul 14, 2026, deprecates Relayer calls (the Relayer submits gasless transactions) to the old CLOB v1 Neg Risk Adapter (a contract for negative-risk, multi-outcome events) and gives redeems through it a grace period until Jul 17, 2026 at 00:00 UTC.

Which V2 is which?

The changelog and the migration pages use "V2" for several things. Keeping them apart avoids most of the confusion.

• CLOB V2 is the upgrade that went live on April 28, 2026: new exchange contracts, a rewritten order backend and pUSD as the collateral token.
• pUSD is the token that replaced USDC.e as collateral in that upgrade.
• Protocol V2 is a second position system, with its own contracts, next to Conditional Tokens. Its migration pages start from integrations that already use pUSD and the CTF Exchange V2 order format.
• Fee Structure V2 and Data API v2 are separate changelog entries, about fee categories and about a new set of data routes. They are other changes that happen to carry the same label.

What the docs leave undated

For Protocol V2 itself, the pages we read give no launch date, no date for the first V2 market and nothing about retiring CTF markets. The migration guides do tell integrators to keep CTF support. The predictions changelog has no entry that announces Protocol V2. The only entries that mention Protocol V2 objects, a v2 oracle or polymarket-v2 condition ids and modules, are the two data entries in the table. In our reading, a mention in a data entry is not a launch date. The SDK changelog mentions Protocol V2 positions in several TypeScript and Python releases, but it lists releases by version number without dates, so it cannot date the launch either.

What the pages do say about V2 markets, without dates, is covered in the guide: their positions live in PositionManager, their orders settle through ExchangeV3, they can use resolution mechanisms other than UMA (the oracle the documentation names for prediction markets), and combinatorial positions use Protocol V2.

Other dated items sit nearby, and none is a launch date. The wallets page says account wallets deployed on or after May 4, 2026 are Deposit Wallets, the default smart wallet, while Proxy and Safe wallets are described as legacy types. The Contracts page lists audit reports titled Polymarket V2 starting in April 2026, and its newest report of any scope is from August 2026. This post does not list every dated item on those pages, such as the other audit reports or a later wallet upgrade. In our reading, an audit date shows when a review was written, not when a market went live.

What changed in practice for a trader

The CLOB V2 cutover paused trading, wiped all open orders and put a new collateral token behind the balance. Protocol V2 is quieter. For people who use the Polymarket app or website, the docs say no technical migration is required beyond completing any approval prompts that appear. The documentation does not say that the Polymarket app shows which ledger a market uses.

Facts worth re-checking after any upgrade (our suggestions, not Polymarket's):

• Open orders. The CLOB V2 cutover wiped them. Routine matching-engine restarts follow their own pattern: they are announced beforehand, and after a restart the engine enters post-only mode for two minutes. The guide to order types explains what post-only means.
• Approvals. The migration overview tells Polymarket app and website users to complete any approval prompts that appear. The pages do not say what those prompts approve.
• The balance unit. Since the cutover, balances and order costs are in pUSD, not USDC.e.
• Resolution rules and status. Protocol V2 markets can use resolution mechanisms other than UMA. The resolution guide shows where to find a market's status in the data.
• Fees. They are set by the protocol at match time. The fees guide has the rates and the dates they changed.

How to follow updates

Polymarket records changes in a few places. The predictions changelog lists dated entries, newest first. The CLOB V2 migration guide points to Discord, Telegram and status.polymarket.com for operational updates and incident notices. For matching-engine work, the documentation says planned restarts and maintenance windows are announced ahead of time in the Trading APIs channels on Telegram and Discord, with a goal of about two days' notice when possible. The documentation's page index is at docs.polymarket.com/llms.txt, and the Markdown copy of each page (add .md to its address) opens with a link to it, which makes it easy to see whether a new migration page has appeared.

Each guide on this site shows the day its rules were last compared with the official pages, and the editorial policy explains how to report an error. When a guide and an official page differ, trust the official page.

PolyTerminal is an independent interface for Polymarket and is not operated or endorsed by Polymarket. Orders placed through PolyTerminal carry PolyTerminal’s Polymarket builder code, and PolyTerminal may charge a builder fee on top of Polymarket’s own fees. This page is educational and is not investment advice. Rules were compared with the official documentation on Oct 19, 2026; check the source before you act on a number.