Ethereum consensus layer developers gathered at ACDC #181 to discuss ideas being considered for future network upgrades, review the recently released Glamsterdam Devnet 6, and discuss ongoing builder and Beacon API changes. Since Devnet 6 was only going live a few hours before the call, a significant amount of the discussion focused on testing, implementation progress, and preparing for the next development cycle.

Developers also reviewed EIP-7688, discussed the specifications of EIP-8282, and looked at a few Hegota proposals. The conference ended with a lighthearted update on Glamsterdam's mascot race, in which the Flamingo continues to win the voting.

• Glamsterdam Updates
  • Devnet 6 Goes Live, While Devnet 7 Planning Begins
  • Builder API Improvements & Circuit Breakers Continue to Evolve
  • EIP-7688 Gains Momentum as Devnet Testing Continues
• Hegota Updates
  • EIP-8080 Faces Pushback Over Complexity Concerns
  • EIP-8045 Stays on Track as EIP-8282 Parameters Are Refined

Glamsterdam Updates

Devnet 6 Goes Live, While Devnet 7 Planning Begins

According to Barnabas, Devnet 5 has been operational for almost 20 days and has remained mostly stable during that time. Teams had a Prysm peering issue and a Lighthouse range-sync issue, both of which have already been resolved. It was anticipated that Devnet 6 would switch to the Gloas branch about forty minutes after the call ended, having been deployed approximately three hours before to the conference.

Except for Stable Containers, nearly all Glamsterdam execution and consensus layer EIPs are included in the new Devnet. Besu, Ethrex, and Geth were involved in the execution layer at the time of the meeting, and more clients from the consensus layer were anticipated to join shortly.

In order to prevent slashed validators from being scheduled in later epochs, developers also talked about validator slashing tests. Similar testing had already been completed on earlier Devnets, according to Barnabas. The validity of a specification issue brought up at the conference was verified, and Devnet 7 will address it. The next Devnet is anticipated to launch in two to three weeks, and the specification document for Devnet 7 is currently online.

Builder API Improvements & Circuit Breakers Continue to Evolve

Bharat re-examined a suggestion to eliminate the Builder APIs' submit_beacon_block endpoint. Developers concurred that the default strategy should be to maintain the endpoint unless there is a strong push for its removal; client teams indicated little interest in doing so.

Then, the subject of circuit breakers, which are intended to stop validators from proposing potentially hazardous payloads, was raised. Others believed that there was no immediate need for protocol-level standardisation, but Barnabas suggested that circuit breakers should remain client-specific.

Prysm now appears to be the only client having an implementation, despite developers pointing out that future generations would likely need to look at execution payloads rather than just beacon blocks. Barnabas jokingly suggested organising a circuit-breaker breakout session.

Additionally, developers examined the State Builder API and Beacon API improvements. While some pull requests for the Beacon API are still for review, Teku has already combined support for some of the suggested modifications. Jokingly threatening to block the Devnet 6 Dora page until all Beacon API pull requests are merged, Barnabas stressed the importance of testing these upgrades as soon as feasible.

EIP-7688 Gains Momentum as Devnet Testing Continues

The developers talked about EIP-7688 for a long time. Client teams indicated positive progress, but a decision to move the proposal to the next level will need to wait until implementations are finished and functioning well on a Devnet. Grandine is still working on an implementation, although Lodestar, Nimbus, and Lighthouse already have one.

Barnabas stated that most consensus layer clients were already ready for Devnet testing and that execution layer clients' tardiness had actually caused Devnet 6 to be delayed. Participants stressed that the proposal helps address the 8,192-deposit overflow issue, even though Toni Wahrstös pointed out that the main benefit of EIP-7688 is giving stable 4788 proofs.

Barnabas stated that the process will likely begin at the end of July. The developers concluded that external audits for EIP-7688 should only take place after Devnet 7.

Hegota Updates

EIP-8080 Faces Pushback Over Complexity Concerns

Developers re-examined EIP-8080 and debated whether the proposal offers sufficient benefits to offset the extra complexity it adds. While some participants contended that the proposal restricts consolidation agility, others questioned whether the problem it seeks to address is important enough to justify protocol modifications.

Although he does not intend to advocate for the EIP himself, Francesco stated that he would be open to proposing it again. Terence and Marius Van Der Wijden agreed that the project should only proceed if it becomes necessary. Before a future ACD call, contributors intend to produce further material explaining the current problems to facilitate further discussion.

EIP-8045 Stays on Track as EIP-8282 Parameters Are Refined

EIP-8045, which has already been tested on previous Devnets, was also considered by the developers. Although most client teams agreed that proposals without implementation work should be postponed, there was support for EIP-8045's continued development because Devnet environments are already using it.

After that, the topic of EIP-8282 and its builder execution request method came up. Participants talked about establishing a maximum of sixty-four requests and a target value of eight. While others noted that lower limitations assist in lessening the likelihood of denial-of-service attacks affecting validator sweeps, Justin Traglia contended that dynamic limits are likely unnecessary.

The question of whether system contract updates should be used to implement future parameter changes was also discussed. While conceding that more testing will assist in determining whether the suggested settings are still appropriate, developers were at ease with them for the time being.

That's all from ACD meeting today. You can follow notes from earlier meetings here.

If you find any issues in this article or notice missing information, please feel free to reach out at team@etherworld.co for clarifications or updates.

To promote your Web3 articles, events, and projects, you may reach out anytime via EtherWorld PR for submissions and collaboration.

To follow blockchain news, track Ethereum protocol progress, and read our latest stories, subscribe to our weekly today.

Related Articles

1. Taiko Halts Network After Security Breach
2. Where RWAs Go Next: 6 Projects to Watch
3. TRON Stablecoin Transfers Hit $167B Daily Peak
4. State of Upgrade – Glamsterdam Edition #1
5. Ethereum Coalition Pushes for Encrypted Mempool in Upcoming Hardfork