Ethereum's execution layer scaling roadmap is on track: - Continuous Gas Limit Increases (EIP-7935) - History Expiry (EIP-4444) - Delayed Execution (EIP-7886) - Block Access Lists (EIP-7928) - Block-Level Warming (EIP-7863) Here's a short thread with additional context👇

1/🧵 Applications for the EF 2026 Internship Program are now open. A paid, full-time, 12-week opportunity to work directly with the teams advancing the Ethereum protocol and ecosystem.

The case for Payload Chunking, in one picture:

6/ Similar to Base’s Flashblocks (low-latency streaming), and with CALs, Ethereum can go for parallel, dependency-free validation while keeping one global state (e.g. no complex cross-shard communication needed). See also @protolambda’s post:

5/ Key benefits: • Streamed block building and validation • Bounded gas & resources (≤16.7M per chunk) • Parallel validation with CALs • Per-chunk ZK/optimistic proofs • Lower latency & smoother propagation All txs are parallelizable — independent of state dependencies.

4/ Validation splits into 2 phases: • Per-chunk: check transactions, gas and execution outputs • Full block: ensure continuity + final state root This keeps blocks atomic, but execution is streamed.

3/ To make this work efficiently, chunks are paired with Chunk Access Lists (CALs): compact state diffs that propagate separately (c.f. EIP-7928). CALs allow validators to reconstruct pre-state quickly and even validate chunks in parallel.

2/ As gas limits grow, monolithic blocks become bottlenecks (compress → propagate → decompress → execute). Semantic chunking redefines a block as a sequence of self-contained chunks, each independently verifiable and executable on arrival.

Blockchains must scale. Other chains bet on sharding, speculative parallelism, or micro-blocks. Ethereum can cherry-pick what works: streaming execution via semantic block chunking. Full post: https://t.co/dWic2isXQ5 TL;DR 👇

Glamsterdam BALs (@nero_eth) - Breakout on Wednesday covered several points. - Discussed handling of precompile. - Nothing major to report; still on track for the first devnet by October. ePBS (@terencechain) - Breakout scheduled for tomorrow. - Spec released yesterday:

EIP-7928 lets Ethereum process non-conflicting transactions in parallel instead of sequentially. Single threaded -> multi threaded tx processor.

Fast finality is not just a meme. It's actually coming. Slot time reduction is graduating from the research phase. @MorphNetrunner and I have been working on prototypes and now ours successfully transition from 12s to 6s and remain stable over several epochs. Check out the code

Working strong on Eip-7928 in reth, things coming up pretty good :) @mattsse_ @nero_eth @SoubhikSMP https://t.co/kaW0u5Kpj7

Block-level access lists are going to open the door to parallel transaction execution optimizations in the EVM. The first set of tests are out now thanks to @fselmo2:

@ethereumfndn is seeking a Protocol Tester focusing on the Consensus Layer. You'll work alongside engineers and researchers advancing the Ethereum protocol refining the `consensus-layer` specifications and its test suite. Link with more info to apply in next tweet!

8/ Compatible with ePBS (EIP-7732) & Delayed Execution (EIP-7886). Chunking reduces latency, smooths bandwidth, and scales with higher gas limits. Full post: 🔗

7/ Benefits: - Streaming validation (lower latency) - Parallel execution & proving - Stateless friendliness - Future extensibility (zk-proofs, sharded exec)

6/ Networking: - Lightweight beacon block gossiped normally - Heavy execution chunks streamed across parallel subnets (beacon_chunk_sidecar_{i}) - Enables immediate parallelization; partial custody possible later

5/ Consensus Layer: - Beacon blocks include chunk_roots - Sidecars prove inclusion via Merkle proofs (similar to blobs) - Fork choice waits for all chunks to be available + validated

4/ Execution Layer: - New header field: <chunk_count> - Chunks contain ≤2²⁴ gas of txs max (+ optional pre-state for stateless exec) - Only roots are committed on-chain; sidecars carry the heavy data (txs, withdrawals, etc.)

3/ With Payload Chunking: - Chunks can be executed while other chunks are still downloading -Validation starts immediately -Multiple cores can execute chunks independently & in parallel - Bandwidth load spreads across slot