Here are the issues the Ethereum Core developers are working on before London goes live

The much-anticipated London upgrade is a blueprint for changing the controversial Ethereum fee structure and is set to launch on August 4th. Tim Beiko, senior coordinator of several Ethereum upgrades, recently joined forces with other core developers to do a Summary about developments related to the upcoming hard fork.

Source: GitHub

First Tim Beiko to discuss about the Görli & Rinkeby fork. With regard to Goerli, the developers Marius VanDerWijden and Karim from ConsenSys have quorum in the Ethereum area:

“… spam the network before and after the fork block to make sure everything runs smoothly.”

On the other hand, the Go Ethereum team for Rinkeby discovered a small catch in their validator configuration.

“The minimum gas price that miners / validators in Geth will accept is 1 gwei and gas prices to London are charged with priority fees instead.”

“However, many transactions got stuck because they had a maximum priority fee of 1 gwei + a maximum fee and the network had a base fee of 7 gwei”.

According to the developers, this problem was solved by lowering the benchmarks set by the validator.

In addition, the customers also agreed to block the provision of 12965000 in the mainnet (Mainnet).

Another topic discussed during the meeting revolved around the storage of gas prices paid by consumers. As is well known, both fields of transaction type 1559 contain the maximum fee (max. Fee + maximum priority fee). To overcome this obstacle, the team added an “effective gas price” to the transaction receipt to combine the price paid after the transaction (base fee + priority fee).

After these updates, Beiko also had an update for the network’s miners. Brothers tweets:

A note to miners: London will double the block size on the network as EIP-1559 aims to keep the blocks 50% full. This happens automatically at the fork, but then the miners have to adjust their target gas limit! “

Next, the discussion also sheds light on how the customer handles the mismatched parts of 1559, namely transaction pool classification and transaction substitution. While most clients use a similar pool design, two different approaches have been used for transaction substitution. Both are very similar, “but with different interpretations”.

Developer Ansgar.eth also emphasizes the complexity of:

“… These are not as easy as sorting by gas price, we can see that different customers prioritize different transactions in the pool.”

Tim Beiko closed the discussion about the London upgrade from specified:

“This can be good in that it” increases “the global transaction pool, but it also has to follow the London Post implementation to see which client implementation does better, while other clients can be customized.”

At home at home

According to AMBCrypto

Follow the Youtube Channel | Subscribe to telegram channel | Follow the Facebook page