terencechain

Saw a lot of back and forth on faster slot time (EIP-7782) and epbs (EIP-7732), so I wanted to share where I stand. First off, I want to emphasize that all the discussions I’ve seen have been in good faith, everyone wants what’s best for Ethereum. The main question is just the order of operations. This is a good problem to have! From the outside it might look messy, but that’s what public R&D looks like. We're in an open kitchen debating whether to serve steak or lobster first, the customer gets both either way, it’s just a matter of when and how.

Now speaking just for myself (not my team), I believe we should ship EIP-7732 first. Here’s why:

1.) From an engineering perspective, it makes more sense to restructure first, then shorten. Doing it the other way around is not just more engineering work, it’s not 1:1 (not linear either) but it's harder to reason about.
2.) From a testing perspective, it's simpler to test slot restructuring first and then faster slots. As we saw in Pectra, testing is the main bottleneck to shipping!
3.) From a security perspective, rolling out a larger change (like restructuring) first and then a smaller one (shortening) is often safer. Let it run on mainnet and harden before adding more complexity.
4.) From a timeline perspective, in terms of combined time, I believe (EIP-7732 → EIP-7782) is faster than (EIP-7782 → EIP-7732). We could ship 7782 just 3–4 months after 7732 if we work on both in parallel and switch to test mode as soon as 7732 lands. A short CL-only fork could get us there quickly.

That’s just my view as someone building and implementing this stuff day to day. I’m missing context in both research and the community. Ultimately the users of Ethereum should have a say, would you prefer faster slot times in Glamsterdam or a higher execution gas limit and more blob capacity? Why? I’d love to hear your thoughts

Haven’t been able to make it to ACD calls as much as I’d like, but today’s session looked super productive. Ethereum is shipping & scaling!

Ethereum validator queue has been growing steadily since late May, I analyzed all the old ETH1 and new EIP-6110 execution deposits from slot 11649077 -> 11931977

Highlevel numbers:
- There are total 82,529 new EL deposits vs. 541 old eth1 data deposits as expected eth1 deposit was deprecated
- Total 2.3M ETH deposited via EL deposit
- 375 EL deposits greater than 32 ETH amount

now we share some charts:

https://launchpad.ethereum.org/en/validator-actions is criminally underrated. The UX for partial deposit, withdrawal, and compound is super smooth. Huge kudos to the team behind it, but as always, DYOR

先月、ブロックを掘り進めていて、興味深いことを見つけました：
172のブロックにはトランザクションがなく、85には手数料受取人がいませんでした。
それは1日あたり約5〜6、再編成とほぼ同じ割合です。
例：https://t.co/lw0pSAePBt
最後の瞬間の再編成がビルダーを驚かせているのでしょうか？誰か詳しいことを知っていますか？cc @Data_Always

Pectraアップデートから1か月。すべてのブロックをダウンロードし、実行リクエストの使用を調査するために簡単なスクリプトを書きました。236,000スロットで見つけたこと:

- 236,000スロットのうち、実行リクエストがあったブロックは30,587のみ
- これらのブロックには69,041の入金リクエスト、312の出金リクエスト（なぜこんなに少ないのか！）、および17,570の統合リクエストがありました
- 入金では、57,293のユニークな公開鍵と2,102のユニークな出金認証情報が見られました
- 出金では、262のユニークなバリデータ公開鍵と100のユニークな送信元アドレスがありました
- 統合では、3,422のユニークなターゲットアドレスと3,544の自己統合があり、これはバリデータの約1.3%が統合したように見えます

ここで何か目立つことはありましたか？

Hoodi testnet reaching 60M gas limit 🚀

One week after Pectra: reorgs per day have dropped back to pre-petra levels, looking good so far

Sepolia testnet reaching 60M gas limit🚀

Pectra saved eth price, who knew all it took was moving committee index out of attestation

Pectra hits mainnet in ~20 hours
I won’t be tweeting finalization—just hoping everything goes smoothly 🫶