KOSUNI CRYPTO
Korea's Crypto Pulse, in English
$BTC $ETH $XRP $SOL $DOGE
Exchanges
Neutral

Polymarket's New System Doesn't Automatically Migrate Existing Bets

Published October 7, 2026 10:40 PM · 6 views $POLY
Polymarket's New System Doesn't Automatically Migrate Existing Bets

Polymarket's new trading system is now live, but existing bets will not be automatically migrated to the new contracts. Existing positions remain in the legacy CTF system while new positions are recorded in V2's PositionManager, meaning app users and integrated services must prepare differently.

Polymarket Protocol lead Rajath Alex announced Protocol V2 on X on October 5. Following the restructuring of the protocol's architecture, this migration requires a separate process to move existing positions to new contracts. General users who access Polymarket via app or website do not need to perform technical transfers—only approve any displayed requests. However, approval alone does not transfer existing bets to V2 positions.

To migrate an existing position, users must first register the condition in the new system before manually moving it. Positions cannot be transferred if conditions are not registered in the new contract. Polymarket's V2 migration documentation outlines this procedure.

Services directly connected to contracts via API or dashboards, such as trading bots or dashboards, must continue supporting legacy CTF position identifiers while adding V2 PositionManager identifiers. Buy and sell signatures and permissions must also be kept separate. Existing approvals granted to CTF do not cover V2 asset trading permissions.

For buys, users must approve ExchangeV3—V2's trading contract—to use collateral pUSD and fees. For sells, ExchangeV3 requires permission to process positions recorded in PositionManager. Services creating or consolidating positions need Router permissions as well.

Since both legacy CTF and V2 contracts operate concurrently, integrated services must distinguish between the two systems when checking balances or processing orders. Polymarket's API migration documentation guides handling of both identifiers simultaneously.

This change does not involve migrating all open bets at once. Polymarket's public V2 contract repository separately addresses legacy CTF and NegRiskAdapter position migration features alongside the new PositionManager system. Rajath Alex mentioned on X that Canary Market testing will run until October 30, with a tentative switch date for new markets set to November 2.

Korean Source

This article is an English localization of a Korean-language crypto news report. Original headline: 폴리마켓, 기존 베팅 자동 이전 안 돼…앱 승인만으로는 부족