0x53764bb95376…53764bbc

ConfirmedInfrastructure672 vB115 sat/vB3 min decode

Polymarket Retires Gnosis Framework, Switches All New Markets to Protocol V2 on Nov 2

Polymarket retires the Gnosis framework it has used since 2019, moving all new markets to an audited Protocol V2 on Nov 2, with pUSD as sole collateral.

Outputs

  1. All new Polymarket markets move to Protocol V2 on November 2, 2026

  2. V2 replaces the Gnosis Conditional Tokens Framework used since 2019

  3. Canary test markets run October 5–30 before the full cutover

  4. Six audit firms, including Certora, reviewed the protocol; the bug bounty pays up to $5 million

  5. pUSD becomes the sole collateral and all positions consolidate into a single ERC-1155 contract

Polymarket will migrate every new market to its Protocol V2 architecture on November 2, retiring the Gnosis Conditional Tokens Framework that has powered the platform since 2019. The rollout, led by Polymarket's developers and protocol head Rajath Alex, began on October 5, 2026, according to the company's announcement.

The upgrade is the most consequential change to Polymarket's core infrastructure since launch. It replaces a borrowed framework with a system the company describes as unified, modular and audited — and it changes how collateral, positions, order routing and market resolution all work under the hood.

What changes under Protocol V2?

V2 consolidates position representation into a single ERC-1155 positions token contract. ERC-1155 is a token standard that lets one smart contract manage many different token types at once, so every outcome share across the platform will live in the same contract rather than being fragmented across per-market deployments.

The other components:

  • pUSD becomes the sole collateral. All positions on the platform will be backed exclusively by pUSD, replacing whatever collateral arrangements the Gnosis-based system allowed.
  • Market-specific exchanges with a router. Each market gets its own exchange, and a front-end router directs orders to the correct venue. Polymarket says the design improves user experience and operational efficiency.
  • Pluggable oracles. A new OracleAggregator component makes resolution sources interchangeable, supporting providers such as UMA and Chainlink on a market-by-market basis. Polymarket is no longer locked into a single method for deciding outcomes.

A staged rollout, not a hard fork

Polymarket is running the migration through canary markets — a limited set of live test markets — from October 5 through October 30. That window closes two days before the November 2 cutover for all new markets.

Existing markets built on the Conditional Tokens Framework will remain intact. Open positions will not be forcibly migrated mid-trade, which removes the most obvious source of user disruption: traders holding shares in legacy markets continue operating on the old stack until those markets resolve naturally.

Developers get their own upgrade in parallel. Data API v2 runs on an in-house on-chain indexer, meaning Polymarket now reads and organizes blockchain data itself rather than relying on outside tooling. The new API ships with standardized data formats and cursor-based pagination — practical improvements for anyone building dashboards, trading tools or analytics on top of Polymarket's data.

How did Polymarket handle security?

Six firms audited the protocol, including Certora. The company is also running a bug bounty that pays up to $5 million for critical vulnerabilities, a ceiling that puts the program in the top tier of DeFi bounty offers.

The audit count and bounty size signal that Polymarket is treating V2 as production-grade infrastructure rather than an experimental rewrite — a meaningful distinction given the platform's exposure to high-volume event markets.

What does this mean for traders, builders and rivals?

For traders, the pUSD-only collateral model concentrates all activity on a single asset, simplifying accounting and settlement across the platform. The operational benefit is straightforward: one collateral pool, one settlement path.

For builders, Data API v2 lowers the friction of third-party development. Standardized formats and dependable pagination reduce the integration work that previously made external tooling fragile.

For competitors, the pluggable oracle design is the strategically significant piece. By supporting UMA and Chainlink — and potentially other providers — Polymarket can match the resolution mechanism to the specific question each market poses, rather than accepting the constraints of a single oracle. That flexibility matters in a sector where resolution disputes have repeatedly damaged user trust.

The retirement of the Gnosis framework also closes a chapter: Polymarket has depended on that infrastructure for its entire history since 2019, and V2 is the first architecture the company fully controls end to end.

The dates to watch are October 30, when canary markets wrap, and November 2, when V2 becomes mandatory for every new market — the point at which Polymarket's operational reality, not just its roadmap, depends on the new stack.

via x.com (Original)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering industry trends and analytics at Mempool Brief.

435 articles