May 5, 2025 · 5 min read · Why this EIP needed? Validators Cast Their Votes by Signing a Message Containing: LMD GHOST Vote: (beacon_block_root, slot) [explained below] Casper FFG Vote: (source, target) [explained below] Committee Index: (index), which identifies the v...
Join discussion
May 4, 2025 · 1 min read · Why this EIP neeeded? Currently, when the eth_feeHistory RPC method is called to fetch recent gas fee data, the EL queries the CL using the engine APIsengine_newPayloadV3 call to retrieve blobGasUsed and excessBlobGas. This creates unnecessary overh...
Join discussion
May 3, 2025 · 2 min read · This is a foundational EIP that will serve as a basis for future EIPs, enabling further standardization of request_type. Why this EIP neeeded? Currently, communication between the Execution Layer (EL) and Consensus Layer (CL) is limited to block cr...
Join discussion
May 2, 2025 · 2 min read · Why this EIP neeeded? Ethereum is scaling through a rollup-centric roadmap. The Dencun upgrade introduced blobs (EIP-4844), and initial monitoring showed network stability with the new gas target and a decrease in re-org rates. The inclusion of the ...
Join discussion
May 1, 2025 · 3 min read · Why this EIP neeeded? The current calldata cost allows a maximum block size of 7.15 MB, while the average block size remains around 100 KB. The goal is to reduce the maximum calldata usage by increasing its cost. This primarily impacts data-centric ...
Join discussion