Polymarket Protocol V2 Goes Live November 2 With Unified Trading System

TLDR

• Polymarket initiated Protocol V2 testing on October 5, with full deployment scheduled for November 2.
• The upgrade replaces Gnosis Conditional Tokens Framework with a unified ERC-1155 position architecture.
• All new V2 markets will exclusively use pUSD as collateral.
• An OracleAggregator component enables markets to settle via UMA, Chainlink, or alternative resolution mechanisms.
• The protocol received audits from six security firms, with bug bounties reaching $5 million.

Polymarket is deploying a fundamental infrastructure upgrade known as Protocol V2. The overhaul modifies market creation mechanics, settlement procedures, and backend data architecture.

The testing phase launched October 5, 2026. According to protocol head Rajath Alex, canary markets—restricted testing environments—will operate until October 30. Full migration of new markets to V2 is targeted for November 2, although Polymarket notes this timeline remains subject to adjustment.

Core Infrastructure Transformations in V2

Polymarket’s existing architecture originates from 2019. It relies on the Gnosis Conditional Tokens Framework, supplemented by custom adapters developed incrementally for various market structures.

V2 eliminates this fragmented architecture. A single ERC-1155 token contract now handles all outcome positions, consolidating functionality previously distributed across multiple systems.

Position identifiers contain expanded metadata under V2. Each token ID now directly encodes the module type, condition parameters, and specific outcome.

A Router component joins the architecture. It channels trade requests to the appropriate exchange contract based on market classification.

Four market modules currently run on Polygon mainnet. These encompass binary markets, two variants of negative-risk structures, and combinatorial markets.

Universal pUSD Collateral Standard

All V2 markets will operate exclusively with pUSD collateral. This token maintains a 1:1 wrapper relationship with both USDC and USDC.e.

pUSD predates the V2 launch. Polymarket introduced it earlier in 2026 as part of broader exchange improvements.

The significance lies in its new universal status. pUSD transitions from an available option to the mandatory collateral standard across all V2 market modules.

Developers with existing pUSD integration can maintain their collateral workflows unchanged. However, permissions linked to the legacy CTF framework require fresh authorization.

Legacy CTF-denominated positions remain intact, according to Polymarket. The platform will not force migration of active positions.

Market resolution undergoes architectural changes in V2. An OracleAggregator component now manages the reporting modules that finalize market outcomes.

Available reporter mechanisms include UMA’s Optimistic Oracle, a Chainlink integration, and manual EOA-based reporting. Markets can employ different combinations depending on threshold configurations.

The Chainlink module leverages Data Streams for markets resolved by price data. UMA handles markets dependent on real-world event outcomes rather than financial feeds.

Cross-chain infrastructure appears in the codebase, utilizing Chainlink’s CCIP transport protocol. Polymarket has not committed to a multi-chain launch timeline. Polygon remains the primary settlement layer.

Six security organizations conducted pre-launch contract reviews. The audit roster includes Cantina, Certora, Quantstamp, Pashov, Sigma Prime, and Zellic.

Certora performed formal verification on key components: the Exchange, Position Manager, and OracleAggregator contracts. Alex confirmed that critical vulnerabilities discovered through the bug bounty program qualify for rewards up to $5 million.

A parallel transition affects developer tooling. Data API V1 sunsets on October 24, nine days ahead of the anticipated V2 market migration.

Data API V2 runs on a proprietary indexer developed internally by Polymarket. It substitutes offset pagination with cursor-based navigation, eliminating the prior 10,000-entry restriction.

End users face no action requirements when V2 activates. Polymarket indicates that certain new markets might trigger additional approval dialogs.

Currently, canary testing continues through its scheduled October 30 conclusion, with Protocol V2 deployment for new markets planned for November 2.