Polymarket V2 could change how users bet on events

Polymarket has begun production testing of Protocol V2 ahead of a tentative Nov. 2 switch for newly created markets, replacing its 2019-era Gnosis CTF market architecture with a single ERC-1155 position system, pUSD collateral and modular resolution.
Summary

• Polymarket Protocol V2 will start handling new markets on November 2 after October canary testing.
• V2 replaces legacy Gnosis CTF adapters with one ERC-1155 position system and unified pUSD collateral.
• UMA and Chainlink can feed outcomes through Polymarket's new modular OracleAggregator settlement layer for markets.
• Polymarket says existing CTF holdings will remain unchanged while new V2 positions use separate contracts.
• Data API V1 retires October 24, giving developers nine days before the planned V2 switchover.

Polymarket protocol head Rajath Alex said on Oct. 5 that canary markets would run in production through Oct. 30 before net-new markets "tentatively" begin moving to Protocol V2 on Nov. 2. Existing CTF markets and positions will not automatically migrate to the new contracts.

Polymarket V2 rebuilds how positions are created

Polymarket's existing market system traces back to Gnosis' Conditional Tokens Framework from 2019. As new market formats were introduced, separate adapters and contracts were added for functions including negative-risk markets, collateral handling and resolution.

Protocol V2 removes much of that structure. Polymarket's official code repository describes V2 as its "next-generation prediction market smart contract system," with ERC-1155 position tokens, collateral handling, modular oracles, order matching and cross-chain functions.

Position IDs now encode information including the module, condition and outcome directly into the token identifier. The system uses a common PositionManager contract and Router, with separate modules handling different market structures.

The initial modules cover binary markets, atomic negative-risk markets, incremental negative-risk markets and combinatorial markets. Polymarket's published Polygon deployment list shows the PositionManager, Exchange, Router and each of those modules already deployed on mainnet.

The October release should not be confused with Polymarket's earlier CLOB v2 upgrade. As previously reported in crypto.news coverage of Polymarket's CLOB v2 rollout, the April upgrade changed exchange contracts, the matching engine and collateral while introducing pUSD for trading. Protocol V2 changes the position and market infrastructure underneath that trading system.

pUSD becomes the common collateral across V2 markets

Polymarket Protocol V2 uses Polymarket USD, or pUSD, as its common collateral asset across the new market modules.

Official contract documentation states that pUSD is an ERC-20 token wrapping USDC and USDC.e at a 1:1 ratio through an external vault. The code requires the combined USDC and USDC.e held by the vault to equal or exceed the outstanding pUSD supply.

The token itself is not new. pUSD arrived with the exchange changes earlier in 2026, but Protocol V2 makes it the common collateral used by its market modules. Existing integrations already using pUSD do not need to replace their collateral setup when adding V2 support, according to Polymarket's migration guide.

For developers, positions do change. V2 balances sit in the new PositionManager, while splits, merges and redemptions go through the Router. Existing CTF approvals do not carry over, so integrations need new permissions for V2 operations.

Polymarket explicitly tells developers to keep CTF support for older markets and holdings. Its migration documentation says existing CTF holdings are not converted when an integration adds Protocol V2.

UMA and Chainlink can settle markets through one layer

Resolution receives a separate redesign through the new OracleAggregator.

Polymarket's V2 code shows that the OracleAggregator sits above pluggable reporter, dispute and arbitration modules. Current reporter contracts include an UMA Optimistic Oracle module, a Chainlink reporter and an EOA reporter.

The UMA module can pass settled UMA outcomes into the aggregator as reporter votes. Chainlink's module handles price-based resolution using Chainlink Data Streams, according to the published contract documentation. Different reporter modules can be combined under thresholds set for individual markets.

Polymarket had already introduced Chainlink for certain objective markets. In related crypto.news coverage of the Chainlink integration, the platform used Chainlink Data Streams and Automation to settle crypto price markets using external market data.

UMA remains relevant for markets requiring event-based resolution. Crypto.news has separately documented how UMA resolves Polymarket prediction markets and how disputes can move through its challenge process. Protocol V2 does not simply replace UMA with Chainlink. Its OracleAggregator allows different resolution sources to plug into the same framework.

The V2 contracts contain cross-chain infrastructure as well. Polymarket's bridge documentation states that positions, collateral and resolution results can move through a transport layer whose current implementation uses Chainlink CCIP. Polygon remains the resolution hub in the published mainnet design.

No date has been announced for a multi-chain activation. The bridge code establishes the technical structure, but the Nov. 2 migration plan concerns new V2 markets and does not by itself announce trading on additional chains.

Security checks cover the new Polymarket contracts

Polymarket has released a detailed security record for Protocol V2 before the planned migration. Its official contract-security repository lists reviews by Cantina, Certora, Quantstamp, Pashov, Sigma Prime and Zellic across major V2 components. The repository lists Certora formal verification work covering the Exchange, Collateral Token, Position Manager, Binary Module, NegRisk Module, Combinatorial Module and OracleAggregator.

Alex said critical vulnerabilities remain eligible for rewards of up to $5 million under Polymarket's bug bounty program. The bounty was launched earlier in 2026 and covers smart contracts and other parts of the platform's technology stack.

The canary period gives developers and market makers a production environment for testing before the planned Nov. 2 transition. Alex said the limited rollout runs from Oct. 5 through Oct. 30, with new markets expected to begin using V2 afterward if the schedule holds.

Developers face an earlier October 24 deadline

A separate migration is already underway for Polymarket's Data API. Polymarket's official documentation says Data API V1 will retire on Oct. 24, 2026, requiring existing integrations to move to V2 routes before that date. The new system uses a shared response structure, cursor-based pagination and snake_case fields.

Data API V2 consolidates several position routes into /v2/positions and adds endpoints covering user profit and loss, volume, price history, resolutions and service status. Cursor pagination removes the old 10,000-row offset limit used by V1.

For regular app and website users, Polymarket says no technical migration is required. Users may encounter new approval prompts when interacting with V2 markets, while developers and smart-contract integrations need to support both V2 positions and legacy CTF holdings.

The current schedule gives API developers until Oct. 24 to leave Data API V1, keeps Protocol V2 canary markets running through Oct. 30, and sets Nov. 2 as the tentative date when newly created markets begin using the V2 protocol.