Polygon Giugliano upgrade takes effect on April 8, nodes act immediately

Polygon Foundation announced on April 7 that the Giugliano hard fork upgrade will officially go live at around 22:00 Beijing time on April 8, at Polygon mainnet block height 85,268,500. This upgrade is a mandatory node update: Bor node operators must upgrade to version v2.7.0, and Erigon node operators must upgrade to version v3.5.0.

Giugliano Upgrade: Three Key Core Improvements

This upgrade focuses on transaction confirmation efficiency and fee information transparency on the Polygon mainnet, bringing three structural improvements at the technical level:

Three Technical Upgrade Directions

Accelerated finality: Allows block producers (Producers) to declare blocks earlier, shortening the waiting time for transactions to reach final confirmation, directly improving on-chain transaction throughput efficiency

Fee parameters embedded in the block header: Fee-related parameters will be written directly into the block header, making fee information access more standardized and easier for developers to integrate

New RPC fee interface: Introduces a brand-new RPC interface to support real-time reading of fee data, providing developers with more complete fee query tools

The three improvements point to the same goal: Make the operation of the Polygon mainnet more efficient and more transparent for users, developers, and node operators.

Guidelines for Node Operators: Cutoff Block Height and Version Requirements

Polygon Foundation has clearly stipulated that all node operators must complete the upgrade before the mainnet reaches block height 85,268,500. Bor node operators must update to version v2.7.0, while Erigon node operators must upgrade to version v3.5.0—both are mandatory requirements.

The official warning states that nodes that do not complete the upgrade before the hard fork goes live will lose their ability to maintain synchronized connections with the mainnet and will be unable to continue operating normally. Node operators should immediately confirm the current software version and complete the corresponding update according to the official documentation, to avoid service interruptions after the upgrade block is reached.

Polygon Ecosystem Recent Developments: JPYC Stablecoin and Private Mempool Launch

Along with the Giugliano upgrade release, the Polygon ecosystem has shown several noteworthy developments recently.

According to data from the Alex platform, the cumulative total transaction volume of the Japanese fiat-backed stablecoin JPYC has reached $136 million, including $90 million in transactions settled through the Polygon network. These are mainly used by payment platforms such as Tria, Daimo, and CurrencyCompetition, reflecting Polygon’s real-world progress in stablecoin payment scenarios across Asia.

In addition, on April 2, Polygon officially launched the Private Mempool feature, providing a private transaction submission channel to protect each transaction from interference by front-running and sandwich attacks. Users only need to replace the RPC address with the corresponding private endpoint to enable the protection feature, with no additional steps required.

Frequently Asked Questions

What is the Polygon Giugliano upgrade?

Giugliano is a mandatory hard fork upgrade for the Polygon mainnet, scheduled to start at around 22:00 Beijing time on April 8 at block height 85,268,500. It brings three core improvements: accelerated finality, fee parameter transparency, and the addition of an RPC fee interface.

How should Polygon node operators handle this upgrade?

Bor node operators must upgrade to version v2.7.0, and Erigon node operators must upgrade to version v3.5.0. They must complete the update before the mainnet reaches block height 85,268,500. Nodes that do not upgrade on time will lose their synchronized connection to the mainnet after the hard fork goes live.

How do you use Polygon’s private mempool feature?

The Private Mempool has been live since April 2. Users only need to replace the RPC address with the private endpoint provided by Polygon to enable it—no other configuration is required. It can protect transactions from interference by front-running and sandwich attacks.