pectra is shaping up to a BIG upgrade, possibly the largest in ethereum's history, so let's review all the code changes that are going into pectra so far and what is still TBD: ⚡️🧵
EL EIPs CONFIRMED FOR PRAGUE:
- EIP 2537
- EIP 2935
- EIP 7685
- EOF
- EIP 7702
CL EIPS CONFIRMED FOR ELECTRA:
- EIP 6110
- EIP 7002
- EIP 7251
- EIP 7549
- PeerDAS (not incl. in the chart below b/c technically it doesn't require a hard fork, if it does end up being ready, they'll also change the blob count and that will have to be a new EIP)
Alongside EIPs confirmed for Pectra, devs are also working on a few parallel initiatives like PeerDAS, history expiry, and light client development. Depending on how these go, we could see new EIPs included in Pectra later on LIKE:
- EIP 7691
- EIP 7639
While the ACDE call today more or less tried to finalize the scope of Prague, CL developers did not reach a consensus on the last ACDC call about the finalized scope of Electra. There's still two major code changes CL devs are weighing and may discuss on next week's call.
Finally, it's important to note that devs are staging the implementation of Pectra EIPs, MEANING if EOF or 7702 or PeerDAS don't make it into a devnet over the coming months, devs may drop it entirely from the upgrade or split out Pectra into 2 hard forks.
Staging multiple EIPs for implementation on devnets is a new development for the Ethereum governance process that leaves the door open for an upgrade with an ever-changing scope.
It's unclear how large or small Pectra will actually end up being given that devs aren't sure what EIPs will be activated together and what they'll activate separately.
For now, they're going to limit the scope of the next devnet, Devnet 1, to implementing the same EIPs as Devnet 0, with fixes and swapping out 3074 with 7702 and EL triggerable consolidations for 7251.
TBD on what will be included in Devnet 2. Devs are trying for the full list shared earlier in this tweet thread but it is A LOT for one upgrade, so there's still a good chance Pectra gets split.
Stay tuned for the full call summary from today's ACD call, coming out tomorrow! And a podcast summary of the call coming out next Tuesday. 🍃
For more information about the Pectra upgrade and Ethereum governance, be sure to check out the reports and prior ACD call summaries all posted for free publicly on the @glxyresearch Research page on :
Yesterday, there was another Ethereum dev call. The primary focus of discussions on ACDC #119 was Cancun/Deneb testing, specifically:
- the status and health of the latest developer-focused testnet, Devnet-9,
- and timing for the launch of Devnet-10.
About the timing for the launch of Devnet-10, not all developers were confident that the next devnet could be launched in the next two weeks, especially given the fact that client teams are still discovering and resolving bugs on Devnet-9.
There was much discussion between developers about what the focus of testing should be on Devnet-10, outside of the validator churn, and what outcomes from Devnet-10 would warrant sufficient preparation for developers to move on to upgrading public Ethereum testnets.
At a high-level, EIP 4844 introduces a new transaction type, called blobs, increases the data and storage requirements of Ethereum blocks, and creates a new fee market for pricing blobs separately from regular transactions.
Additionally, proto-danksharding is a precursor and “prototype” of full danksharding which will enable existing Ethereum nodes to safely process several more blobs per block than the initial maximum set out by EIP 4844.
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.
Great podcast episode from @BanklessHQ today about the non-finality issues Ethereum faced last week. @preston_vanloon and @terencechain explained what happened and to the best of their knowledge why.
Read below for a TLDR of the episode 🧵
Full episode:
@BanklessHQ@preston_vanloon@terencechain *What happened?* Teku and Prysm validator nodes were receiving old attestations, that is votes on what the head of the chain should be, and evaluating the validity of these old attestations by replaying chain state.
@BanklessHQ@preston_vanloon@terencechain Replaying chain state is a computationally heavy operation. Teku and Prysm nodes that were experiencing high CPU loads were unable to process new attestations in a timely manner b/c they were bogged down with "valid but untimely attestations."
1. Precompile input and output mismatch: @yperbasis, developer for the Erigon (EL) client, mentioned that the input format for the EIP 4844 precompile differs from its output. The input uses little-endian while the output uses big-endian.
@yperbasis Developers agreed to harmonize the output and input to both rely on big-endian, which is the default method for storage of multibyte data types on the EL.