The implementation of the next Ethereum Update, known as Fusaka, began with “some degree of turbulence,” according to developers who attended the 166th meeting of the “Ethereum Major Developer Consensus Layer” (ACDC) on October 2nd.
Fusaka began testing on October 1st on the test network Holesky (Test Net) Ethereum. The report states that “fork activation in Holesky was generally good,” but it was inconvenient.
According to what was explained, Fusaka «About 2 days of non-financialHe then recovered and resumed the end».
The expression “non-nutrition” means that Transactions and blocks do not reach irreversible state It can damage the time security of your network over time.
That is, transactions and blocks during the first few hours of the test network They did not get a decisive state This will prevent them from being reversed.
It then adds that, according to a developer’s report, “there was a decrease in initial participation due to insufficient updates from clients.”
Participation refers to the percentage of validated nodes active in a network. Participation fell from “66%” to a minor number Block completion was affected.
Despite “turbulence,” these types of conflicts are usually seen in early testing.
In fact, as Cryptonoticia reported in the debut of Pein (a previous update of Ethereum), in Holesky, A similar episode has already been registeredreflects the experimental and tuning properties of these stages.
What caused the Ethereum Fusaka problem?
Among the possible causes of the detected issues, the developers showed three factors: An extraordinary amount of data that can handle block block delays, node overloads, and saturate the test network.
These combined elements They can reduce the network capacity to validate and verify transactions It’s stable.
The report also states that at Holesky many validators manage around 10,000 signatures or validation keys each. This high server load It may affect performance Increases the chances of temporary breakdowns.
Ethereum collaborators also estimated that the next update for Holesky is scheduled October 7th.
The test calendar will then continue on Sepolia Network (October 14th) and Hoodie (October 28th). It will not arrive by December.
Meanwhile, the developers discussed the development of the name “Glamsterdam”, the update that follows Fusaka.
Regarding Gram Stardom, they pointed out that “EIP deadlines are not set a week after Fusaka’s mainnet date has been confirmed.”
What does Fusaka bring to Ethereum?
As reported by Cryptonotics, Fusaka incorporates 13 suggestions for improvements to Ethereum (EIP).
The most notable is EIP-7594, which introduces “Peerdas,” a system for the availability of paired data. That system allows nodes to “specialize” Save and check various types of dataincreasing the storage and efficiency of your network.
Through Ethereum’s “Peerdas” Transaction costs are reduced in tier 2 (L2) Bases include arbitrum and others. Over time, you will climb 128 blobs (data packages outside the chain) per block. Host a light node that stores only a small portion of the data.