The Ledger
Polygon Proposal Seeks Hard Fork to Recover About $6.5M in POL
A Polygon governance proposal targets native POL held at four Polymarket addresses and one Binance address. The plan calls for a fixed-block balance transfer after governance approval and recovery-address checks.

A Polygon governance proposal would move about 70.49M POL, valued indicatively at US$6.5M at US$0.0924 per POL on 29 October 2026, out of five blocked addresses and into recovery addresses designated by Polymarket and Binance. Published on 4 November by Parvez03, the proposal calls for a coordinated hard fork on Polygon PoS. At a specified activation block, it would set each listed address’s native POL balance to zero and credit the same amount to the relevant recovery address.
The proposal limits the change to native POL in four Polymarket addresses and one Binance address; other tokens and Binance Class B addresses are out of scope. Total supply would remain unchanged and Heimdall, the StakeManager and bridge contracts would not change, the proposal says. The proposal is scheduled for presentation at the Polygon Protocol Governance Call on 5 November 2026 at 14:30 UTC.
Even in a decentralized system, exceptional circumstances call for collective action through transparent governance and with community consensus.
Just
Four Polymarket addresses and one Binance address
About 28M POL was involved in the Polymarket incident on 29 October 2026, according to the proposal. The proposal identifies four blocked addresses holding about 23.86M POL of that amount. At 18:30:34 and 18:35:59 UTC, 3,282,275.71 POL moved from one listed address to another in two native transfers.
For the Binance incident, the proposal says Binance asked all validator-elected block producers to block an address on 30 October. In block 96,406,484, a Binance hot wallet sent that address 46,626,589.6 native POL and 6,185,900.1 USDT. Tether has frozen the USDT, leaving the native POL as the balance still at risk.
Why Polygon’s block list is a stopgap
Polygon PoS block producers added the addresses to Bor’s transaction block list at the affected parties’ request. Each producer reads its list only at startup, the proposal says, so changes require a deployment and a Bor restart or span rotation. Block-list entries have no automatic expiry.
The filter covers outer senders and EIP-7702 authorities, not every way an asset might be moved. The proposal records a pending transaction observed on 30 October with a fee of about 219,450 POL, or 10.45 POL per gas. The attacker also contacted validators offering cash to help unblock a transaction, according to the proposal.
Polymarket opened an on-chain recovery channel to the attacker through the SEAL Safe Harbor Recovery safe and received no response. The block list stops the funds from moving but cannot return them to their owners, the proposal says.
Approval, verification and a mainnet fork
Before activation, Polymarket and Binance must provide their recovery addresses in the proposal discussion, prove control of those addresses and confirm in writing that they are theirs to receive the funds. Polygon Labs will confirm the proof of control, the proposal says. The listed recovery addresses are specified in the PIP.
Activation requires approval through Polygon’s governance process, continued publication of the victims’ post-mortems consistent with the on-chain record, and block lists that remain in force until the fork. The proposal also requires the listed balances to be reread at a snapshot block and any differences from the table to be published.
After approval, the plan calls for client development and an Amoy deployment and rehearsal. The proposal describes about two weeks after approval as workable and one week as tight. Before the mainnet fork, validators, RPC providers and explorers would receive notice; Polygon validator operations expects about 70% to 80% of stake to reach the required software version quickly after release.
The change would break consensus on Bor, so validators, RPC providers, exchanges and node operators must run the new release before the activation block. Nodes that do not upgrade would follow a different chain from that block. The test plan requires an unupgraded node to reject the activation block and checks that no other account changes during the balance transfer.
Sources
- Original source Polygon Governance Forum forum.polygon.technology
Related stories
- Polygon PIP 93 Proposes Consolidating Multisigs and Adding a Timelocked Upgrade Route
- Polygon Labs Releases Bor v2.11.0 With Uburu Hardfork
- Bitquery traces $954,703 in stablecoins from Reental lending app
- Bitquery Reports $2.73M Lost Across 737 Polymarket Accounts
- Polymarket Restores Trading After One-Hour Third-Party Security Halt