0x0f5f619f0f5f…0f5f619c

ConfirmedSecurity514 vB119 sat/vB3 min decode

Polygon Proposes Hard Fork to Return $7M in Stolen POL to Binance and Polymarket

A Nov. 4 PIP proposes a Polygon PoS hard fork to zero five attacker addresses and return 70.49 million POL, about $7 million, stolen in the Binance and Polymarket breaches.

Polygon proposes hard fork to recover $7M in stolen Binance, Polymarket funds
WitnessPolygon proposes hard fork to recover $7M in stolen Binance, Polymarket fundsAaronJOlson / pixabay

Outputs

  1. PIP filed November 4, 2026 proposes a Polygon PoS hard fork to recover 70.49 million POL (~$7 million).

  2. Roughly 23.86 million POL traces to four Polymarket-linked addresses; 46.63 million POL to one Binance-linked address.

  3. Community discussion is set for the Protocol Governance Call on November 5, 2026, at 14:30 UTC.

  4. Amoy testnet validation is expected to take about two weeks before mainnet activation.

  5. The fork is supply-neutral: no POL is minted or burned, and USDT involved in the incidents is out of scope.

A Polygon Improvement Proposal (PIP) filed on November 4, 2026, calls for a hard fork of the Polygon Proof-of-Stake mainnet to recover roughly 70.49 million POL — about $7 million at current prices — stolen in the October 29–30 security incidents at Binance and Polymarket. The proposal would zero out five attacker-controlled addresses and credit matching balances to verified recovery accounts for each victim.

Parvez03, a member of the Polygon Labs validator support team, introduced the PIP. It describes an exceptional, one-off state change to the ledger rather than a routine protocol upgrade. The stolen funds break down as follows:

  • Approximately 23.86 million POL spread across four addresses tied to the Polymarket breach.
  • Approximately 46.63 million POL in a single address linked to the Binance incident.

The total supply of POL would not change. No tokens are minted and none are burned; the coins simply move from the thieves' addresses back to the entities they were taken from.

Frozen, but not finished

Polygon's block producers have already added the five addresses to a transaction denylist, which in principle prevents the funds from moving. The proposal's backers say the attackers have continued trying to extract the assets through high-fee transactions and alleged bribery of validators. That pressure is the operational argument for a permanent, fork-level resolution rather than reliance on a denylist.

The scope is deliberately narrow. The recovery covers only native POL still locked on Polygon PoS; other tokens involved in the incidents, including USDT, fall outside the proposal. Both Binance and Polymarket have already reimbursed most affected users from their own funds, so the fork is less about making individuals whole and more about recovering the remaining stolen assets stuck on-chain. For the two platforms, that makes this a balance-sheet matter: recovering the POL would offset costs already absorbed out of pocket.

Developer teams have stressed the measure is extraordinary and not intended to set a precedent for future incidents.

What does the fork change for POL holders?

The supply-neutral design removes the most obvious holder concern. Because no POL is created or destroyed, the fork does not dilute existing holders — the returning tokens were already part of circulating supply. For validators and node operators, the practical question is operational: a hard fork requires coordinated client upgrades across the network, with all the synchronization risk that entails.

The deeper tension is immutability. Confirmed transactions on a public blockchain are supposed to stay confirmed. Polygon's framing manages that tension by routing the intervention through formal governance, labeling it exceptional, and leaving total supply untouched — a bounded correction rather than a new habit, at least as presented to the community.

The timeline from here

The community is scheduled to discuss the PIP at the Protocol Governance Call on November 5, 2026, at 14:30 UTC. If it receives approval, client development and validation on the Amoy testnet are expected to take roughly two weeks before the state change could ship to mainnet — placing a potential activation window in late November 2026.

via Crypto Briefing (Source)

More from Nathan Brooks

Nathan Brooks

Show full bio

Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

751 articles