Polymarket has begun manufacturing testing of Protocol V2 forward of a tentative Nov. 2 swap for newly created markets, changing its 2019-era Gnosis CTF market structure with a single ERC-1155 place system, pUSD collateral and modular decision.
Abstract
- Polymarket Protocol V2 will begin dealing with new markets on November 2 after October canary testing.
- V2 replaces legacy Gnosis CTF adapters with one ERC-1155 place system and unified pUSD collateral.
- UMA and Chainlink can feed outcomes by way of Polymarket’s new modular OracleAggregator settlement layer for markets.
- Polymarket says current CTF holdings will stay unchanged whereas new V2 positions use separate contracts.
- Information API V1 retires October 24, giving builders 9 days earlier than the deliberate V2 switchover.
Polymarket protocol head Rajath Alex said on Oct. 5 that canary markets would run in manufacturing by way of Oct. 30 earlier than net-new markets “tentatively” start shifting to Protocol V2 on Nov. 2. Current CTF markets and positions won’t robotically migrate to the brand new contracts.
Polymarket V2 rebuilds how positions are created
Polymarket’s current market system traces again to Gnosis’ Conditional Tokens Framework from 2019. As new market codecs have been launched, separate adapters and contracts have been added for capabilities together with negative-risk markets, collateral dealing with and backbone.
Protocol V2 removes a lot of that construction. Polymarket’s official code repository describes V2 as its “next-generation prediction market good contract system,” with ERC-1155 place tokens, collateral dealing with, modular oracles, order matching and cross-chain capabilities.
Place IDs now encode info together with the module, situation and end result straight into the token identifier. The system makes use of a standard PositionManager contract and Router, with separate modules dealing with totally different market constructions.
The preliminary modules cowl binary markets, atomic negative-risk markets, incremental negative-risk markets and combinatorial markets. Polymarket’s revealed Polygon deployment checklist reveals the PositionManager, Change, Router and every of these modules already deployed on mainnet.
The October launch shouldn’t be confused with Polymarket’s earlier CLOB v2 improve. As beforehand reported in crypto.news coverage of Polymarket’s CLOB v2 rollout, the April improve modified trade contracts, the matching engine and collateral whereas introducing pUSD for buying and selling. Protocol V2 adjustments the place and market infrastructure beneath that buying and selling system.
pUSD turns into the widespread collateral throughout V2 markets
Polymarket Protocol V2 makes use of Polymarket USD, or pUSD, as its widespread collateral asset throughout the brand new market modules.
Official contract documentation states that pUSD is an ERC-20 token wrapping USDC and USDC.e at a 1:1 ratio by way of an exterior vault. The code requires the mixed USDC and USDC.e held by the vault to equal or exceed the excellent pUSD provide.
The token itself will not be new. pUSD arrived with the trade adjustments earlier in 2026, however Protocol V2 makes it the widespread collateral utilized by its market modules. Current integrations already utilizing pUSD don’t want to switch their collateral setup when including V2 assist, in keeping with Polymarket’s migration information.
For builders, positions do change. V2 balances sit within the new PositionManager, whereas splits, merges and redemptions undergo the Router. Current CTF approvals don’t carry over, so integrations want new permissions for V2 operations.
Polymarket explicitly tells builders to maintain CTF assist for older markets and holdings. Its migration documentation says current CTF holdings usually are not transformed when an integration provides Protocol V2.
UMA and Chainlink can settle markets by way of one layer
Decision receives a separate redesign by way of the brand new OracleAggregator.
Polymarket’s V2 code shows that the OracleAggregator sits above pluggable reporter, dispute and arbitration modules. Present reporter contracts embrace an UMA Optimistic Oracle module, a Chainlink reporter and an EOA reporter.
The UMA module can go settled UMA outcomes into the aggregator as reporter votes. Chainlink’s module handles price-based decision utilizing Chainlink Information Streams, in keeping with the revealed contract documentation. Totally different reporter modules might be mixed underneath thresholds set for particular person markets.
Polymarket had already launched Chainlink for sure goal markets. In related crypto.news coverage of the Chainlink integration, the platform used Chainlink Information Streams and Automation to settle crypto value markets utilizing exterior market knowledge.
UMA stays related for markets requiring event-based decision. Crypto.information has individually documented how UMA resolves Polymarket prediction markets and how disputes can transfer by way of its problem course of. Protocol V2 doesn’t merely exchange UMA with Chainlink. Its OracleAggregator permits totally different decision sources to plug into the identical framework.
The V2 contracts include cross-chain infrastructure as nicely. Polymarket’s bridge documentation states that positions, collateral and backbone outcomes can transfer by way of a transport layer whose present implementation makes use of Chainlink CCIP. Polygon stays the decision hub within the revealed mainnet design.
No date has been introduced for a multi-chain activation. The bridge code establishes the technical construction, however the Nov. 2 migration plan considerations new V2 markets and doesn’t by itself announce buying and selling on extra chains.
Safety checks cowl the brand new Polymarket contracts
Polymarket has launched an in depth safety file for Protocol V2 earlier than the deliberate migration. Its official contract-security repository lists opinions by Cantina, Certora, Quantstamp, Pashov, Sigma Prime and Zellic throughout main V2 parts. The repository lists Certora formal verification work overlaying the Change, Collateral Token, Place Supervisor, Binary Module, NegRisk Module, Combinatorial Module and OracleAggregator.
Alex mentioned essential vulnerabilities stay eligible for rewards of as much as $5 million underneath Polymarket’s bug bounty program. The bounty was launched earlier in 2026 and covers good contracts and different components of the platform’s expertise stack.
The canary interval provides builders and market makers a manufacturing atmosphere for testing earlier than the deliberate Nov. 2 transition. Alex mentioned the restricted rollout runs from Oct. 5 by way of Oct. 30, with new markets anticipated to start utilizing V2 afterward if the schedule holds.
Builders face an earlier October 24 deadline
A separate migration is already underway for Polymarket’s Information API. Polymarket’s official documentation says Information API V1 will retire on Oct. 24, 2026, requiring current integrations to maneuver to V2 routes earlier than that date. The brand new system makes use of a shared response construction, cursor-based pagination and snake_case fields.
Information API V2 consolidates a number of place routes into /v2/positions and provides endpoints overlaying person revenue and loss, quantity, value historical past, resolutions and repair standing. Cursor pagination removes the outdated 10,000-row offset restrict utilized by V1.
For normal app and web site users, Polymarket says no technical migration is required. Users could encounter new approval prompts when interacting with V2 markets, whereas builders and smart-contract integrations must assist each V2 positions and legacy CTF holdings.
The present schedule provides API builders till Oct. 24 to go away Information API V1, retains Protocol V2 canary markets working by way of Oct. 30, and units Nov. 2 because the tentative date when newly created markets start utilizing the V2 protocol.
