Offchain Labs: Prysm Has New Update, EIP-4844 Is In Development

Key Points:

• The Prysm team has now implemented and reviewed all the core functions that support withdrawals in the Capella.
• The team successfully completed the shadow fork with the Devnet3 configuration on the Sepolia testnet.
• Prysm also started the EIP-4844 devnet and solved many problems.

Offchain Labs published an update on Capella and EIP-4844 of the Ethereum client Prysm in a blog post.

According to the blog post, withdrawals will be included in the upcoming Shapella (execution layer’s Shanghai + consensus layer’s Capella) network upgrade. The scope of withdrawals includes both full and partial withdrawals:

• Full withdrawals: Full withdrawals mean withdrawing the validator’s entire balance.
• Partial withdrawals: Partial withdrawals mean withdrawing any earnings that are above the validator’s 32 ETH base balance.

The Prysm team has now implemented and reviewed all the core functions that support withdrawals in the Capella upgrade in the default branch “develop” of GitHub and is designing solutions to handle extreme cases, such as broadcasting BLSToExecutionChange messages before and after forks and extending the CLI tool prysmctl provided by Prysm, to improve the user withdrawal experience.

At the same time, Devnet3 is running smoothly, and the validator exit test is completed. Devnet 4, 5, and 6 were launched at the interop conference last week of January, testing validator credential changes with a mainnet-sized validator list. The team also successfully completed the shadow fork with the Devnet3 configuration on the Sepolia testnet. Testnets such as Goerli and Sepolia will also launch withdrawals in the coming weeks.

During the interoperability meeting, the team started the EIP-4844 devnet and solved many problems, re-wrote the new KZG encryption library to support blob transaction security, and it is expected to be put into use in the next few weeks.

The KZG library also switched the backend go-kzg to Gnark for the audit in the next month and a half. In terms of the execution layer, the design of the blob transaction memory pool is becoming more and more mature and solves the coupling and decoupling problem between blocks and blobs in the consensus layer, but new specification changes and client implementations are still required.

DISCLAIMER: The Information on this website is provided as general market commentary and does not constitute investment advice. We encourage you to do your own research before investing.

Join us to keep track of news: https://linktr.ee/coincu

Website: coincu.com

Harold

Coincu News