Odaily Planet Daily reports: Polygon Labs has issued an emergency notice stating that Polygon PoS nodes still running older versions of Bor or Heimdall after the activation of the Austin and Kyoto hard forks have fallen out of consensus and must upgrade their clients to catch up with the network. Austin was activated at mainnet block 91,949,700, requiring nodes to run Bor v2.10.0 or higher; Kyoto was activated at block height 51,533,000, requiring nodes to run Heimdall v0.11.0 or higher. Austin addresses two types of Bor resource exhaustion risks: L1-to-L2 bridge state synchronization events were not counted toward the gas limit, potentially slowing block processing; and the TxDependency field lacked size restrictions, which could cause peer nodes to crash.
Polygon PoS nodes out of consensus after forks; Labs urges client upgrade
KuCoinFlashShare
Summary
Polygon Labs has issued a notice urging node operators to upgrade following the activation of the Austin and Kyoto hard forks, part of a broader network upgrade. Nodes running outdated Bor or Heimdall versions have lost consensus. To rejoin the upgraded blockchain, Bor must be updated to v2.10.0 or higher for the Austin fork (block 91,949,700), and Heimdall must be updated to v0.11.0 or higher for the Kyoto fork (block 51,533,000). The Austin fork addresses two Bor resource risks, including unbounded TxDependency fields and L1-to-L2 bridge synchronization events.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.