3 posts tagged with "eip7702"

A small EIP-8141 text fix landed on Friday. The frame-transaction draft had accidentally priced zero calldata bytes at 16 gas and nonzero bytes at 64; the intended EIP-7976 floor is 64 for both. Execution specs already counted the bytes correctly, so this was not a client fix or a live-network bug.

It did send me back to current mainnet calldata. Across the 14 complete UTC days from August 7 through August 20, one executeBatch target accounts for 30.01 billion of the 67.87 billion added gas in a fixed-path EIP-7976 backcast. That is 44.22% from one address, and 85.7% of the affected calldata bytes sent to it were zero.

The previous type-4 post left one obvious loose end. The labelled Poisoner target was the gas-heavy part of EIP-7702's type-4 surface, so I half-expected it to be private orderflow or at least hard to see before inclusion.

It was the opposite. From Jun 30 through Jul 6 UTC, Xatu saw every one of the 31,565 canonical type-4 transactions sent to that target in its mempool table. The barely visible bucket was the much smaller executeBatch tail.

Type-4 transactions are easy to count and easy to overread. From Jun 20 through Jul 3 UTC, Ethereum had 257,388 deduped type-4 transactions, which was only 0.824% of all transactions in the same blocks. That sounds like a small EIP-7702 adoption number until you look at the gas: one address labelled Poisoner and a pile of plain ERC-20 transfer(address,uint256) calls consumed 86.5% of type-4 gas.

That is the trap. transaction_type = 4 tells you the envelope is EIP-7702's set-code transaction type. It does not, by itself, tell you this is a clean smart-wallet action, a user operation, or even something interesting at the authorization-list layer.