Infiniti Briefing

Polymarket is tentatively targeting November 2, 2026, to begin creating new markets on Protocol V2, according to KuCoin. The transition would not automatically move existing markets or require holders of current CTF positions to convert them.

Testing comes before the transition

Polymarket introduced the upgraded infrastructure on October 5, 2026, starting with limited live testing. Canary testing is scheduled to continue through October 30, 2026, with its results determining whether the broader rollout proceeds as planned.

Developers face an earlier deadline: October 24, 2026, when Polymarket plans to retire Data API V1 endpoints, subject to documented exceptions. Affected integrations must move to Data API V2, which uses cursor-based pagination, standardized responses and snake_case fields. Its /v2/positions endpoint supports status filters for open, redeemable, mergeable and closed holdings.

Separate systems for new and legacy positions

According to KuCoin, Protocol V2 adds ERC-1155 position tokens, ExchangeV3 and modular contracts accommodating four market formats. Collateral remains pUSD, backed 1:1 by USDC. Legacy holdings stay linked to their original contracts, while V2 positions have separate accounting; portfolio applications therefore need to recognize both. Documentation provides for conversion of certain eligible legacy positions only after the relevant conditions or events are registered—not through an automatic platform-wide migration.

Trading integrations must also distinguish between V2 positionIds and legacy clobTokenIds. ExchangeV3 requires EIP-712 signing domain version 3, compared with version 2 for CTFExchangeV2; using the wrong format can cause order rejection. Older approvals do not automatically cover V2 contracts: purchases require sufficient pUSD approval for ExchangeV3, and sales require operator permission for the relevant PositionManager tokens.

Resolution tools expand

Six security firms reviewed the V2 contracts, KuCoin reports. The new OracleAggregator supports UMA and Chainlink integrations: OOReporterModule can pass settled UMA Optimistic Oracle results into resolution, while ChainlinkReporterModule can use configured Chainlink Data Streams information for price-based outcomes, including starting-versus-ending price comparisons.

OracleAggregator also provides reporting thresholds, dispute windows and arbitration procedures, allowing challenges under configured rules before final settlement. Cross-chain functionality remains a possible future capability, rather than a confirmed general rollout.

What it means for prediction markets

• November 2 is a target, not a completed migration. The scheduled October 30 testing conclusion remains a key checkpoint for newly created markets.
• Legacy and V2 markets will coexist. Existing CTF positions remain supported without mandatory conversion, making market-version identification important for portfolio and trading tools.
• Integration readiness matters before launch. The October 24 API deadline precedes the planned market transition, while identifiers, signing formats and approvals require separate updates.
• New resolution infrastructure is not a cross-chain launch. UMA and Chainlink support broadens the available resolution mechanisms, but does not establish a general cross-chain rollout.