im sick of "alignment" being the goal of #ethereum projects, @peter_szilagyi's open letter to the EF explicitly critiques this culture of kingmaking where what @VitalikButerin and his posse say is good for the ecosystem is good and aligned,
how about you think about @Polygon tempo paradigm not through the lens of alignment but your own critical thinking skills and decide for yourself for a change. ethereum is supposed to be a neutral protocol where people can do this!
plus, this way you can avoid the mental gymnastics of trying to absolve every single decision made by buterin and his close friends at the EF as right for ethereum. in general, you're just going to get angry at life if you keep letting someone else think for you.
last point, it's actually impossible to be aligned with ethereum if what you're aligning with is really just the views and opinions of a small group of high profile ethereum thought leaders, because believe me when i say, this group isn't always themselves aligned with each other!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
There have been 2,225,958 blobs purchased at an average cost of $1.59/ blob and 1,104,315 blob carrying Layer 1 transactions at an average cost of $5.22/ transaction in the 150-day period following the implementation of EIP-4844.
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)
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."