Polygon Labs has issued an urgent notice after the Austin and Kyoto hard forks went live on the Polygon PoS network, warning that nodes still running outdated Bor or Heimdall clients have fallen out of consensus. According to CryptoSlate, the Austin fork activated at mainnet block 91,949,700 and requires Bor v2.1.0 or later, while the Kyoto fork activated at height 51,533,000 and requires Heimdall v0.11.0 or later. Austin addresses two Bor resource-exhaustion issues: one where L1-to-L2 bridge state sync events were not counted toward the Gas limit, which could slow block processing, and another where the TxDependency field had no size limit, potentially allowing peer nodes to be crashed. Kyoto patches a set of vulnerabilities, including deeply nested message attacks, fee coin scanning, and checkpoint signature recovery. Both hard forks are described as pure binary upgrades, meaning no state migration is required and nodes that have not forked do not need to resync. Polygon Labs urges operators of older clients to upgrade promptly and, if necessary, resume synchronization under its guidance.
Polygon Labs Issues Urgent Notice for Stale Nodes
Polygon Labs has issued an urgent notice following the activation of the Austin and Kyoto hard forks. According to CryptoSlate, Polygon PoS nodes that are still on older versions of Bor or Heimdall have already fallen out of consensus. Operators need to upgrade their clients promptly and catch up with the network.
Austin and Kyoto Activation Details
Austin, which requires Bor v2.1.0 or later, activated at mainnet block 91,949,700. Kyoto, which requires Heimdall v0.11.0 or later, activated at height 51,533,000.
What Austin Fixes
Austin fixes two Bor resource-exhaustion risks. First, L1-to-L2 bridge state sync events were not counted toward the Gas limit, which could slow down block processing. Second, the TxDependency field had no size limit, which could cause peer nodes to crash.
What Kyoto Fixes
Kyoto patches vulnerabilities related to deeply nested message attacks, fee coin scanning, and checkpoint signature recovery.
Upgrade Guidance
Polygon Labs said both hard forks are pure binary upgrades, so no state migration is needed and nodes that have not forked do not require resynchronization. Operators of older clients should upgrade as soon as possible and, if needed, resume syncing under Polygon's guidance.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
