What Is Being Proposed?
The funds come from two separate incidents on Oct. 29 and 30. A Binance hot wallet sent about 46.63M POL and 6.19M USDT to an attacker address, and Tether froze the USDT. Polymarket temporarily restricted trading after a third-party service provider was compromised, then reopened and said affected users would be compensated.
Plain-English version: Polygon’s four block producers added the attacker addresses to a block list, so the thieves can’t move the POL. But the tokens just sit there. Getting them back to their owners without the attacker’s private keys means changing the blockchain’s own rules at a set block, which is a hard fork.
The proposal also alleges that the attacker tried a transaction on Oct. 30 with a fee worth about 219,450 POL, and approached validators offering cash to help move the funds. Polymarket reportedly tried to contact the attacker on-chain without a response. Those are the proposal author’s claims.
How Would It Work, and What Are the Risks?
At a predetermined block, the five addresses would be set to zero and the same amounts credited to recovery wallets that Binance and Polymarket verify in writing. Polygon’s other contracts and past transactions would stay unchanged. Validators and node operators would have to install compatible software before the activation block, and the proposal flags a chain-split risk for any that don’t. No activation block or client release has been picked.
Why Is It Controversial?
Because it touches the principle that blockchain history shouldn’t be edited. Supporters see a narrow, one-time fix: the funds belong to known victims, the attacker’s addresses are already blocked, and the alternative is leaving the tokens frozen forever. For background, Ethereum’s 2016 DAO fork split the network into Ethereum and Ethereum Classic.
Critics raise the precedent. Coverage frames it as a question of how far a decentralized network should go to recover stolen assets, and a hard fork shows the validator set can change who owns what.
The comparison people are making is Arbitrum. On Oct. 30, its 12-member Security Council used a 9-of-12 emergency multisig to move about $30M in ETH and ARB out of an attacker-linked address, and the funds can now move only through a DAO vote. That fueled its own centralization debate. Polygon’s route is different: it requires validator adoption instead of a council vote, but it ends in the same place.
Why It Matters
The money is small compared with Binance’s $6.3B loss, but the question is bigger: when a chain’s validators can reverse a theft, what else can they reverse? Expect the argument to continue whichever way the vote goes. Watch today’s call, any formal PIP vote, and whether other chains with attacker funds follow the same path.
