Polymarket Protocol V2 will not auto-convert CTF positions
Polymarket Protocol V2 canaries run through October 30, with a tentative November 2 switch for new markets. Existing CTF positions do not auto-convert.
Polymarket Protocol V2 is matching production canaries, and the new ledger does not take the old book with it. Head of protocol Rajath Alex wrote on October 5, 2026 that those markets run through October 30, with a tentative switch of net-new markets on November 2. The migration guide is narrower than that post: existing Conditional Tokens Framework (CTF) holdings are not converted, and an integration update does not move those balances.
A new engine for new listings is not a novation of open positions. Two ERC-1155 ledgers stay live on Polygon: PositionManager for Polymarket Protocol V2, and the 2019 Gnosis contract for markets already open. The contracts page adds what the post omits. Migration is implemented on BinaryModule and NegRiskModule, but only after Polymarket registers that condition or event. Nothing opened here makes registration automatic, or dates it to November 2.
What the new contracts replace
Alex described the legacy stack as 2019 Gnosis code plus a later contract per market type: a pUSD adapter, wrapped neg-risk collateral, a second exchange and a separate UMA adapter. He called Polymarket Protocol V2 "a rebuild of that foundation, from the position token up": one ERC-1155 positions contract, Polymarket USD (pUSD) as sole collateral, one exchange for every market type and one router. The contracts page lists one PositionManager, one ExchangeV3 and one Router on Polygon, chain ID 137, beside the two CTF exchanges.
The post names four opening types: binary, atomic neg-risk, incremental neg-risk and combinatorial. The positions guide publishes three modules: BinaryModule (ID 1), NegRiskModule (ID 2) and CombinatorialModule (ID 3). It does not say how the two neg-risk types share NegRiskModule. The ID's first byte is the module and its last byte is the outcome, 0 for YES and 1 for NO. A CTF token ID must not go to PositionManager, or a V2 ID the other way.
Resolution runs through OracleAggregator, which Alex said can plug into UMA, Chainlink and later oracles. The contracts page also lists an optimistic-oracle reporter, a Chainlink reporter and an externally owned account reporter, and says the aggregator delivers the result to the owning module. Bridging is designed and not live. He put activation at "when we do go multi-chain."
Collateral and the approval reset
Polymarket's collateral page calls pUSD a standard ERC-20 on Polygon, backed by USDC, enforced onchain, with no fractional reserve. It says trading settles in native USDC, while the documented wrap and unwrap take USDC.e, and it prints no mint ratio. Unchained describes pUSD, from the April collateral change, as redeemable 1:1 for Circle's USDC. The wrapper does not rewrite issuer terms, including delays Circle's terms can put on a European USDC redemption.
App and website users need no technical migration beyond approval prompts. Integrators do. The contract migration note says CTF approvals do not carry over. Splits need a fresh pUSD approval for the Router; merges and redemptions need PositionManager operator approval for it. Buys approve ExchangeV3 to spend pUSD, including fees, and sells approve it as operator. Orders use EIP-712 domain version "3". Mints skip ERC-1155 receiver callbacks. On the router, 1,000,000 base units equal one pUSD, or one share.
"Polymarket currently runs on smart contracts that were never designed for what it became," Rajath Alex, head of protocol at Polymarket, wrote in the October 5 post.
He put the critical-finding bounty at up to $5 million. The contracts page links Cantina, Certora, Quantstamp, SigmaPrime, Zellic and Pashov, including reports from April 2026 to August 2026 and Certora formal verification. A review is not a custodian sign-off.
Two clocks, neither a conversion
November 2 is tentative, and it covers net-new markets only. The migration docs opened here do not restate the canary window. Polymarket's Data API migration note says Data API v1 is retired on October 24, 2026, and leaves the accounting snapshot route on v1. The October 5 post introduces Data API V2, a Rust service on an in-house indexer, and does not print that date.
Two live ledgers are not a shutdown. Blast is winding down an Ethereum layer 2 because cost exceeded revenue, while Polymarket is keeping the 2019 contracts so open positions are not forced across. The approval reset is a Polygon permission, not FinCEN's withdrawal of the unhosted-wallet rule, and not Summer Mersinger stepping down at the Blockchain Association.
The tidy rollout fails if November 2 still opens markets on CTF, if a named open market is never registered, or if the docs drop "tentative." Until then, old tokens stay put.
This article is informational analysis only and is not financial, investment, or trading advice. Cryptocurrencies are highly volatile and can lose substantial value rapidly. Past performance and historical patterns do not guarantee future results. Do your own research and consult a regulated financial adviser before making any investment decision.
Reporting by Karthik Subramanian. Filed 7 October 2026, 08:04 GMT.
Digital Assets Correspondent
Karthik Subramanian is a founder, writer, and technology consultant with nine years in the crypto ecosystem.
