Polymarket’s upgrade won’t automatically move existing bets to new contracts
Polymarket’s Protocol V2 rollout doesn’t robotically transfer present bets held below its older Conditional Tokens Framework, or CTF, onto new contracts. Its migration guidance tells buying and selling integrations to retain help for these holdings whereas including a separate system for V2 positions and new buying and selling permissions.
In his Oct. 5 announcement, Rajath Alex mentioned Polymarket would run a number of reside check markets, often called canary markets, from Oct. 5 by means of Oct. 30. He described Nov. 2 as a tentative swap for newly created markets, relatively than a deadline for changing each present guess.
For folks utilizing Polymarket’s app or web site, no technical migration is required. Customers ought to full any approval prompts proven within the app. The guides tackle Polygon-based onchain buying and selling; Polymarket’s main documentation directs customers of Polymarket US to separate documentation.
A separate mechanism does enable holders to maneuver CTF positions into V2. Polymarket’s contract registry says the related situation or occasion should be registered by Polymarket first. Its indexing reference describes occasions connecting the outdated CTF stability to the brand new PositionManager stability. That could be a distinct operation from updating buying and selling software program.
Integrations should help each techniques
For builders, the change begins with the place shares are recorded. Legacy CTF positions stay on the older ledger, whereas V2 balances sit in a separate contract known as PositionManager. The contract migration guide requires integrations to deal with the suitable balances and retain CTF identifiers for older markets.
Permissions additionally keep separate. Underneath the API migration guide, the account holding a V2 purchaser’s belongings should authorize ExchangeV3, the brand new buying and selling contract, to spend sufficient pUSD, Polymarket’s buying and selling collateral, to cowl purchases and costs. Promoting requires permission for ExchangeV3 to function on the vendor’s PositionManager shares. Present CTF permissions don’t grant both approval.
Buying and selling software program should choose the proper share identifier from every market’s model, even when each generations’ identifier fields seem within the response. V2 orders use place IDs and signing-domain model 3; CTF orders retain their alternate and signing-domain model 2. These signing variations distinguish the 2 buying and selling paths. Stability requests additionally distinguish V2 shares from CTF shares.
For integrations that create, mix or redeem positions immediately by means of contracts, V2 makes use of Router. Creating positions requires approval for Router to spend pUSD; combining or redeeming them requires Router operator permission on PositionManager. Integrations additionally must replace stability dealing with and payout reads.
The same model labels check with totally different upgrades. Polymarket’s changelog information CLOB V2 going reside on April 28 and Information API v2 launching on Sept. 4, each in 2026. The October Protocol V2 rollout provides the separate place system.
For integrations already utilizing pUSD and the CTFExchangeV2 order format, collateral, wallets, order-book credentials and endpoints keep the identical. Polymarket however tells builders to confirm purchases, gross sales and balances on each a V2 market and a CTF market.
