Polymarket Protocol V2 will not auto-convert legacy CTF positions
Polymarket will not automatically convert existing conditional tokens framework positions when its Protocol V2 goes live. Users with legacy CTF bets must manage them separately while new markets trade on the upgraded contract architecture. Canary testing runs through October 30 ahead of a tentative November 2 switch for new markets. Third-party integrations must handle both systems in parallel, and app users face new approval workflows.
Third-party developers building on Polymarket's infrastructure now face a hard port-or-perish choice. Teams that integrated with the legacy Gnosis contracts must rebuild their tools for V2's single-contract design or lose access to new market flows after the November 2 switch. The split system adds ongoing operational cost: every integration must handle parallel data streams until legacy positions close naturally.
Polymarket gains cleaner architecture for its institutional push, but the friction falls on external builders. The canary window through October 30 is the only live test period to validate those integrations. A failed port by a major market maker or brokerage would leave Polymarket's new infrastructure starved of liquidity at launch.