1. This is average case, not worst case. We need real-time worst case for safe L1 use 2. Not formally verified 3. ~100 kW to prove. Proving is a 1-of-n trust model, but even still, perhaps we want proving doable at home (~10 kW) 4. We wanna 10-100x the L1 gaslimit So, truly amazing work by @pumatheuma and team, but definitely still a few steps to the final destination.

1. This is average case, not worst case. We need real-time worst case for safe L1 use 2. Not formally verified 3. ~100 kW to prove. Proving is a 1-of-n trust model, but even still, perhaps we want proving doable at home (~10 kW) 4. We wanna 10-100x the L1 gaslimit So, truly amazing work by @pumatheuma and team, but definitely still a few steps to the final destination.

以太坊跑不跑得起，已不是技術問題，而是階級問題？ 當以太坊持續尋找擴展主網效能的路時，有一個經常被忽略、但至關重要的問題浮上檯面：一般散戶還能自己跑節點嗎？ Vitalik 在 Ethereum Research 發表的新文，就聚焦在這點，「怎麼讓普通人，依然能跑得起節點？」 以太坊的擴展策略其中一環，是提高區塊的 gas limit，簡單說就是每個區塊可以處理更多交易、更多資料。問題是，這會讓節點必須處理和儲存的資料量暴增，對硬體要求越來越高，變成一種技術與金錢的門檻。 節點不只是區塊鏈的「檢查員」，還是用戶保護自己隱私和抵抗審查的最後防線，只能靠外部 RPC 讀資料，這些服務就可能成為單點故障、監控你行為、配合封鎖的風險點。 @VitalikButerin 提出了一系列「讓節點輕量化」的想法：從短期的 EIP-4444（只保留最近 36 天的歷史資料）開始，到中期推動無狀態驗證（讓節點不用存整份狀態也能驗證區塊），最後進化出一種新型態節點部分無狀態節，這讓節點變得更像是個人化、可調的「區塊鏈私服」

How can Ethereum fund the infrastructure it relies on? → Surfacing what matters • What principles, outcomes, or metrics should guide how funds are allocated? • What principles, outcomes, or metrics should guide how funds are allocated? • What does the ecosystem value? → A transparency dashboard • Aggregate ecosystem-wide funding data • Track contributions across shared infra → An ecosystem-wide support commitment Octant is closely aligned with this vision: a scalable growth engine that routes capital + revenue using DeFi for ecosystem growth and Ethereum as a whole, sustainably. Check out the full post by @sejal_rekhan and @TheDevanshMehta supported by insights from @audreyt, @julianzawist, @clesaege, @dwddao, @jchaskin22, and @owocki

just wrote up a monster post with @sejal_rekhan around how ethereums ecosystem can become self-sufficient & circular Some of these ideas have sat in my head for ages & grateful to Sejal for making the push to comprehensively write up an entire roadmap here's a 5 point TL;DR 1. There's limited appetite for a "shared treasury" to fund infrastructure as that feels like "donating" however there is a desire by ecosystems to contribute to repos that they depend on, which feels more like integrating revenue & cost centers For eg, @CurveFinance makes use of @vyperlang ; so funding them isn't a donation so much as making their own product more secure 2. Eligibility requirements is the hard question to solve for; what repos should even be allowed into an ecosystems funding round, whatever the mechanism may be? On what grounds could Curve include vyper in their funding stream but reject solidity? 3. There's need for an L2Beat style system tracking the extent to which DAOs, dapps & L2s are funding software they make use of it would be quite manual though, since answering questions like "does @arbitrum contribute more or @Optimism" isn't straightforward, since @prylabs is funded by offchain labs but needs to be accounted for similarly some of optimisms funding goes to growing dapps on their ecosystem (creating dependents) rather than their dependencies, so opinionated calls would need to be made on how much of the retrofunding gets counted in the leaderboard 4. We propose augmenting the pledge to, ,,1% airdrop to @ProtocolGuild , 2% revenue to your own dependencie" Some estimates of funding amounts if this pledge gets taken; - @ensdomains earned $31 million over 12 months, so $620k to their dependencies - @Securitize gave $25.4 million in dividends, 92% on ethereum, 2% of which would be $467,360 - @nounsdao is currently selling at ~2 ETH/day, 2% of which over a year would be 14.6 ETH to repos they depend on 5. Finally, how would we go about fairly allocating to repos? Step 1 is simply generating a dependency graph of all repos that make your revenue generating product work well Step 2 is giving weights to each dependency. QF, Deep Funding, Futarchy, PG style time weighting, metrics based retrofunding etc are some ways to obtain weights Step 3 is encoding a stream from revenue earned to your local dependency graph, thus creating reliable & recurring funding for teams that your project depends on Curious to actually see how these ideas pan out in practice! if you're building in public goods, pivot from seeking donations to self-interested systems where projects can easily pay for the software they rely on

Pectra is live on Ethereum mainnet! - Smart account wallet UX features now active - L2 scaling data storage blobs increased by 2x - Validator UX improvements live Community members will continue to monitor for any issues over the next 24 hours.

"most prefer to dance kumbaya" is vibes, not reality. From where I'm standing, there's basically universal agreement among researchers that gas limit increase features are top priority for glamsterdam. @adietrichs and others in ER have this as their primary focus: delayed execution, block-level access lists, 4444, gas pricing changes, all things that can together enable gas limit -> 300m (not 100m) If the functionality is done sooner than glamsterdam, then glamsterdam itself can happen "sooner than glamsterdam". I'm seeing a lot of willingness to do faster hard forks post-pectra with near-zero pushback. And all the other things are already in the pipeline. 7702 solves the "click two times to swap" thing, that's in pectra (though it requires wallet support). Based rollups are making rapid progress (@taikoxyz and @NethermindEth Surge are good to follow here). Long-term AA (7701) is being aggressively simplified (thank you @yoavw!) so that we can get the benefits of abstracted verification (with censorship resistance) with minimum load on consensus spec.

@rstormsf @alex_pertsev You created Tornado in significant part because of my suggestion that it is something worth building. It would violate basic honor for me to do that, and then fail to support you in your hour of need. In Ethereum we protect our own, and uphold our honor. Milady