以太坊研究日报
Four more EIP-8141 changes were submitted: lightclient split a frame's `gas_limit` into `execution_gas_limit` and `state_gas_limit`; AnkushinDaniil banned SLOTNUM in validation prefixes and noted that frame receipts carry no transaction-level status, after Nethermind and ethrex reported `0x1` and `0x0` respectively for the JSON-RPC `status` of the same transaction. The system addresses of EIP-8250 and EIP-8272 were pinned to addresses ending in 8250 and 8272. trent_vanepps explained the 10 EIPs in Glamsterdam.
(lightclient), submitted: a frame's `gas_limit` splits into `execution_gas_limit` and `state_gas_limit`; execution gas stays (generally) a call-frame-level concept while state gas is a frame-level concept, to clear up the remaining edge cases between frames and EIP-2780, 7623, 7708, 7825 and 8037.
(AnkushinDaniil), submitted: the validation prefix already bans opcodes whose value changes between admission and inclusion, such as `TIMESTAMP`, `NUMBER`, `PREVRANDAO`, `BASEFEE` and `BLOBBASEFEE`, since otherwise a transaction could pass simulation at admission and revert on inclusion; EIP-7843's `SLOTNUM` (`0x4B`) has the same property.
(AnkushinDaniil), submitted: `ReceiptPayload` has no transaction-level status field, but JSON-RPC receipts have `status`; on a Nethermind/ethrex devnet, the same transaction with a reverting SENDER frame was reported as `0x1` by one client and `0x0` by the other, while all consensus fields matched.
And EIP-8272: pin RECENT_ROOT_ADDRESS to 0x…8272 (AnkushinDaniil), submitted; both known implementations independently chose the address equal to the EIP number, matching 8141's `EXPIRY_VERIFIER = 0x…8141` convention.
EIP-8250: pin NONCE_MANAGER to 0x…8250 and EIP-8272: pin RECENT_ROOT_ADDRESS to 0x…8272 (AnkushinDaniil), submitted; both known implementations independently chose the address equal to the EIP number, matching 8141's `EXPIRY_VERIFIER = 0x…8141` convention.
04:15.
05:52, aimed at migrating the signature layer of onchain and agent identity to post-quantum, relying on recomputation rather than trust; the author argues that "adding a post-quantum signature alongside the classical one" does not actually close the gap.
(hanniabu), submitted as EIP-8359: an optional 32-byte beacon block body field where validators report CL/EL clients, setup type and multi-node threshold for client diversity statistics; forum, 04:41.
New EIP: Beacon Block Reporting Field (hanniabu), submitted as EIP-8359: an optional 32-byte beacon block body field where validators report CL/EL clients, setup type and multi-node threshold for client diversity statistics; forum, 04:41.
Submitted; the March 2025 exploit of about $355K came from a transient storage slot used for pool address verification being overwritten for another purpose.
03:52; Barnabé: praising a project by jalilwahdat, jackbutcher and others that became the second-largest gas-consuming contract in the 24 hours it was open, 02:34.
Growthepie: TokenWorks' new app generated over $170k in Ethereum gas fees in under a month, 03:52; Barnabé: praising a project by jalilwahdat, jackbutcher and others that became the second-largest gas-consuming contract in the 24 hours it was open, 02:34.
00:19.
01:50.