Polygon Quietly Patched Serious Security Flaws Before Public Disclosure ⋆ ZyCrypto

Coinbase
fiverr


Polygon Active Addresses Surge 60% in 30 Days: $3 MATIC All-Time High Milestone in Sight?


Add ZyCrypto News On Google

Polygon developers revealed security vulnerabilities they fixed before disclosing them to the community. The changes prevented possible exploitation and usage glitches as crypto network safety concerns linger.

Two Hard Forks Rescue Polygon

In a recent community release, the Validator’s Support Team disclosed recent changes and the reasons behind the shift. The flaws were discovered and fixed through Austin and Kyoto hard forks, both deployed without prior communication to users. 

bybit

According to the team, the issues would affect Polygon’s Bor and Heimdall users, including validator resource exhaustion, milestone and checkpoint processing, and denial-of-service risks.

Austin hard fork targeted a couple of denial-of-service risks in Bor that could cause a glitch in service speed. However, neither was a consensus-correction issue and did not disrupt the mainnet. 

State-sync events (L1→L2 bridge deposits) execute contract code and precompiles just like ordinary transactions, but the gas they consume wasn’t metered against a hard cap. A block carrying enough state-sync events, or one especially expensive event, could make block processing take long enough to transiently stall the chain.”

Follow ZyCrypto On Google News

&nbsp

Further, Bor witnessed the removal of the TxDependency wire field, ensuring parallel execution doesn’t rest on the producer’s hint being accurate. On the other hand, Heindall saw most changes introduced by the Kyoto hard fork.

Before the upgrade, some transactions could cause validators to take on excessive processing tasks, leading to time lags. Specifically, changes include Fee-coin count cap, checkpoint signature recovery-byte normalization, milestone range voting bound to the signed parent hash, non-halting future-span creation, etc.

“The nested-Any decode bound closes the most severe issue in this batch, a permissionless way to force costly, correlated work across the whole validator set. The remaining items harden checkpoint finality, milestone accounting, and L1-event replay against edge cases and resource pressure. All were resolved and validated before either hard fork activated,” the statement reads.

This year, several chains have suffered vulnerabilities that led to lost funds, worsening the crypto red wave. With rising bad-actor activity, users expect weak sentiment around major incidents but remain positive on the general outlook.

A major concern around blockchain security is Q-Day, a period when quantum computers will become advanced enough to break digital asset cryptography. However, several networks are already developing quantum-safe wallets to prevent any incidents in the coming years.



Source link

fiverr

Be the first to comment

Leave a Reply

Your email address will not be published.


*