Loading prices…
🔥BULLISH

POL Recovery: Polygon Plan to Sweep 70M From Hack Wallets

The plan would zero five addresses through a network rule rather than signed transfers, handing recovery authority to governance and validators while leaving total supply untouched.

POL Recovery: Polygon Plan to Sweep 70M From Hack Wallets
POL Recovery: Polygon Plan to Sweep 70M From Hack Wallets

Polygon's November 4 proposal would move roughly 70 million POL out of five hack-linked wallets without their holders signing anything. The recovery would wipe each listed address's balance at a future activation block and credit the same amount to company-designated recovery addresses, all through a rule written into the upgraded software itself. About 24 million POL is attributed to four Polymarket-linked addresses and 47 million POL to a single Binance-linked address.

Why it matters

The design shifts recovery authority to a combination of governance approval, the specified address list and the software rule validators adopt, bypassing the private keys that control the stolen funds. That is a notable precedent: a chain rewriting balances through a hard fork rather than negotiating with attackers or freezing assets at the token contract level.

The proposal itself flags the risks. Full balances move at activation, so later deposits into the five addresses would be swept too even if they came from legitimate users, and misidentifying an attacker-controlled address could confiscate a legitimate balance. Recipient addresses require proof of control, such as a signed message or test transfer, confirmed by Polygon Labs.

Market impact

For exchanges and custodians, the sweep creates a balance that no ordinary transaction explains, forcing explorers, indexers and accounting tools to reconcile a transaction-free change. An Amoy testnet rehearsal and a mainnet-fork replay are planned, with the change and a verification script to be published after activation.

Trader compensation stays separate: Polymarket said 95% of affected wallets were refunded on October 30, with $4 million returned, including $1 million for pause-related losses. The fork itself still needs a governance decision, a final software specification and an activation block, none of which are locked in yet.

Related tokens
$POL

Frequently asked questions

  1. How would Polygon move 70 million POL without the wallet holders' signatures?

    The recovery would be written into upgraded software that reads each listed address's balance just before activation, sets it to zero and credits the same amount to a designated recovery address. No signed transfer from the source wallets is required.

  2. Which hack-linked addresses does the Polygon recovery proposal cover?

    It targets five addresses: four linked to stolen funds from prediction market Polymarket holding about 24 million POL, and one linked to an exchange incident at Binance holding about 47 million POL.

  3. Does the POL sweep change Polygon's total token supply?

    No. Total supply stays the same because the coins are only moved between addresses. Earlier chain history also remains intact, and the design still requires confirmation from Bor engineering.

  4. What risks does the Polygon proposal itself acknowledge?

    The full-balance rule means later deposits into the five addresses would be swept too, even legitimate ones, and misidentifying an attacker-controlled address could move a legitimate balance. Recipient addresses need proof of control confirmed by Polygon Labs.

  5. How is Polymarket's customer refund program related to the POL recovery fork?

    They are separate processes. Polymarket said 95% of affected wallets were refunded by October 30, returning $4 million including $1 million for pause-related losses, while the proposed fork would return assets to company-designated recovery addresses rather than individual traders.

Source attribution
Aggregated from CryptoSlate · Verified · Last refreshed 38m ago
Open original →