Skip to content
EVENT / TOPICActive

Binance and Polymarket Seek Polygon Hard Fork to Recover Stolen POL

2 reports2 sources11/5/2026 updated

Current overview (not historical)

AI overview

Binance and Polymarket have proposed a Polygon hard fork to recover about 70.49 million POL tokens frozen after an October 30 attack on Polymarket's frontend and a Binance hot wallet, but the proposal has not been approved by Polygon governance and Polygon officials, PPGC members, and core developers have not publicly commented. Validators froze four Polymarket hacker addresses holding roughly 23.86 million POL and one Binance address holding roughly 46.63 million POL. Activation would require governance approval and testing on the Amoy testnet, with a mainnet discussion planned for November 5, 2026 and no fork date set. PANews said the proposal is unlikely to pass. Reports disagree on the stolen funds' value: Cointelegraph cited about $6.8 million, while PANews first cited about $6.7 million and later about $6.5 million.

Written with AI from the reporting · updated 11/5/2026

Expand the detailed fact route and sources

Story route

A station-by-station route from the first public evidence onward; every station carries its own evidence and uncertainty.

  1. 1Unclassified fact stationNov 5, 14:21report-time onlyrevised

    币安和 Polymarket 提议 Polygon 硬分叉追回约 680 万美元被盗 POL 代币

    Read original source ↗ CointelegraphReplay this moment in the explorer
    Evidence & revisions · 2 source records
    Subject:
    Binance 和 Polymarket
    Action:
    提议 Polygon 网络硬分叉以追回被盗代币
    Object:
    约 7049 万枚 POL 代币(价值约 680 万美元)
    Occurred (fact side):
    not recorded
    Cointelegraph ↗Report pageRevision 2 · currently revised
    Published (valid side):
    Nov 5, 14:02
    First seen (known side):
    Nov 5, 14:21
    PANews · Articles ↗Report pageOriginal / first version
    Published (valid side):
    Nov 5, 21:00
    First seen (known side):
    Nov 5, 21:27
    Fact stationRevisedReport-time only

    Copy may have been revised later; time replay is bounded. Layer labels group reading only, not causation between layers.

Uncertainty marks flag where to check the sources; they are not proven causation.

Report timeline

Explore every side through dated source reports.

Nov 5
  1. PANews · ArticlesFact occurrence time unverified
    Polymarket and Binance propose Polygon hard fork to zero about 70.49 million POL in hacker addresses

    Report first recorded Nov 5, 21:27

    On October 30, hackers breached Polymarket's frontend and Binance hot wallet; Polygon validators froze four Polymarket addresses holding 23.86 million POL and one Binance address holding 46.63 million POL, about 70.49 million POL, priced at about $6.7 million in the proposal though the article later says about $6.5 million. On November 5, Polymarket and Binance proposed a Polygon PoS hard fork to zero those hacker addresses and credit the same amount to designated recovery addresses, with a PPGC defense at 22:30 Beijing time. The hacker did not respond and allegedly offered to pay for unblocking. As of press time Polygon had no public stance and the article assesses passage as unlikely, citing Ethereum The DAO and Core Network as precedents while warning of reputational risk to immutability.

    Read original source ↗
  2. CointelegraphFact occurrence time unverifiedSource report revised
    Binance and Polymarket propose Polygon hard fork to recover about $6.8 million in stolen POL tokens

    Report first recorded Nov 5, 14:21

    Binance and Polymarket have proposed a Polygon network hard fork to recover roughly 70.49 million POL tokens worth about $6.8 million stolen in separate incidents. The fork would move funds from five attacker-controlled addresses to verified recovery wallets at a predetermined block without changing POL supply. The plan needs governance approval and Amoy testnet testing, with no mainnet date set.

    Read original source ↗

Event activity trend

Not enough continuous observations to chart activity.

Event discussion

Reader opinions are hosted on GitHub Discussions; posting requires a GitHub account. Comments are not verified facts.

Open GitHub Discussions