🚀 Excited to release Ress - a fully validating stateless Ethereum node with just 14GB disk requirements, built on Reth! Statelessness paves the way for scaling L1 gas limit, scaling optimistic L2s, and for implementing Native Rollups to improve the L2 ecosystem’s security &

Block-Level Access Lists (EIP-7928) is a favorite for Glamsterdam & ranks high with both the community and the core devs. https://t.co/29Sqc3A3sb curates client progress, analyses, code, EL/Engine API specs & tests, plus mainnet JSON examples, everything to get started.

the EU is pushing chatcontrol again, this time even worse, but it's almost impossible to get a hold of a representative, and the entirety of the apparatus is so embarassingly opaque if you're in the eu & you care about privacy, please check

Spotted at Frontiers

.@r_krasiuk shares the key benefits achieved and milestones needed to reach L1 ZKEVMs , Benefits : scale & privacy Milestones needed : ePBS which introduces asynchronous execution and opcode repricings are key

Earlier this week we published Reth team perspective on Glamsterdam headliners: https://t.co/t5xOuQ0Cri Even though we gave preference to EIP-7732 over EIP-7782, both are in my S-tier. Unfortunately, both can't be shipped in the same fork

IMO the Reth state transition on tip of a large chainstate (eg Ethereum, Base) is the best benchmark for real world zero knowledge proof performance. We already have that demonstrated with multiple ZKVMs, today, powered by a stateless MPT Reth executor program such as Succinct's

🧵 1/ zk-Stateless Ethereum Clients Berlin workshop talk by @kevaundray @r_krasiuk @ignaciohagopian Why can't we just raise the gas limit? What does stateless execution really look like? And how do zk-proofs come into play? Let’s unpack the design space and architecture ↓

Some ideas: - EIP7503: ZK Wormholes for base layer privacy. - Aggressive Gas Repricing (make compute nearly free, cache-aware storage) for scaling. - R55: Rust and C smart contracts. - Subset of native account abstraction: Batching & pay fees in any coin. What else?

New post on Delayed Execution. Together with @fradamt, we explore EIP-7886—a proposal that could unlock 10x L1 scaling by decoupling block validity from execution. https://t.co/DjnsvzHqgA Let’s break it down 👇

😭@github pls fix

Delayed Execution (EIP-7886) is one of the widely discussed proposals aimed at Ethereum L1 scaling, enabling significantly higher gas limits or shorter slot times. I put up this commented spec to give more insight into how it works and where it’s headed: https://t.co/5prMeX292C

Reconfiguring AllCoreDevs To deliver on Ethereum's ambitious L1 roadmap, we should decouple planning and execution. To that end, I'm proposing we reorient ACD to focus on scoping future forks, and elevate our existing testing calls as the main venue for the current ones. 🧵👇

My personal take for Fusaka. This does NOT reflect @prylabs' position nor has been discussed with them. 1) Forks should be scheduled with a time horizon. ACD has long refused to commit to a timeline since all the merge delays. However, not committing to a deadline drags... 1/7

hiring one Reth Core Dev -- this is a unique opportunity to work with me & under direct mentorship from @r_krasiuk on upgrading Ethereum. responsibilities would be 100% time spent on core protocol development. cash/equity.

Really excited for today's Ress release. Ress is Stateless Reth and highlights how there's an "offense" angle to statelessness that is historically underdiscussed. <4K LoC, built on Reth SDK.

Huge thanks to piapark @0xpiapark for getting the project off the ground, @joshie_sh for implementing hive adapter and @notnotstorm for gathering the bytecode data.

For a deeper dive into Ress read the full article: https://t.co/Hy3v98RWMx

Ress is built using Reth SDK in under 4K lines of code. It reuses reth's networking stack and implements a "witnessed" EVM executor. Feedback and contributions are welcome! https://t.co/CXkW8V3TWz

Ress operates with no protocol changes, following the chain's tip and attesting to its validity. Upon receiving new payload, it fetches all necessary data from peers and executes and fully validates the block.