Polygon Activates Giugliano Hardfork Wednesday, Reviving a Feature That Failed in Production Last Year
Polygon PoS is scheduled to activate its Giugliano hardfork at block 85,268,500 on April 8, 2026 at 2:00 PM UTC, bundling two protocol changes that target block propagation speed and gas fee transparency.

Polygon PoS is scheduled to activate its Giugliano hardfork at block 85,268,500 on April 8, 2026 at 2:00 PM UTC, bundling two protocol changes that target block propagation speed and gas fee transparency. The upgrade is notable for a specific reason: one of its two components was already attempted on mainnet in July 2025, caused enough problems to be rolled back, and has now been revised and reintroduced.
What the Hardfork Changes
Giugliano (PIP-84) packages two separate improvements to the protocol.
The first, PIP-66, addresses a gap between when a primary validator finishes assembling a block and when it actually broadcasts that block to the network. Currently, primary validators wait out the full two-second block interval before announcing, even though block assembly typically finishes in roughly 500 milliseconds. PIP-66 removes that waiting period for primary validators, allowing them to broadcast immediately upon completion. Non-primary validators keep their existing timing rules to prevent single-block reorganization attacks. The practical gain is an estimated 1.5 seconds of reduced latency per block, which tightens the window between when a block is produced and when nodes across the network see it.
The second change, PIP-83, embeds two EIP-1559 gas pricing parameters called GasTarget and BaseFeeChangeDenominator in the extra data field of block headers, making them accessible via enhanced RPC methods. EIP-1559 is the fee mechanism that governs how base fees adjust based on block fullness. Before this change, these parameters were not readable from block data itself, meaning developers had to rely on off-chain documentation or third-party tools to understand how fees might move. After Giugliano, wallets, indexers, and decentralized applications can read those parameters natively from any block.
Upgrade Requirement: All Node Operators Worldwide
Node operators and validators running Bor need to upgrade to v2.7.0 before the April 8 activation window at 2:00 PM UTC; Erigon users need v3.5.0. This requirement applies to all validators and node operators globally. Nodes that have not upgraded will fall out of consensus.
Why PIP-66 Is the More Interesting Story
PIP-66 was supposed to ship with the Bhilai hardfork in July 2025. It did ship, then had to be disabled after behavioral issues were observed on mainnet. The governance proposal for Giugliano, PIP-84, authored by Lucca Martins (@lucca30) on GitHub, describes the current version as a "reviewed implementation that addresses all issues observed during the prior deployment."
This kind of correction cycle is not unusual in protocol development, but it does make Giugliano more than a routine upgrade. It is specifically a second attempt at a feature that failed in production, and the re-attempt required its own hardfork to deploy safely.
Before reaching the activation block, Giugliano cleared a formal governance review at PPGC-40 on March 26, 2026. For an upgrade partly defined by a prior failed deployment, that governance step adds meaningful credibility to the revised implementation.
Community validator Everstake weighed in on the original PIP-66 forum discussion thread: "[PIP-66] improves block propagation [but] implementation requires careful coordination" for the hardfork process, according to a post from Everstake representative everstake_masha on the Polygon Forum. Also writing in that same PIP-66 thread, community member infra_john described the proposal: "This PIP is much simpler but still delivers the benefit of potentially shaving off 1.5s of latency."
Network Context and Token Data
Polygon's on-chain activity has climbed steadily heading into this upgrade. According to Messari's Q4 2025 report, daily active addresses averaged 930,800 during the quarter, up 57.3% from Q3 2025 and 78% year over year. Daily transactions averaged 5.2 million, with February 2026 setting a monthly record at 204 million transactions.
The prediction market platform Polymarket accounts for 55% of all Polygon transactions and 67% of gas fees, according to CoinMarketCap AI data, underscoring how concentrated some of that activity is. Peer-to-peer stablecoin transfers are also a significant segment, with 3.51 million unique monthly addresses sending stablecoins on-chain, up 28%.
POL, the network's native token, was trading at approximately $0.09 as of April 6, well below historical peaks. The network carries roughly $1.3 billion in DeFi total value locked, with more than $7.3 billion in bridged assets. The gap between a depressed token price and rising usage is worth noting for anyone interpreting the upgrade through a market lens.
What This Means for Developers in South Asia and Africa
For developers outside North America and Europe, PIP-83 carries practical weight. Many teams building wallets and consumer apps in India, Nigeria, Kenya, and Ghana rely on third-party gas estimation tools because fee parameters are not directly accessible on-chain. Embedding those parameters in the block headers' extra data field means locally built tools can read fee data without depending on external providers.
India, Vietnam, and the United States consistently rank as the top three countries by active Polygon wallet count, according to CoinLaw's Polygon statistics. The payments dimension is visible in the network's real-world footprint as well. Financial services provider Revolut has processed more than €1.2 billion in on-chain transactions via Polygon, and in Latin America, 89% of local-currency stablecoin activity runs through the network. Both figures illustrate the kind of payments-driven demand that makes fee transparency and faster block propagation more than incremental concerns for developers serving these regions.
Polygon has publicly framed its roadmap around reaching 100,000 transactions per second and sub-second block times under what it calls its Gigagas roadmap. Giugliano is an incremental step in that direction, not a headline leap. The bigger performance jumps came with Heimdall v2 in July 2025, which cut finality from roughly 90 seconds to about 5 seconds, and the Rio upgrade in October 2025, which targeted 5,000 TPS. What Giugliano adds is a cleaner, faster block propagation path and the fee data infrastructure that downstream tooling will need as the network continues to scale.