Polymarket’s upgrade won’t automatically move existing bets to new contracts

Polymarket’s Protocol V2 rollout doesn’t automatically move existing bets held beneath its older Conditional Tokens Framework, or CTF, onto new contracts. Its migration guidance tells buying and selling integrations to retain assist for these holdings whereas including a separate system for V2 positions and new buying and selling permissions.

In his Oct. 5 announcement, Rajath Alex stated Polymarket would run just a few reside check markets, often called canary markets, from Oct. 5 via Oct. 30. He described Nov. 2 as a tentative swap for newly created markets, reasonably than a deadline for changing each existing guess.

For folks utilizing Polymarket’s app or web site, no technical migration is required. Users ought to full any approval prompts proven within the app. The guides deal with 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 move CTF positions into V2. Polymarket’s contract registry says the related situation or occasion have to be registered by Polymarket first. Its indexing reference describes occasions connecting the outdated CTF steadiness to the new PositionManager steadiness. That is a definite operation from updating buying and selling software program.

Integrations should assist each programs

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. Under the API migration guide, the account holding a V2 purchaser’s belongings should authorize ExchangeV3, the new buying and selling contract, to spend sufficient pUSD, Polymarket’s buying and selling collateral, to cowl purchases and charges. Selling requires permission for ExchangeV3 to function on the vendor’s PositionManager shares. Existing CTF permissions don’t grant both approval.

Trading software 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 change and signing-domain model 2. Those signing variations distinguish the 2 buying and selling paths. Balance requests additionally distinguish V2 shares from CTF shares.

For integrations that create, mix or redeem positions immediately via 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 want to replace steadiness dealing with and payout reads.

The related model labels refer to totally different upgrades. Polymarket’s changelog data CLOB V2 going reside on April 28 and Data 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 nonetheless tells builders to confirm purchases, gross sales and balances on each a V2 market and a CTF market.

The submit Polymarket’s upgrade won’t automatically move existing bets to new contracts appeared first on CryptoSlate.