• A proposal put to Polygon’s community would use a to move 70.49 million POL into recovery wallets.
  • The are tied to what the reporting calls the Polymarket and Binance incidents. The total supply of POL would not change.
  • This is a proposal. Nothing has been forked yet, and headline framing elsewhere blurs that distinction.

Changing who owns what on a is supposed to be the one thing nobody can do. A proposal now circulating in Polygon‘s community would do exactly that for 70.49 million POL, moving the tokens into recovery wallets by way of a hard fork.

Blockchain balances get described as immutable, as though the record were a law of physics. In practice it’s an agreement between the people running the software, and when enough of them agree to rewrite a balance, the balance gets rewritten. This proposal is a live example of where that line actually sits.

For anyone holding POL, the narrow practical point is that nothing here changes the number of tokens in existence. It isn’t a burn and it isn’t new issuance. What would change is control of one specific pile of them.

What a hard fork actually is

Black and white image of railway tracks converging at a station, symbolizing travel and journeys.
Railway tracks converging at a station. A hard fork is the point at which a blockchain’s history can split onto separate paths. Photo by Sophie Dale on Pexels.

Every machine helping to run a blockchain is executing software with a shared set of rules: what counts as a valid transaction, what counts as a valid block. A hard fork is a change to those rules that older software will refuse to accept. Everyone has to upgrade. Anyone who doesn’t carries on validating a separate version of history, which is how one chain quietly becomes two.

Most hard forks are unremarkable. They’re scheduled upgrades, agreed months in advance, and the only people who notice are the ones running nodes.

A fork that reassigns specific balances is a different category of thing. The rules of the network aren’t really what’s being altered. The ledger is. That’s why these proposals attract the argument they do, regardless of how sympathetic the reason behind them.

Ethereum did this in 2016, and the chain split

The precedent most readers half-remember is The DAO. In June 2016 an attacker drained roughly 3.6 million ETH from a fund built on Ethereum. The following month the network hard-forked to move the funds somewhere investors could reclaim them. A minority refused to upgrade, kept validating the original chain, and that chain survives today as Ethereum Classic. One decision, two networks, two tokens.

The comparison is useful but not exact. Ethereum in 2016 was barely a year into mainnet with a small and ideologically tight community. Polygon now is a larger, more commercial network with considerably more parties who would lose money in a split. Our own reading is that this cuts both ways: more pressure to make users whole, and more pressure not to fracture the chain doing it. That’s an inference on our part, not something stated in the proposal.

Where the evidence stops

We worked from The Defiant’s write-up and could not locate the underlying governance post, the proposal text, or any on-the-record statement from Polygon, Binance or Polymarket about it. There is no quotation in this article because nobody involved has been quoted in the reporting we have. Treat the specifics, including the breakdown between the two incidents, as the aggregator’s account rather than as confirmed detail.

What the proposal does not say

Moving tokens to a recovery wallet is not the same as getting them back to the people who lost them, and the two steps are easy to collapse into one when reading a headline. A recovery wallet is a holding pen. Whether anyone is ever made whole depends on three things that aren’t settled here.

Who holds the keys to those wallets. Whether there’s a claims process, and who adjudicates it. And whether the set would need to vote on the fork formally, at what threshold, with what happens if a minority declines to upgrade.

There’s a broader point buried in that. Holding your own keys protects you from an exchange failing, which is the risk most people are told to worry about and the one our guide to self-custody deals with. It doesn’t protect you from the ledger itself being amended. That’s a rarer risk and a stranger one, and it only exists because somebody has the social authority to coordinate an upgrade.

We’ve deliberately not put a dollar figure on 70.49 million POL. Any number depends entirely on which moment you price it at, and the current POL price will tell you more than a stale conversion would.

What to watch

Whether this reaches a formal governance process with a published document attached, rather than remaining a discussion. That’s the point at which the detail becomes checkable.

After that, two things. Whether validators publicly signal support, since a fork with meaningful dissent is how a chain splits. And whether anyone publishes a route from recovery wallet back to the people affected. Without that second one, 70.49 million POL has simply changed address.