A Polygon Improvement Proposal published on Nov. 4 requested a coordinated hard fork that would remove 70.49 million POL from five attacker-controlled addresses and re-credit equivalent balances to verified recovery wallets for Binance and Polymarket. The proposal is scheduled to be presented at Polygon’s Protocol Governance Call on Nov. 5, according to FXStreet.
The proposed chain-level change would replace an emergency blocklist measure that stopped the wallets from moving funds but could not return the assets. Any implementation remains dependent on approval.
Proposal would zero five blocked addresses and re-credit 70.49 million POL
Five blocked addresses would be emptied of their native POL under a coordinated hard fork outlined in a Polygon Community Forum proposal. Equivalent amounts would be credited to verified recovery wallets for Binance and Polymarket.
Of the 70,489,329.34 POL covered by the proposal, 46,626,593.27 POL is linked to Binance in one address and 23,862,736.07 POL is linked to Polymarket across four addresses.
Its stated purpose is narrower than a general blocked-wallet process: the proposal frames the change as recovery-specific. The listed recovery wallets do not mean the upgrade has occurred; the proposal is not itself an executed network upgrade.
Block producers’ freeze could stop movement but not restore assets
Polygon block producers blocked the addresses after separate security incidents on Oct. 29 and Oct. 30, the proposal says. That action prevented movement from the wallets, but it did not provide a way to transfer the locked POL back to its verified owners.
The proposal also describes the blocklist as operationally fragile. Maintaining it required block producers to continue enforcing the restriction, whereas the requested fork would directly alter the balances and remove the need for that stopgap.
Protocol Governance Call and two-week implementation estimate
The proposal was set for presentation at the Nov. 5 Protocol Governance Call. If approved, implementation was estimated to take roughly two weeks, covering client development and a rehearsal on the Amoy testnet.
That timetable is an estimate contingent on governance approval and the associated technical work. The planned Amoy rehearsal would precede any coordinated deployment of the recovery change.
