Polygon's Giugliano Hardfork Cuts Finality and Rewires Fees

On April 8, 2026, Polygon PoS activated its Giugliano hardfork at mainnet block 85,268,500, according to Coinspeaker. The upgrade is small in scope and large in implication: it shaves roughly two seconds off transaction finality and, for the first time, publishes EIP-1559-style fee parameters directly inside block headers. Neither change will make headlines the way a new scaling claim would, but both touch the part of the stack that high-frequency DeFi and consumer payments actually live in.

For a network that spent much of 2025 fighting reliability perception problems, Giugliano is less a spectacle and more a quiet statement that Polygon's core chain is getting harder to complain about.

The headline numbers

Per BanklessTimes, Giugliano was scheduled to go live around 14:00 UTC on April 8, with validators required to run Bor v2.7.0 or Erigon v3.5.0. The same report notes that transaction finality on Polygon PoS had already fallen from over sixty seconds to roughly five seconds after the Bhilai upgrade in mid-2025; Giugliano's two-second improvement, measured on the Amoy testnet, cuts that remaining window meaningfully further.

Two seconds sounds trivial until you consider what uses those seconds. A perpetuals exchange updating mark prices, a payment app confirming a point-of-sale swipe, a solver routing a cross-chain order — each of them pays a latency tax every time a chain forces the user to wait for a block to be considered safe. Giugliano does not change block times; it changes when a validator is allowed to treat a block as final.

How the finality cut actually works

The mechanism is deceptively simple. Under the new rules, block producers can announce blocks earlier in the consensus cycle, letting downstream validators begin their confirmation math sooner. Coinspeaker reports that the change revives behavior originally shipped in PIP-66 as part of the Bhilai hardfork, which was later reverted after operational issues. Giugliano is the refined implementation, re-introduced once the kinks were worked out.

That lineage matters. This is not new research being deployed to mainnet; it is a previously battle-tested change returning in a safer form. For a chain that has been accused of pushing upgrades too fast, the "this time with a fix" framing is a credibility move as much as a technical one.

The Amoy testnet activation at block 35,573,500 in late March, also noted by Coinspeaker, gave node operators roughly two weeks of runway before mainnet — a tight but not reckless window for a change that touches the consensus loop.

Fee parameters move into the block header

The second change is the one developers are quietly more excited about. Giugliano embeds fee parameters into the block header itself and adds new RPC endpoints for reading that data, per BanklessTimes.

Today, wallets and dApps on EVM chains typically estimate gas by making separate RPC calls, by querying an external gas oracle, or by running heuristics over recent blocks. Each of those paths has failure modes: stale oracles, misconfigured fallbacks, or the dreaded "transaction underpriced" error that greets users on congested days. Pulling fee parameters into the header means any client parsing blocks already has the canonical fee context for free, without a second round-trip.

The implications ripple in three directions:

• Wallets can show users more accurate fee estimates without depending on third-party gas APIs. That is a non-trivial simplification for mobile wallets and embedded wallet SDKs that today carry extra infrastructure just to guess fees.
• Light clients and rollups that consume Polygon block data get a cleaner, canonical source for pricing. For any system that bridges from Polygon or posts proofs against it, header-level fee data reduces one class of indexing errors.
• MEV and solver infrastructure gain a primitive they can trust block-to-block, which matters when fee spikes are the signal a searcher is trying to read.

None of this is glamorous, but it is the kind of change that removes daily friction for the people actually building on the chain.

Why this matters for the Gigagas roadmap

Polygon has been loud about its Gigagas target of 100,000 transactions per second, as BanklessTimes notes. Giugliano does not move that number. It does not touch the block gas limit, the execution engine, or the data availability layer. So why frame it as a Gigagas step?

Because scaling throughput without first fixing latency and fee legibility is a trap. A chain that hits 100,000 TPS with unreliable finality or opaque fee markets is a chain that cannot be built on at the top of the funnel — users, wallets, and exchanges lose confidence long before the theoretical throughput ceiling matters. The hardest scaling problems are not the ones measured in TPS; they are the ones measured in "does my wallet show the right fee" and "is this transaction final yet."

