Activations
| Upgrade | Forum | PIP | Activation |
|---|---|---|---|
| Delhi Hardfork | Link | PIP-7 | Block >= 38,189,056 on Polygon Mainnet (Bor) |
| Indore Hard Fork | Link | PIP-13 | Block >= 44,934,656 on Polygon Mainnet(Bor) |
| Aalborg Hard Fork | Link | PIP-21 | Block >= 15,950,759 on Polygon Mainnet (Heimdall) |
| Agra Hard Fork | Link | PIP-28 | Block >= 50,523,000 on Polygon Mainnet (Bor) |
Block >= 41,874,000 on Polygon Mumbai (Bor) | |||
| Napoli Hardfork | Link | PIP-33 | Block >= 54,876,000 on Polygon Mainnet (Bor) |
Block >= 5,423,600 on Polygon Amoy (Bor) | |||
| Ahmedabad Hardfork | Link | PIP-37 | Block >= 62,278,656 on Polygon Mainnet (Bor) |
Block >= 11,865,856 on Polygon Amoy (Bor) | |||
| Jorvik Hardfork | Link | PIP-53 | Block >= 22,393,043 on Polygon Mainnet (Heimdall) |
Block >= 5,768,528 on Polygon Amoy (Heimdall) | |||
| Danelaw Hardfork | Link | PIP-56 | Block >= 22,393,043 on Polygon Mainnet (Heimdall) |
Block >= 6,490,424 on Polygon Amoy (Heimdall) | |||
| Bhilai Hardfork | Link | PIP-63 | Block >= 22,765,056 on Polygon Amoy (Bor) |
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.