Polygon replaced MATIC with POL for gas and staking

Polygon activated the MATIC-to-POL migration on September 4, 2024, making POL the native gas and staking token of the Polygon proof-of-stake network. The change reached the production network after community governance and a testnet rehearsal, replacing the token used to pay for transactions and secure Polygon PoS without requiring holders on that chain to perform a manual swap.

The development mattered because it changed a core dependency shared by users, validators, wallets, exchanges, bridges and decentralized applications. It was not merely a marketing rename. Polygon’s official launch notice said every Polygon PoS transaction from September 4 used POL for gas, while the staking system also moved to POL. At the same time, backward-compatibility measures were intended to keep existing applications operating through the transition.

What changed—and what did not

MATIC already located on Polygon PoS converted automatically. Polygon told those holders that no token-migration transaction was required. A wallet could nevertheless continue displaying “MATIC” if its network settings had not been updated, creating a visible naming mismatch even though the network’s native token had changed.

The treatment of MATIC on Ethereum was different. Holders could use Polygon’s Portal interface to exchange MATIC for POL at a one-to-one ratio. Polygon’s July 18 migration notice said there was no deadline for Ethereum or Polygon zkEVM holders as of September 4, although community governance could establish one later. It also said MATIC stakers and delegators on Ethereum did not need to take action for the staking transition.

Those distinctions limited the scope of any simple statement that MATIC had disappeared. The production Polygon PoS network had adopted POL, but MATIC balances elsewhere were not all automatically rewritten. Centralized-exchange customers also depended on each platform’s own implementation and communications.

The governance package behind the switch

Polygon Improvement Proposal 46 described the activation package as one backward-compatible transaction payload combining three earlier proposals. PIP-19 changed the Polygon PoS native token to POL. PIP-41 enabled direct POL emissions to the staking manager. PIP-42 upgraded proof-of-stake staking to use POL.

That record makes the September 4 event more precise than a ticker change: the migration connected the chain’s transaction-fee asset, staking machinery and token contracts. Polygon had tested the migration on July 17 before the mainnet change. The production activation therefore followed an announced sequence rather than an unplanned contract substitution.

The immediate utility was deliberately narrower than Polygon’s longer-term pitch. On September 4, verified functions were gas and staking on Polygon PoS. Polygon said later phases could give POL broader roles across its proposed AggLayer system, but those functions remained dependent on future community consensus. They should be read as a roadmap, not as capabilities completed on September 4.

Why the migration mattered

A native token sits in operational infrastructure. Validators need it for staking; users need it for fees; wallets need the correct symbol and metadata; and exchanges, bridges and applications must distinguish tokens by network and contract rather than by name alone. The migration therefore tested whether a mature blockchain ecosystem could alter that shared layer while preserving continuity for users and software.

The one-to-one conversion ratio also matters to interpretation. It defined an upgrade path between MATIC and POL, not an event-day market return. The surviving records do not establish that the migration itself caused any particular price move, trading volume or change in network usage, and this reconstruction makes no such claim.

Contemporaneous reporting on September 4 independently recorded that Polygon developers had put the migration live and that POL had become the Polygon PoS gas and staking ticker. The strongest evidence, however, is Polygon’s dated activation notice and the finalized governance specification. Together they establish a consequential protocol event while leaving future AggLayer utility, exchange timetables and market effects outside the verified event-day result.