Seen that way, Giugliano is the kind of invisible work that has to happen before the headline numbers are allowed to grow. The Bhilai upgrade in mid-2025 pushed throughput past roughly a thousand TPS, per BanklessTimes, and Giugliano is the first follow-up whose explicit job is to clean up what that jump exposed. Throughput is easy to advertise; the plumbing underneath is what determines whether the advertised number is usable.

The second half of the upgrade: PIP-85

Bundled with Giugliano is a separate improvement activating slightly earlier. Coinspeaker reports that PIP-85 activates at block 85,245,000 and routes priority fee income directly to delegators. For a proof-of-stake network, that change is not just an economic tweak — it is a signal about who the chain wants to optimize its rewards for.

Routing priority fees to delegators aligns validator economics with staker economics, which reduces the drift between who secures the network and who is compensated for congestion. It is the same philosophical direction Ethereum took with EIP-1559's tip model, adapted to Polygon's delegation structure.

It is worth noting that these two changes — a finality cut and a fee-routing tweak — arriving in the same upgrade window suggests Polygon is trying to cluster consensus and economics fixes into predictable delivery cadences, rather than shipping them piecemeal. For validator operators, fewer upgrade windows means fewer coordination costs.

What it means for users and developers

Regular users should not need to do anything. No token migration, no wallet reconfiguration — the upgrade is transparent at the application layer, which is itself a design achievement for a consensus-level change.

Developers have more to think about. Wallet teams can simplify fee estimation pipelines once a majority of RPC providers expose the new endpoints. Bridge and indexer teams should verify their header-parsing assumptions — adding fields to a block header is the sort of thing that breaks naive parsers written three years ago. And any protocol that currently relies on external gas oracles as a trust assumption should audit whether it can now drop that dependency.

For the Polygon ecosystem as a whole, the message is that the chain is being tuned rather than rewritten. After a year when reliability narratives mattered more than feature announcements, tuning is arguably the correct product strategy.

The harder question: is this enough?

Giugliano is a solid, targeted upgrade. It is also, objectively, small compared to what competing chains are shipping. Layer-2 rollups on Ethereum are iterating on proving latency and shared sequencing. Alternative L1s are advertising sub-second soft confirmations as baseline features. A two-second improvement at roughly the five-second mark is welcome but not a competitive moat.

The honest read is that Giugliano is a prerequisite, not a differentiator. Polygon's strategic question is whether the Gigagas roadmap can deliver the throughput and cost story the team has been promising, and whether upgrades like this one arrive often enough to keep developer confidence from leaking to alternatives. The answer will not come from a single hardfork. It will come from the next three or four, and from whether they land without the kind of revert drama that plagued PIP-66 the first time around.

The fact that Giugliano is PIP-66's second attempt, shipped more carefully, is the most reassuring detail in the whole announcement.

Implications

If Giugliano performs on mainnet the way it performed on Amoy, the most immediate winners are consumer-facing applications that care about confirmation feel — payment apps, gaming settlement, and social dApps where users read confirmation UI in real time. The secondary winners are infrastructure providers who can now simplify their fee estimation stacks, which tends to show up as quieter incident channels rather than press releases.

The broader signal for the L2/sidechain landscape is that the competitive frontier is moving from peak throughput claims to reliability of the last meter between the chain and the user. Header-level fee data is a small but genuine example of that frontier. Expect competing chains to ship similar primitives, if only because the alternative — relying on off-chain gas oracles forever — is already showing its age.

Key Takeaways

• Finality cut: Giugliano reduces Polygon PoS transaction finality by roughly two seconds, building on the five-second baseline established by the mid-2025 Bhilai upgrade.
• Fee data in headers: EIP-1559-style fee parameters are now embedded directly in block headers, with new RPC endpoints for clean access, removing a class of wallet and dApp estimation bugs.
• Second attempt: The finality mechanism revives behavior originally shipped in PIP-66 during Bhilai and later reverted — this is the refined re-implementation.
• Gigagas plumbing: The upgrade does not itself move the 100,000 TPS target, but it fixes latency and fee legibility issues that would bottleneck any future throughput push.
• Operator requirements: Validators need Bor v2.7.0 or Erigon v3.5.0; regular users do not need to take any action.