Polygon has rolled out its Ithaca upgrade on the mainnet, which brings new infrastructure updates that aim to make network payments more dependable. The upgrade activated at block 50,185,000 and focuses on keeping transactions going even when a block producer runs into trouble, stopping certain transactions from slowing down the network, and giving node operators better tools to monitor the blockchain’s health.
This upgrade targets developers, businesses, and infrastructure teams that rely on Polygon for payments. Instead of focusing on new user features, Ithaca makes the core systems more resilient. Polygon says the changes help with cutting down on transaction interruptions or the need for people to step in and fix things manually. Ithaca is also the fourth upgrade to the mainnet in less than five months, preceded by Lisovo, Giugliano, and Zurich, as Polygon keeps working on making payment processing more stable and efficient.
Ithaca Introduces Automatic Failover and New Transaction Protections
One of the biggest highlights of the Ithaca upgrade is an automatic failover system for block producers. Before this, if the node creating new blocks had an issue, the network could freeze for about 15 minutes and there was not any automatic fix for it. That meant pending transactions could just stay stuck until someone stepped in and fixed it.
Polygon says these kinds of delays stand out during busy times, like shopping events or payroll runs. Now, with Ithaca, if a block producer has a problem, another health block producer steps in automatically without waiting for any manual rescue, so that the transactions keep flowing. The upgrade also blocks oversized transactions, which according to Polygon, can put extra load on the network and hurt its performance. With the new protection, these transactions are rejected before they can slow things down or affect the stability.
Ithaca Upgrade is live on Polygon Chain.
Operators: double check your nodes are upgraded.
Everyone else: go make a payment. It’ll clear smoother than ever, on an even more reliable chain. pic.twitter.com/i6DItDcXM2— Polygon | POL (@0xPolygon) July 30, 2026
Polygon points out that these features help the network perform steadily, even under heavy usage. The goal is not to change how people interact with Polygon but to keep transactions running smoothly and reduce issues that would otherwise result in abrupt payments. The company also adds that these improvements are designed to reduce the situations where transactions become delayed or where operators need to step in to resolve issues. The company describes the goal as making payments continue to process smoothly while reducing disruptions behind the scenes.
The Upgrade Gives Node Operators Better Visibility Into Network Operations
Besides the transaction changes, Ithaca brings new tools for the people running Polygon’s infrastructure. The upgrade gives node operators more visibility into the network health so they can spot and solve problems earlier. Polygon says that the upgraded monitoring can alert infrastructure teams about issues before they get bigger, making day to day blockchain management smoother and keeping payments more reliable.
The company told node operators that they need to upgrade Heimdall v0.10.0 for Ithaca to work and also warned against running mixed software versions at the time of activation. This release is a part of Polygon’s ongoing efforts to make every part of its payment related blockchain stronger. Polygon says each recent upgrade tackles problem areas in processing payments by introducing fixes before users feel any impact.
Also read: Polygon Turns Deflationary in 2026 After Removing 107M POL
Ithaca follows Lisovo, Giugliano, and Zurich, making it the fourth mainnet upgrade in five months. Polygon says this series of upgrades is aimed at improving reliable uptime, delivering predictable performance under network loads, and helping transactions continue to process smoothly. The latest update continues that effort by introducing automatic recovery for block producers, blocking oversized transactions that could affect network performance, and improving operational visibility for the node operators that are responsible for maintaining the network.
