Same familiar topic:

Transfer(address,address,uint256)
0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef

Your eth_getLogs pipeline can treat native ETH like a token event.

In @ethereumjs/vm:

const result = await runTx(vm, { tx, block })
const logs = result.receipt.logs

No new API beyond Hardfork.Amsterdam.
If the tx reverts → empty logs (as today).

Decode with @ethereumjs/evm:

decodeEIP7708TransferLog(log)
→ { from, to, value }

One value transfer → 1 log in our example.

Burn logs use Burn(address,uint256) on balance-removal paths.

Run it (Node 20+, any OS):

mkdir amsterdam-7708 && cd amsterdam-7708
npm init -y
npm i @ethereumjs/vm@10.1.3 @ethereumjs/block@10.1.3 @ethereumjs/common@10.1.3 @ethereumjs/tx@10.1.3 @ethereumjs/util@10.1.3 @ethereumjs/evm@10.1.3 tsx

Copy runTxTransferLogs.ts →

npx tsx runTxTransferLogs.ts

github.com/ethereumjs/eth…

The gotcha:

Zero-value transfers → no log.
Contract calls with value → yes.
Indexers must not assume *only* ERC-20 contracts emit Transfer.

Bloom filters change — watch false positives.

Also: EIP-2780 bundles the transfer log into intrinsic gas (thread 1).

Experimental — not production.

Next: bigger contracts + CREATE2 factory (EIP-7954 / 7997). 🚀