以太坊研究日报
Nethermind measured the frame transaction validation budget: once clients pause validation while processing a block, raising MAX_VERIFY_GAS to 300k is workable, which is the range private transfers and post-quantum accounts need. Trail of Bits published a four-step guide for signing systems after the Binance incident, stressing that 7702 delegations should be treated as admin privileges. A token-level Protected Accounts proposal appeared on Magicians. Francesco and Barnabé discussed what gas repricing really does.
Image: Trail of Bits, After Binance, check what your signing systems can approve
Posted at 06:26 by Stefano De Angelis, Daniil Ankushin and Manuel Arto of Nethermind. In a frame transaction the signature check is arbitrary EVM code in a VERIFY frame, and a node must simulate the validation prefix before admitting the transaction. If validation fails, nobody pays for that work, which is a DoS vector.
(published 11-06 US time; Trail of Bits announcement post at 00:53). The core point: if a server allowed to request signatures is compromised, a key can be misused without ever being extracted. A 7702 delegation is like the wallet signing a standing instruction, "use this code when my account is called", which stays in place until changed or cleared with the wallet's key, so funds deposited after the first theft were moved too. Four recommendations: reduce access to signing infrastructure; treat delegation as an administrative privilege; limit the damage even if signing is compromised; monitor changes in wallet authority. The post also notes that 7702 authorizations sit outside ordinary calldata, and that session keys, recovery paths, Safe modules and ERC-4337 UserOps all need monitoring too.
Trail of Bits: after Binance, check what your signing systems can approve (published 11-06 US time; Trail of Bits announcement post at 00:53). The core point: if a server allowed to request signatures is compromised, a key can be misused without ever being extracted. A 7702 delegation is like the wallet signing a standing instruction, "use this code when my account is called", which stays in place until changed or cleared with the wallet's key, so funds deposited after the first theft were moved too. Four recommendations: reduce access to signing infrastructure; treat delegation as an administrative privilege; limit the damage even if signing is compromised; monitor changes in wallet authority. The post also notes that 7702 authorizations sit outside ordinary calldata, and that session keys, recovery paths, Safe modules and ERC-4337 UserOps all need monitoring too.
Opened at 14:28. An optional "protected" flag for ERC-20s: small transfers are instant, transfers above the limit are queued and can be cancelled by a pre-registered backup wallet. A "stress" action cancels all pending transfers and moves the balance to the backup, locked for a preset duration the caller cannot choose, which also helps against coercion. Over-limit `transferFrom` calls revert, so routers and lending protocols cannot be fooled. The reference implementation is a 1:1 USDC wrapper (pUSDC) on Base Sepolia, built at ETHGlobal Mumbai. Turning protection on is instant; weakening it (turning it off, raising the limit, shortening the wait, changing the backup) waits for a delay the holder chooses.
18:57. Higher gas costs for state operations do not make them proportionally more expensive, because the gas limit is rising too.
16:20, commenting on an outside write-up: he disagrees with some of its assumptions but agrees with its conclusion that Glamsterdam should proceed. He says there are really two classes of invariants, the first being "parameters" such as the gas cost of an operation (the post is cut off at that point).
00:35, a private message board on Aztec Tierra. Connect an Ethereum wallet and post under any name or anonymously; no wallet address is attached to posts. Based on an experiment by Vitalik and completed by Zac (Aztec blog: RollingChat private messaging board).
Aztec: RollingChat goes live, 00:35, a private message board on Aztec Tierra. Connect an Ethereum wallet and post under any name or anonymously; no wallet address is attached to posts. Based on an experiment by Vitalik and completed by Zac (Aztec blog: RollingChat private messaging board).
05:51. Even when a transaction is private, network traffic can reveal the sender; wallets and dapps can route traffic through Nym to hide where it comes from.
04:43.
22:08.
Merged at 20:50.
Opened at 18:39.
02:08, deadline November 20.
01:32; Caspar: Ethereum will be a post-quantum, post-AI store of value, 18:49.
Barnabé: ethereum:native will be a post-quantum store of value, 01:32; Caspar: Ethereum will be a post-quantum, post-AI store of value, 18:49.
18:48.
12:58.
11:49, which will bring privacy ideals back.