Polymarket Launches Protocol V2 in Canary Markets Ahead of Planned November Migration
Key Takeaways
- •Protocol V2 consolidates Polymarket's layered contract stack into a single ERC-1155 position token contract, one pUSD collateral asset, one exchange, and one router, creating a unified integration surface for developers across all market types.
- •The new architecture natively supports binary, atomic and incremental negative-risk, and combinatorial markets at launch, with settlement handled by an OracleAggregator featuring pluggable modules for UMA, Chainlink, and future oracle providers.
- •The codebase has been audited by six firms—Cantina, Certora, Quantstamp, SigmaPrime, Zellic, and Pashov—formally verified by Certora, and covered by a bug bounty program offering up to $5 million for critical vulnerabilities.
- •Canary Markets running Protocol V2 will operate in production from October 5 through October30, ahead of a tentative November 2 switchover for net new markets, while holdings under the legacy Conditional Tokens Framework will not be converted.
- •Polymarket simultaneously released Data API V2, a Rust-based service powered by an in-house on-chain indexer, and advised v1 integrations to migrate in step with the October-to-November protocol transition.

Polymarket has launched Protocol V2, a next-generation smart contract architecture designed to succeed the legacy infrastructure that has served the prediction market platform since its inception. Rajath Alex, the company's protocol lead, announced the release, stating that the new system will first run in production through Canary Markets between October 5 and October 30, ahead of a tentative transition of all new markets to the upgraded stack on November 2. Polymarket ranks among the largest prediction market platforms in the crypto industry, and the state of its core contracts shapes how quickly new market types can ship and how easily external integrations connect to the platform.
The overhaul is driven by the architectural limits of Polymarket's current base layer. Since going live, the platform has operated on the Conditional Tokens Framework (CTF), a general-purpose system originally developed by Gnosis in 2019. Although serviceable, the framework demanded an extra adapter contract for every new market type introduced: a dedicated adapter for pUSD collateral, a wrapped token for negative-risk markets, a separate exchange for each market type, and its own oracle adapter for every integration. In practice, that meant each expansion of the platform's market lineup multiplied the number of contracts users and integrators had to route through.
Protocol V2 collapses that layered stack into a unified design anchored by a single ERC-1155 position token contract, a single collateral asset (pUSD), one exchange covering all market types, and a single router. Each position ID encodes its market type, market, and outcome, allowing the protocol to read position metadata straight from the identifier rather than routing through intermediary contracts. For developers and integrators, the practical effect is a single integration surface across every market type the platform supports, rather than a bespoke path for each one.
The system ships as a set of modules that natively handle binary markets, atomic negative-risk markets, incremental negative-risk markets, and combinatorial markets at launch. Every module also exposes additional primitive operations that broaden what can be built on top of positions while improving capital efficiency.
Outcome settlement runs through a new OracleAggregator with pluggable modules that connect to UMA, Chainlink, and future oracle providers, giving the platform more flexibility in how results are finalized. Bridging of positions, collateral, and resolutions across chains is embedded as a first-class capability and will be activated when Polymarket extends to multiple networks. The entire protocol can be upgraded through a secure governance process, enabling faster feature delivery without disrupting existing integrations.
Security, Audits, and Migration Timeline
Security anchored the rollout plan. The codebase has been audited by six firms — Cantina, Certora, Quantstamp, SigmaPrime, Zellic, and Pashov — and formally verified by Certora. Polymarket has also introduced a bug bounty program offering rewards of up to $5 million for critical vulnerabilities.
The migration itself will be gradual. Canary markets running on Protocol V2 will stay live in production through October 30, giving developers and market makers a window to integrate, with weekly office hours available throughout the four-week period. A tentative switchover of net new markets is scheduled for November 2; holdings in the existing Conditional Tokens Framework will not be converted. Existing positions therefore remain under the legacy framework even after new markets begin settling on V2 — a detail relevant to anyone holding or tracking CTF-based positions through the transition period.
Alongside the protocol release, Polymarket rolled out Data API V2, a new Rust-based service powered by an in-house on-chain indexer. The API supports the V2 protocol, standardizes response formats, and implements cursor-based pagination to keep trade and activity feeds consistent as new records arrive. Integrations still using Data API v1 are advised to migrate in step with the protocol transition, tying API upgrades to the same October-to-November timeline as the underlying contracts.
Looking ahead, the protocol establishes a foundation for features currently in research and development, including scalar resolution and directional collateral return. With canary markets live through October 30, the transition can be tracked against the tentative November 2 switchover of net new markets and the later activation of built-in cross-chain bridging as Polymarket extends to additional networks.