description: Notes from the regular proof of stake [Eth2] implementers call
# Consensus Implementers’ Call #105 - 2023-03-23
[Quick contemporaneous notes by Ben Edgington; fka "Eth2 Implementers' Call"]
Alex Stokes in the chair today.
### Client releases
Consensus spec release [1.3.0-rc5](https://github.com/ethereum/consensus-specs/releases/tag/v1.3.0-rc.5) is out.
Round-robin call-out for Capella (and Shanghai) readiness: all client teams on call will have a release out this week or early next week.
EF Blog post should be up Tuesday or Wednesday next week.
[Pari] There will be one more mainnet shadow fork once all releases are out.
[Fredrik] Bug bounty for Shanghai--Capella specific issues have been boosted to 2x. Up to $0.5m now: bounty.ethereum.org.
[MEV-boost community call](https://collective.flashbots.net/t/mev-boost-community-call-2-30-mar-2023/1465) upcoming, mainly to discuss Capella readiness. March 30th at 16:00 UTC.
[Gajinder] Discussion of [Add corresponding proofs to BlobsBundleV1](https://github.com/ethereum/execution-apis/pull/392): add proofs to the get-blobs engine API. [EIP 6610](https://github.com/ethereum/EIPs/pull/6610) means that the execution layer now has the proofs, so it is easy to pass them to the consensus layer. Consensus layer doesn't need to generate any proofs or commitments, just verify what it receives from the execution client.
[Marius] KZG library startup times. Some can be slow to start and mean that every test can take 2 seconds. To be addressed in the KZG library. Not a problem in normal running, but a big problem for testing. [Dankrad] Transforming the setup data to Lagrange form is what takes most of the time. We could change the initialisation file to store in Lagrange form rather than compressed point form. This should reduce the startup time to milliseconds.
[Etan] SSZ discussions remain ongoing. How much of the changes do we want to bring forward into Deneb? [Tim] Monday's SSZ breakout call decided to wait until All Core Devs makes a decision on this - there are lots of factors to consider. Different client teams are in different places on this.
## Research, spec, etc.
[Naming for the post-Deneb upgrade](https://ethereum-magicians.org/t/e-star-name-for-consensus-layer-upgrade-after-deneb/13248). "Electra" seems popular. Join the EthMagicians' discussion to give input.
[Marius] Would like to drop the execution layer fork name. There is a possibility of independent upgrades happening on each side, but we can use a one-off name in that case. Having two (or actually three - Shangahi/Capella/Shapella) names for a single fork is confusing for everybody. [Poojah] There are still people confused about Eth2 naming. Improving our naming will definitely help. Tim likes the portmanteau names 🤮
* * *
# Chat highlights
Mostly just banter this week.