Polygon to undergo hard fork to reduce reorgs and gas spikes

Polygon to undergo hard fork to reduce reorgs and gas spikes

Whats the Difference between MATIC on Polygon and Matic on Ethereum

Layer 2 PoS blockchain Polygon has announced a hard fork upgrade to its platform to deal with gas spikes and improve the security of blocks on the sidechain network.

The hard fork debate was first presented to the Polygon community in December 2022.

In their recent post, Polygon Labs claims that the proposed hard fork on January 17th will help reduce network gas fee spikes and chain reorganization, or reorganization. Hard forks, unlike soft forks, are not backward-compatible and require all node operators on the network to update to the latest software at a specified time.

Hardfork upgrade to address gas spikes and reorgs

The upgrade will reduce the effect of gas fee spikes by increasing the “BaseFi ChangeDenominator” from 8 to 16 to smooth out the base fee change rate. The BaseFeeChangeDenominator is a factor that inversely determines the rate at which the base transaction fee changes in response to current demand for block space.

The goal of this change is to smooth out the rate of change of the base fee, thereby reducing the severity of gas price fluctuations during periods of high demand, and to enhance the customer experience with the chain.

Polygon is confident the change will work as it has backtested it against historical Polygon POS mainnet data.

Another issue that is intended to be addressed with the hard fork update is the chain reorg. Blockchain networks may briefly split in two due to reconfiguration, which may result from network congestion or malicious attacks.

This hard fork upgrade reduces the sprint length from 64 blocks to 16 blocks, reducing the production time of a single block producer from the current 128 seconds to 32 seconds.

The hard fork will help reduce sprint length, increase transaction finality, and reduce the frequency and depth of reorgs.

There will be no change in the overall rewards, as the change has no effect on the number of blocks produced by validators or on the total time.

Before January 17th, all PoS nodes will need to upgrade to Bor to keep their nodes in sync.

Follow us on Google News


Please enter your comment!
Please enter your name here