Wednesday, 30 Apr 2025

BNB Chain starts Lorentz Hard Fork even though Ethereum Eof takes out the upgrade

admin
30 Apr 2025 02:54
Coins 0 3
4 minutes reading



Ethereum

  • The BNB-Chain Lorentz-Hardfork significantly reduces the block times to BSC and OPBNB and improves the responsibility and pace.
  • The Fusaka upgrade from Ethereum comes on schedule, but without EOF. Development delays and technical uncertainty are given as reasons.

The BNB chain has its Lorentz-Hardfork for both the BNB Smart Chain (BSC) and OPBNB completedwhich leads to noticeable improvements in network performance.

After the upgrade, the block times have dropped to BSC at only 1.5 seconds and only 0.5 seconds to OPBNB, which leads to a faster transaction confirmation and faster interactions with decentralized applications.

This upgrade was made possible as part of the constant endeavor to improve the BNB chain. The Lorentz update was communicated as an optimization that makes DAPPS reaction more quickly and at the same time simplifies the interaction of users and developers with the blockchain.

The improved speed of the network in transaction processing ensures that the real-time defi and gaming applications of BNB chain can work with the lowest possible delay.

These lower latencies and better passes are the factors that distinguish BNB chain from other networks, with a strong focus on the introduction of user -friendly innovations. The community has already received the first positive reactions from the developers who are working on the renewed infrastructure.

Ethereum brings the fusaka upgrade without eof

Despite the Successes of BNB Chain In the technology department, the developers who work with Ethereum have to do all hands full because the planned Fusaka-Hardfork was postponed.

It was confirmed thatone of the Main suggestions, the EVM Object Format (EOF), was taken out of Fusaka, as there is fear that it is not ready and could extend the process.

EOF was developed to The execution process of a new smart contracts to improveby defined a format for bytecode. The conversations among the Ethereum nucleus developers showed however that the technical imponderables were still considerable.

Some people who recently spoke to each other admitted that they itself The effects of the last proposed EOF variantwere not fully aware ofwhich indicates doubts about their admission to a critical update.

Eof’s elimination was not a decision that light -hearted was hit. The team agreed that the focus of Ethereum is currently on the implementation of Peerdas, one very important Function for the future scalability of the network. At this point, the addition of EOF is the risk of turning back the Fusaka schedule and confusing the community even more.

The change should be for the Ethereum development team be a moment of self -reflection, was The way decisions and communication are made. One was aware that the process of integrating the EOF integration is a mistake in the Way of how the upgrade priorities are managedcaused .

Nonetheless led die Supporter of the community, Think about der Community And some unanswered questions about the common conviction that it would be the better decision to withdraw EOF.

Different paths for two chains

The comparison between the BNB chain, the Lorentz has smoothly implemented and Ethereum’s fall of the abolition of the basic fund also shows the problems with the orchestration of upgrades in large decentralized platforms.

In addition, the BNB chain harte Changes with a noticeable development and a decline in block times carried out while Ethereum It preferred to withdraw and wait for the development of a situation that was understandable for more people.

The changed plan provides that Ethereum the Anger-upgrade carried out in the 3rd or 4th quarter of 2025 at the earliest, which does not apply to EOF. Pectra becomes As the most important thing for the Ethereum project identifiedand it is confirmedthat it I have 7. May will take place .

 

No Comments

Leave a Reply

Your email address will not be published. Required fields are marked *