Polymarket Upgrade Leaves Existing Bets on Old Contracts
Polymarket says existing positions will not migrate automatically to new contracts, with app users facing approval prompts and integrations needing V2 identifiers.
Polymarket's contract upgrade will not automatically transfer existing bets to new contracts, according to the platform. Positions already placed will remain on their current contracts rather than being shifted over as part of the change.
What users and integrators face
- App users interact with approval prompts as part of the transition.
- Integrations need to retain support for CTF, the Conditional Tokens Framework, rather than dropping it.
- Builders must also add V2 identifiers and permissions to stay compatible.
The requirement to keep CTF support alongside new V2 identifiers suggests the upgrade is additive for third parties: existing infrastructure continues to function while newer components are introduced. For users, the approval steps determine how their positions and permissions are handled, rather than any automatic migration.
Prediction markets depend on contract-level accounting for open positions, so changes to underlying contracts typically require coordinated action from both end users and the developers whose products read or write to those contracts. Polymarket has not indicated a timeline in the source material.