Polygon Proposal Seeks Hard Fork to Recover 70.49 Million POL
- Published
- Updated
- Since then
- 11 new reports
- In
- Governance
Polygon is weighing a hard fork that would move about 70.49 million POL from five attacker-controlled addresses into recovery wallets tied to Binance and Polymarket. The proposal keeps POL’s total supply unchanged and has governance discussion scheduled for Nov. 5.
Key claims & sources
What it means
Polygon validators already froze the stolen POL at the protocol level, a power most base-layer chains reserve for extreme cases. The precedent most readers will recall is Ethereum's 2016 DAO fork, which split the chain to reverse a theft rather than let 'code is law' stand. Polygon, built on a proof-of-stake validator set rather than miners, can coordinate a client upgrade far faster, which is exactly what this proposal tests only nine years later.
If adopted, validators must run new client software that zeroes out balances in the five attacker addresses and credits the same 70.49 million POL to wallets controlled by Binance and Polymarket. Node operators who refuse the upgrade stay on the old chain, splitting the network in two. Binance and Polymarket recover funds without waiting on courts or bridges; every other holder now knows a sufficiently coordinated validator set can rewrite their balance too.
A blockchain that can quietly reassign tokens to favor two well-connected victims is not the same product as one that guarantees no one, including its own operators, can touch a balance. Supporters frame this as consumer protection after theft; critics see a governance body picking winners, with smaller hack victims unlikely to get the same treatment. Both readings are legitimate, and the proposal itself concedes the tension by calling it a one-time, supply-neutral exception rather than a new norm. (per cryptobriefing.com)
Polygon's governance discussion on Nov. 5 will show whether validators and token holders back the fork or stall it over the immutability objection. A yes vote sets a recovery mechanism other chains facing large thefts may now feel pressure to copy; a no vote leaves Binance and Polymarket's funds frozen but unrecovered, and reaffirms that even block producers won't unilaterally rewrite balances.
Market reaction i
The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 2 months ago | Duelbits · Hot Wallet Key Compromised incident | $7M |
| 10 months ago | Saga · Infinite mint incident | $7M |
| 1.2 years ago | ODIN.FUN · Price manipulation incident | $7M |
| 2.0 years ago | PolterFinance · FlashLoan attack incident | $7M |
| 2.8 years ago | GMEE · Contract vulnerability incident | $7M |
4285 incidents stored · 432 were as large as this one or larger ($7M)