Polygon Crypto Secures Bor and Heimdall Clients Before Disclosure

Polygon Crypto deployed two coordinated hard forks, Austin on Bor v2.10.0 and Kyoto on Heimdall v0.11.0, to close denial-of-service, resource-exhaustion and consensus-hardening risks across its Polygon PoS client stack.

Both upgrades were rolled out privately and validated on the Amoy testnet before mainnet activation, according to a Polygon forum post published August 27.No mainnet disruption was observed from the vulnerabilities Austin addressed, and both forks were already active on Amoy and mainnet by the time the disclosure went public.

Source: PolygonThe sequencing matters: Polygon fixed the issues, confirmed the fleet was safe, then explained what had been broken – not the other way around.Polygon Crypto: What Austin and Kyoto Actually FixedAustin closed two Bor block-processing DoS paths.

State-sync events, which handle L1-to-L2 bridge deposits, execute contract code and precompiles just like ordinary transactions, but their gas consumption previously wasn’t metered against a hard per-block cap.