Testing on Ethereum’s Zhejiang testnet prior to the Shanghai hard fork revealed several bugs, but nothing affected the progress of introducing staking to the network.
Developer Marius VanDerWijden has documented a sync error that other customers encountered that the Ethereum team is confident can be patched. He noted that this bug will not affect any established timeline for the proposed upgrade for the Sepolia testnet scheduled for February 28.
Link to the fix: https://t.co/092ZPcN7mz
— MariusVanDerWijden (@vdWijden) February 16, 2023
The latest withdrawal devnet update detailed a stress test that included 600,000 validators, 360,000 of which performed withdrawal credential updates at the time of the hard fork.
Developer Tim Beiko says there has been a spike in RAM and CPU, so developers will evaluate the number of lost login update notifications against the number recorded in the past few days. next day.
The test also revealed a bug between the PoS client, Prysm, and the Besu client designed for allowed use cases. To sync properly, the Prysm client expects a certain number of responses, however Besu imposes response limits that cause the app to drag below the required sync threshold, so the Besu team This issue is being reviewed.
This test also revealed a Prysm <> Besu issue, where Besu limits the number of responses it sends via RPC to prevent DoS, but Prysm expected a higher number of responses than Besu’s current limit. The Besu team is currently looking into this.
— timbeiko.eth (@TimBeiko) February 16, 2023
After discussing how to best optimize the initial client orientation, the developers finally decided to ban 4844 transactions altogether, which would change the client’s assumption about transactions and can complicate the setup process.
After some back and forth, we agreed to completely ban them for now. This will make things simpler for clients in their initial implementation, and it’s always easier to relax a constraint than add a new one.
— timbeiko.eth (@TimBeiko) February 16, 2023
The developers also discussed how to proceed with the deprecation of “SELFDESTRUCT,” which will terminate the contract, remove the contract’s bytecode from the blockchain, and reroute funds on the contact to a specified address.
Synthetic Kyptos
