Polymarket’s transition to Protocol V2 will not automatically migrate existing bets from its older Conditional Tokens Framework (CTF) to the new smart contracts. According to the platform’s migration guidelines, trading integrations are instructed to maintain support for legacy CTF holdings while simultaneously integrating the separate V2 system and its new trading permissions.
In an announcement on October 5, Rajath Alex outlined the rollout timeline, stating that Polymarket will operate a limited number of live test markets, referred to as canary markets, from October 5 through October 30. He indicated that November 2 is the tentative date for switching over newly created markets, rather than a hard deadline for converting all legacy positions.
For end users interacting with the Polymarket application or website, no manual technical migration is necessary. Users simply need to complete any approval prompts that appear within the interface. Official documentation focuses on Polygon-based onchain trading, with separate guides provided for users of Polymarket US.
However, a manual migration mechanism is available for holders who wish to move their CTF positions to the V2 system. Polymarket’s contract registry specifies that the relevant condition or event must first be registered by Polymarket. The indexing reference then links the old CTF balance to the new PositionManager balance, a process that is distinct from updating trading software.
Integrations must support both systems
For developers and integrations, the core change lies in how shares are recorded. Legacy CTF positions remain on the older ledger, whereas V2 balances are managed within a separate contract called PositionManager. The contract migration guide mandates that integrations support both balance systems and retain CTF identifiers for older markets.
Access permissions also remain segregated. Under the updated API migration guide, an account holding a V2 buyer’s assets must explicitly authorize ExchangeV3—the new trading contract—to spend sufficient pUSD, Polymarket’s trading collateral, to cover purchases and transaction fees. Similarly, selling requires ExchangeV3 permission to operate on the seller’s PositionManager shares. Existing CTF permissions do not carry over to these new approvals.
Trading software must dynamically select the correct share identifier based on each market’s version, even if identifier fields for both generations are present in the API response. V2 orders utilize position IDs and signing-domain version 3, while CTF orders retain their original exchange and signing-domain version 2. These distinct signing versions separate the two trading paths, and balance queries must explicitly differentiate between V2 and CTF shares.
For integrations that directly create, combine, or redeem positions via smart contracts, V2 utilizes a Router contract. Creating positions requires Router approval to spend pUSD, while combining or redeeming positions requires Router operator permission on the PositionManager. Developers must also update their balance handling and payout read mechanisms accordingly.
It is important to note that these version labels refer to distinct upgrades. Polymarket’s changelog records CLOB V2 going live on April 28 and Data API v2 launching on September 4, both in 2026. The October Protocol V2 rollout introduces the separate position system detailed here.
For integrations already utilizing pUSD and the CTFExchangeV2 order format, existing collateral setups, wallets, order-book credentials, and endpoints remain unchanged. Nevertheless, Polymarket advises developers to thoroughly verify purchases, sales, and balances across both a V2 market and a CTF market to ensure full compatibility.
