Polymarket’s Protocol V2 upgrade will introduce a separate system for new positions, but existing bets held under the platform’s Conditional Tokens Framework will not move automatically. According to CryptoSlate, users accessing Polymarket through its app or website do not need to carry out a technical migration, while developers of trading integrations must support both systems during the transition.
Existing positions remain under the older system
The upgrade affects how positions are recorded, traded and authorized on Polymarket’s Polygon-based onchain markets. Existing holdings remain in the older Conditional Tokens Framework, commonly called CTF. New V2 balances are recorded separately in a contract known as PositionManager.
That means the rollout is not a single process in which every existing bet is transferred to a new contract. Polymarket’s migration guidance distinguishes between updating trading software and moving a particular position. A CTF holding can be moved into V2, but only through a separate, registered migration process.
The relevant condition or event must first be registered by Polymarket. The platform’s contract registry and indexing references then connect the old CTF balance with the new PositionManager balance. This operation is separate from a developer adding V2 support to an exchange interface or trading application.
Rajath Alex said on Oct. 5 that Polymarket would operate several live test, or “canary,” markets from Oct. 5 through Oct. 30. Nov. 2 was described as a tentative date for switching newly created markets to the new system. It is not a deadline by which every existing bet must be converted.
For ordinary users of Polymarket’s app and website, the guidance says no technical migration is needed. Users should complete any approval requests displayed in the application. The instructions covered Polygon-based onchain trading; Polymarket US users are directed to separate documentation.
Developers must maintain compatibility with both systems
The biggest operational changes concern trading integrations, including software that connects to Polymarket’s markets. These systems must continue to recognize legacy CTF positions while also adding support for V2 position identifiers, balances and permissions.
V2 uses PositionManager balances, whereas older markets continue to use CTF identifiers. Integrations must select the correct share identifier according to the market’s version, even when responses contain identifier fields for both generations.
The two trading paths also use different order and signing details:
- V2 orders use position IDs and signing-domain version 3.
- CTF orders continue to use their existing exchange format and signing-domain version 2.
- Balance requests must distinguish V2 shares from CTF shares.
Permissions are separate as well. For a V2 purchase, the account holding the buyer’s assets must authorize ExchangeV3, the new trading contract, to spend enough pUSD—the collateral used for trading on Polymarket—to cover the purchase and fees. Selling requires permission for ExchangeV3 to operate on the seller’s PositionManager shares.
Existing CTF permissions do not automatically provide either of those approvals. As a result, software that previously worked with CTF markets cannot assume that its existing authorizations will cover V2 transactions.
Integrations that create, combine or redeem positions directly through smart contracts face additional changes. V2 uses a Router contract. Creating positions requires approval for Router to spend pUSD, while combining or redeeming positions requires Router operator permission on PositionManager. Developers must also revise balance processing and payout-related reads.
What stays unchanged for some integrations
The migration does not require every part of an existing trading setup to be replaced. Integrations already using pUSD and the CTFExchangeV2 order format can continue using the same collateral, wallets, order-book credentials and endpoints, according to the guidance.
They must nevertheless test and verify purchases, sales and balances on both a V2 market and a CTF market. The need for parallel support reflects the fact that the older and newer position systems will coexist rather than being combined automatically.
The Protocol V2 rollout should also be distinguished from earlier Polymarket software updates. The platform’s changelog lists CLOB V2 as going live on April 28, 2026, and Data API v2 as launching on Sept. 4, 2026. The October Protocol V2 change concerns the separate position-management system.
Current market picture
Moneyiar market data at 2026-10-08 09:34 +03:30 showed Polygon (prev. MATIC), now listed as POL, at $0.1016997872, down 0.73% over 24 hours and 9.19% over seven days. OriginTrail (TRAC) stood at $0.4019739998, down 0.15% in 24 hours and 15.29% over seven days. RedStone (RED) was $0.1523731942, up 1.23% over 24 hours but down 16.32% over seven days.
These market figures provide a snapshot of selected assets connected to the broader blockchain ecosystem at that time; they do not measure Polymarket’s migration progress or determine how individual positions will be handled.
