Polymarket is testing V2 with real markets
Polymarket has started a production canary for its rebuilt protocol. Traders may see new contract approvals, while builders must support two market systems during the transition.
Article
Polymarket has started testing a rebuilt trading system with real production markets.
This is not a demo. A limited group of markets is already using Protocol V2 during an October 5 to October 30 canary period. If the test holds, Polymarket tentatively plans to move new markets to V2 on November 2.
Existing positions stay on the old system. New V2 markets use different contracts and position identifiers.
That creates a short period where traders and builders need to understand both.
What changes for a normal user
Polymarket says app users do not need to move their existing positions.
The visible change may be a new smart-contract approval. Your wallet could ask for permission to use a V2 contract because the new market is not trading through the old exchange contract.
Read the contract address and permission before signing. A familiar website does not make a new approval meaningless.
Polymarket's head of protocol announced a production canary from October 5 to October 30, followed by a tentative November 2 switch for new markets.
Rajath Shashidhar (@0xrajath) · October 5, 2026
What V2 rebuilds
The new system changes several pieces at once:
- Position tokens: a market position now carries more routing information inside its token ID.
- ExchangeV3: V2 positions use a new exchange contract and signing domain.
- pUSD collateral: V2 markets use Polymarket’s dollar token as their sole collateral.
- Modular oracles: different oracle modules can be plugged into the system that resolves outcomes.
- A shared router: trades and position actions can move through one routing layer.
For a trader, most of this should stay behind the interface. For a market maker, wallet tracker or analytics tool, it is a real migration. Old assumptions about contract addresses and position IDs can return incomplete or wrong data.
Why the canary matters
A canary release puts a small amount of real activity through a new system before the full switch.
Polymarket says the contracts received audits and formal verification, and it announced a $5 million bounty for critical bugs. Those are useful safeguards. They are not proof that a live market cannot fail.
The canary is meant to expose problems while the affected surface is still limited.
What is still unclear
The reviewed announcement and migration guide did not provide a complete public list of the live V2 canary markets.
Polymarket also describes the new architecture as ready for multiple chains, but it has not announced another network or a cross-chain launch date.
The upgrade controls matter too. An upgradeable system can be fixed without replacing every contract, but whoever controls upgrades also holds meaningful power over the protocol.
What to watch before November 2
- Failed orders or incorrect balances on V2 markets.
- Wallet warnings about new approval targets.
- Integrators that still show only old-system positions.
- Any change to the October 30 canary end date.
- A final confirmation of the November 2 switchover.
The important story is not that Polymarket renamed its contracts. It is that real money is now testing the replacement before the rest of the market follows.
Sources and reporting notes
Checked October 6, 2026. The rollout dates, architecture, audits and bug bounty come from the protocol lead’s announcement. User and integrator migration requirements come from Polymarket’s V2 migration guide. Contract architecture and published addresses come from the official V2 repository. Cointelegraph independently reported the rollout.