Migration Guide
    2026-04-27T22:08:00Z10 min read

    What Changes With Polymarket V2 on April 28, 2026

    A one-hour outage, a new collateral token, and some real migration work for API traders. Here’s what retail users, builders, and market makers actually need to know.

    Cutover

    2026-04-28

    Downtime

    ~1 hour

    Collateral

    USDC.e → pUSD

    Open orders

    Canceled

    Quick Summary

    The key takeaway from this page

    Retail users mostly face a short outage and a one-time approval flow, while API traders and builders need to migrate to the V2 stack before cutover. The important distinction is between what changes mechanically—collateral, order flow, SDK compatibility—and what does not, including existing positions and the broader regulatory picture.

    Cutover snapshot

    The outage window, correction history, and the fastest practical summary

    The Polymarket V2 cutover window (~11:00 UTC on 2026-04-28) has passed.

    Date correction history

    This cutover was originally announced for April 22, 2026, then silently revised by Polymarket to April 28, 2026 between April 17 and April 19 without a public announcement. On April 22, a live-industry signal briefly suggested the cutover was reverting to the original April 22 date; a primary-source re-fetch at 17:29 UTC that same day re-confirmed Polymarket’s own docs still state April 28, 2026 at ~11:00 UTC. The confirmed date is April 28.

    This page maintains the full correction audit trail in the underlying data file. Primary source: docs.polymarket.com/v2-migration.

    30-second answer

    If you’re a retail user:

    • Polymarket will be offline for ~1 hour starting ~11:00 UTC on 2026-04-28 (~07:00 ET).
    • Your funds and positions are safe. No action is required beyond a one-time “approve” click when you next log in.
    • Your USDC.e balance converts 1:1 into pUSD.

    If you use the API or run a bot:

    • Migrate to the V2 SDK before 2026-04-28 or your orders will stop working.
    • All open limit orders will be wiped at cutover.

    Auto-redemption is now live

    Auto-redemption of winning positions is now live on Polymarket. You no longer need to manually click through each resolved market to collect—your winning position balance updates automatically after resolution. Manual redemption still works for any pre-existing positions that predate the rollout.

    The timeline

    The dated milestones around the migration and what each one signals

    2026-04-06

    Polymarket announces 'full exchange upgrade' including pUSD and CTF Exchange V2

    2026-04-17

    Initial cutover date reported as April 22 ~11:00 UTC, ~1 hour downtime

    2026-04-19

    Cutover date CORRECTED: April 28 ~11:00 UTC (was April 22 in earlier docs, silently revised by Polymarket between Apr 17 and Apr 19)

    2026-04-22

    AM commit briefly reverted page to April 22 based on live-industry signal without re-fetching primary source. Afternoon re-fetch of docs.polymarket.com/{changelog,v2-migration} at 17:28–17:29 UTC re-confirmed April 28 ~11:00 UTC unambiguously; page corrected back to April 28.

    2026-04-28

    V2 cutover. V1 permanently decommissioned. Open orders wiped.

    What’s actually changing

    Mechanical changes worth tracking versus background facts that stay the same

    Three user types — what you actually do

    The migration work is different for retail frontends, API traders, and builders

    Retail user via the Polymarket website or app

    Estimated effort: 30 seconds

    Before cutover:

    None required

    At cutover:

    One-time approve transaction for pUSD wrap on next login

    API trader or bot operator

    Before cutover:

    1. Install @polymarket/clob-client-v2 (npm) or py-clob-client-v2 (pip)
    2. Remove legacy clob-client / py-clob-client packages
    3. Update SDK constructor from positional args to options object; rename chainId to chain
    4. Remove feeRateBps, nonce, taker from order creation code
    5. If signing orders manually, update verifyingContract and Order fields; bump EIP-712 domain version from '1' to '2'
    6. Test against clob-v2.polymarket.com before the cutover date

    At cutover:

    Open orders will be wiped. SDK hot-swap auto-refreshes to V2 endpoints.

    Builder / integrator (attribution-based)

    Before cutover:

    1. Copy builderCode from Polymarket Settings, Builder tab
    2. Attach builderCode to orders going forward
    3. Remove builder-signing-sdk dependency (no longer needed; attribution is native)

    At cutover:

    None beyond the SDK migration above

    The pre-cutover week in context

    The migration now sits inside a broader regulatory week, not a same-day catalyst pileup

    The cutover now sits inside a regulatory week, not a same-day catalyst stack. These are the dated items around it:

    2026-04-21 10:00 ET

    Kevin Warsh Senate Banking confirmation hearing (Fed Chair nominee)

    Polymarket/Kalshi pricing of Fed-chair confirmation + rate path referenced by press. Separate week from V2 cutover.

    Read more
    2026-04-28 07:00 ET

    Polymarket V2 downtime begins (~11:00 UTC per dev docs)

    ~1-hour outage. Kalshi and ForecastEx unaffected. Note: Polymarket help-center FAQ states a 7:00 AM UTC pause / 8:00 AM UTC resume window that contradicts the dev-doc 11:00 UTC timing on the same help-center page's own Key Details section. Treat dev-doc 11:00 UTC as authoritative; monitor status.polymarket.com on the day for the actual start.

    2026-04-29 13:00 ET

    NCSL Town Hall: Prediction Markets

    State legislators' coordinated policy discussion one day before the federal comment window closes.

    Read more
    2026-04-30 EOD

    CFTC ANPRM public comment period closes (RIN 3038-AF65)

    Federal event-contract rulemaking input phase closes.

    Read more

    If you rely on Polymarket pricing for news reactions, the site will be unavailable for ~1 hour mid-morning on 2026-04-28. Kalshi and Interactive Brokers ForecastEx are not affected.

    Caution — what this page is not

    Important boundary lines so the migration story does not get confused with token speculation or scam bait

    • This is not a POLY airdrop guide. Polymarket has not announced a POLY token launch. The V2 upgrade is separate from any governance-token plans.
    • This is not investment advice on pUSD. pUSD is a platform collateral token, not a tradable speculation asset. It is not listed on exchanges.
    • Scam warning: Anyone asking you to “airdrop your wallet for POLY” is likely a scam. Never sign transactions from third-party sites claiming to distribute POLY tokens.

    Source transparency

    Why this page uses primary-source migration docs rather than recycled crypto-blog summaries

    Source transparency: All mechanical facts on this page come from Polymarket’s own changelog and V2 migration documentation. Secondary journalism and crypto-blog syndications are excluded from citation by editorial policy. Primary-source links are provided inline where available; any pending primary-source verification is noted in the data layer and will be completed by our verification process. Last verified: 2026-04-27T22:08:00Z.

    Frequently Asked Questions

    8 common questions answered

    Continue exploring