Polygon Sets Giugliano Hard Fork for April 8 Mainnet Upgrade

Polygon Sets Giugliano Hard Fork for April 8 Mainnet Upgrade

According to Polygon Foundation, the Giugliano hard fork will activate on April 8 to improve Polygon finality, with Amoy testnet results indicating final confirmation time was reduced by about two seconds.

Fact Check
The core of the statement is supported by two independently fetched reports: PANews and BlockBeats both say Polygon Foundation announced the Giugliano hard fork for April 8 on Polygon mainnet, with activation around block 85,268,500, and both describe the upgrade as improving finality. PANews and BlockBeats therefore support the main timing and purpose of the upgrade. In addition, media_trace on the Odaily link identified a The Block article as the upstream source, which is consistent with the user-provided The Block link, though that page could not be fetched here. However, the narrower detail that 'Amoy testnet results indicated final confirmation time was reduced by about two seconds' was not confirmed by any fetched source in this run. Because the main claim is corroborated but the specific performance-number detail is unverified, the overall statement is best assessed as likely true rather than fully confirmed.
    Reference
Summary

Polygon Foundation said in an official announcement that the Giugliano hard fork will activate on Polygon mainnet on April 8 at block height 85,268,500, around 14:00 UTC. The upgrade is intended to improve finality speed, and tests on the Amoy testnet showed final confirmation time was reduced by about two seconds. The foundation also said node operators must upgrade Bor to v2.7.0 or Erigon to v3.5.0 before the fork.

Terms & Concepts
  • Hard fork: A blockchain network upgrade that changes protocol rules and requires node software updates to stay compatible.
  • Finality: The stage at which a blockchain transaction is considered confirmed and effectively irreversible.
  • Amoy testnet: Polygon’s test network used to trial upgrades and measure their effects before deployment on mainnet.