Thread by @christine_dkim

gm, for anyone who missed yesterday's acdc call, here's a quick summary:

galaxy.com/research/insig…

On ACDC #111, developers discussed what CL-focused EIPs to include in Deneb. Deneb is the name of the CL upgrade that will occur simultaneously with the Cancun EL upgrade.

Last week, client teams finalized the scope of Cancun. Summary of last week's call:
galaxy.com/research/insig…

The 3 CL-focused EIPs that are being prepped for Deneb are:
- EIP 7044: A code change to improve the staking user experience by ensuring that signed validator exits are valid in perpetuity. The EIP proposed by @dapplion has been merged into Deneb specs.

github.com/ethereum/conse…

@dapplion - EIP 7045: A code change to enhance chain security. The EIP would expand the attestation slot inclusion range from a rolling window of one epoch to two epochs. The EIP proposed by @dannyryan is undergoing more discussion and a final review.

github.com/ethereum/conse…

@dapplion @dannyryan - EIP 4788: A code change to improve the staking user experience. The EIP would expose roots of Beacon Chain blocks containing information about chain state inside of the Ethereum Virtual Machine (EVM) for trust-minimized access by decentralized application (dapp) developers.

@dapplion @dannyryan EIP4788 like EIP 4844 impacts both the EL and CL. It was proposed by @ralexstokes and greenlit for inclusion in Cancun and Deneb during ACDE #163.

galaxy.com/research/insig…

@dapplion @dannyryan @ralexstokes Developers are still considering increasing the maximum blob count per block from 4 to 6 as per the recommendation of @dankrad. Related to this discussion around the maximum blob count, @jcksie raised the issue of increasing block reorganizations on mainnet post-Shanghai upgrade.

@dapplion @dannyryan @ralexstokes @dankrad @jcksie “What’s been happening over the past six months is that we’ve gone from practically no reorgs at all to a few per hour. There’s no great answer as to why this is happening, just a couple of theories. It looks like it’s growing with the number of validators," said @jcksie.

@dapplion @dannyryan @ralexstokes @dankrad @jcksie Based on these observations, @jcksie proposed considering changes to the four second deadline for aggregating validator attestations and sending them through the network. Devs agreed to do more investigation into the matter.

@dapplion @dannyryan @ralexstokes @dankrad @jcksie .@mikeneuder shared his proposal to remove the 32 ETH cap on validator effective balances to help reduce the growth of the active validator set.

ethresear.ch/t/increase-the…

@dapplion @dannyryan @ralexstokes @dankrad @jcksie @mikeneuder Developers debated the potential pitfalls of this change and the possibility of combining the proposal with the proposal to enable initiations of partial and full withdrawals directly from the EL. Ultimately, devs agreed to continue discussing this proposal asynchronously.

@dapplion @dannyryan @ralexstokes @dankrad @jcksie @mikeneuder Before ACDC #111, Ethereum core developers met for their first coordination call on the launch of the Holesky test network. As background, Holesky is envisioned to replace the existing Goerli testnet by the end of the year.

github.com/Ethereum/pm/is…

@dapplion @dannyryan @ralexstokes @dankrad @jcksie @mikeneuder .@parithosh_j said that his team was looking to get confirmations from client teams, Layer-2 protocols, and other Ethereum stakeholders on their commitment to put up infrastructure and run validators for the genesis of Holesky.

@dapplion @dannyryan @ralexstokes @dankrad @jcksie @mikeneuder @parithosh_j The plan is to gather these commitments by the next Holesky Coordination Call on June 29 and prepare a final configuration release for Holesky in August and hopefully launch the testnet by September 15.

@dapplion @dannyryan @ralexstokes @dankrad @jcksie @mikeneuder @parithosh_j That's it for the call summary! For more details on what was discussed on ACDC #111, read the full call notes:

galaxy.com/research/insig…