Prediction market platform Polymarket has announced that its Protocol V2 upgrade will not automatically transfer existing user bets held under its older Conditional Tokens Framework (CTF) to new smart contracts, according to migration guidance published by Rajath Alex on Oct. 5.
While everyday traders using Polymarket's web or mobile application will not need to perform technical migrations beyond completing standard in-app approval prompts, third-party developers and trading integrations must update their systems to support both legacy and V2 contracts concurrently.
Key Takeaways
- Canary Testing Timeline: Live canary test markets are running from Oct. 5 through Oct. 30, with Nov. 2 targeted as the tentative switch for newly created markets.
- Dual-Ledger Architecture: Legacy positions stay on the original CTF ledger, whereas new V2 balances will sit in a separate smart contract called PositionManager.
- New Trading Permissions: Buyers must authorize ExchangeV3 to spend pUSD collateral, while sellers must grant permission for ExchangeV3 to operate on PositionManager shares.
- No Auto-Conversion: Existing CTF approvals will not transfer to V2 contracts; manual registration by Polymarket is required to connect old balances to new position balances.
Developer Integration Requirements for Protocol V2
For developers building automated trading systems or interface integrations on Polygon, Protocol V2 alters where positions are stored and how orders are signed. Legacy CTF holdings remain on the existing ledger, while V2 balances are managed through the PositionManager contract. Integrations must retain CTF identifiers for older markets while selecting the correct version identifiers for V2 positions.
Trading permissions remain completely isolated between generations. Under the API migration guide, V2 purchase orders require account authorization for ExchangeV3 to spend pUSD, Polymarket's trading collateral. V2 orders utilize position IDs alongside signing-domain version 3, whereas legacy CTF orders retain signing-domain version 2.
Integrations interacting directly with smart contracts for creation, combination, or redemption must now utilize the Router contract. Router requires pUSD spend authorization for position creation, as well as operator permissions on PositionManager for combining or redeeming shares. These changes follow previous system updates noted in Polymarket's changelog, including CLOB V2 on April 28, 2026, and Data API v2 on Sept. 4, 2026.
Migration Mechanisms and Platform Support
Although Protocol V2 does not automatically transfer open positions, a distinct mechanism allows traders to move CTF holdings into V2 if the specific market condition is registered by Polymarket first. Polymarket's indexing documentation outlines events connecting legacy CTF balances to new PositionManager balances, but this operates separately from software updates.
The update arrives as prediction market volume reaches $188 billion, driving increased scrutiny on infrastructure reliability. Integrations using pUSD and CTFExchangeV2 will keep identical order-book credentials, wallet structures, and endpoints, but Polymarket advises developers to explicitly verify buying, selling, and balance queries across both market types.
Why It Matters
Requiring developers to maintain dual-system compatibility prevents disruption to live positions while Polymarket transitions to upgraded settlement infrastructure. However, operating parallel contract systems adds technical overhead for market makers and automated trading algorithms that must handle separate signing domains and permission structures. The smooth execution of canary testing through Oct. 30 will be a critical indicator of whether the Nov. 2 rollout for new markets can proceed without fracturing liquidity or creating order execution delays.
