Skip to main content
Hardfork activation timestamps and block heights for Polygon Chain (Bor and Heimdall). Failing to update client software before the specified activation point may result in chain divergence, requiring a full resynchronization. The upgrade naming scheme follows the order of release on the Polygon network.

​
Activations

​
Upgrade process

Network upgrades follow a general process: features are included in a release version cut from the develop branch, then deployed on production networks.
Diagram omitted (missing source asset in this repo).

​
1. Proposal and governance approval

Significant protocol changes, including hardforks, are proposed and approved through Polygon governance:
  • Submit a Polygon Improvement Proposal (PIP).
  • Community discussion and feedback.
  • Onchain voting to pass the proposal.

​
2. Development and testing

Once a proposal is approved:
  • Code is developed and reviewed.
  • Testing is conducted on devnets and testnets.
  • Smart contracts and Layer 2 infrastructure are upgraded.

​
3. Node and software upgrades

Before the hardfork activation timestamp, validators and node operators must update their software. Failure to upgrade may result in chain divergence.

​
4. Hardfork activation

  • The upgrade activates at a specific block height or timestamp.
  • Nodes that fail to update before activation risk being left on an outdated chain.

​
5. Post-hardfork monitoring

  • The network is monitored for stability after activation.
  • Bugs or issues are addressed through patches if needed.