Crypto exchange giant Binance and decentralized prediction markets platform Polymarket have taken joint action following a wave of late-October security breaches, officially petitioning the Polygon network to execute a targeted hard fork. The proposed intervention is designed to reclaim approximately 70 million Polygon (POL) tokens currently held in addresses controlled by the hackers responsible for the recent exploits.
According to a formal Polygon Improvement Proposal (PIP) submitted to the community, the two firms are asking the network to nullify the POL balances across five specific attacker-controlled wallets. Simultaneously, the proposal requests that identical balances be credited directly to secure recovery wallets managed jointly by Binance and Polymarket.
The targeted funds amount to roughly 70.49 million POL. Based on the valuation metrics utilized in the proposal, which reference market prices from October 29th, the stash is worth approximately $6.5 million. The compromised assets are split between two distinct incidents that occurred on the same day: roughly 23.86 million POL remains trapped across four addresses tied directly to the Polymarket hack, while an additional 46.63 million POL resides in a single address linked to the massive Binance security breach that unfolded late on October 29th.
In the immediate aftermath of the exploits, Polygon’s block producers acted swiftly to mitigate further damage by placing the rogue addresses onto a strict block list, effectively freezing the stolen assets and preventing the hackers from transferring them out of those wallets. However, both Binance and Polymarket emphasize that this defensive measure is merely a temporary stopgap rather than a permanent resolution.
As the proposal notes, while the current setup successfully prevents the funds from moving, nothing in the existing network architecture allows for those trapped assets to be legally returned to their rightful owners. Furthermore, the threat actor has shown persistent determination to bypass these security blocks. According to the proposal, the attacker has actively attempted to extract the funds by trying to bribe network validators with cash incentives in exchange for processing transactions and unblocking the restricted wallets.
To permanently neutralize the threat and restore the assets, the proposed
hard fork would serve as a definitive surgical remedy. Crucially, the protocol upgrade would leave Polygon’s total token supply entirely unchanged, ensuring no inflationary pressure or dilution occurs as a result of the recovery operation.
Executing such a drastic measure requires a strict, methodical protocol rollout. The intervention will only proceed if it successfully gains formal approval through Polygon’s established governance framework. Before any mainnet deployment, the hard fork code must undergo rigorous testing on the Amoy testnet. Additionally, Binance and Polymarket must provide cryptographic proof verifying that they hold absolute control over the designated recovery wallets destined to receive the reclaimed funds.
Both companies have acknowledged the extraordinary nature of the request, explicitly stating that a hard fork targeting specific user balances is an extreme action that should remain exceptionally rare and should not become a common practice within the blockchain ecosystem.
The recovery plan is scheduled for formal presentation at the upcoming Polygon Protocol Governance Call on November 5th at 14:30 UTC. Should the community vote in favor of the proposal and testing phases proceed smoothly, the rollout of the hard fork is expected to take approximately two weeks following final approval.
The Polygon network proposal follows an unprecedented sequence of security challenges across the digital asset sector. Binance reported that it has already successfully replaced the vast majority of the staggering $6.3 billion stolen from its hot wallets during the record-breaking October 29th security incident, even as recovery efforts and investigations continue on multiple fronts across the industry.

Comments (0)