EIP-7708 - ETH transfers and burns emit a log

Created	2024-05-17
Status	Draft
Category	Core
Type	Standards Track
Authors
Requires	EIP-1559 EIP-4788 EIP-6780

Abstract

All ETH transfers and burns emit a log.

Motivation

Logs are often used to track when balance changes of assets on Ethereum. Logs work for ERC-20 tokens, but they do not work for ETH. ETH transfers from EOAs can be read from the transaction list in the block, but ETH transfers from smart contract wallets are not automatically logged anywhere. This has already led to problems in the past, eg. early exchanges would often not properly support deposits from smart contract wallets, or only support them with a much longer delay. This EIP proposes that we automatically generate a log every time a value-transferring CALL or SELFDESTRUCT happens. We also add a similar log for transfers in transactions, so that all ETH transfers can be tracked using one mechanism.

Specification

ETH transfer logs

A log, identical to a LOG3, is issued for:

Any nonzero-value-transferring transaction to a different account, before any other logs created by EVM execution
Any nonzero-value-transferring CALL to a different account, at the time that the value transfer executes
Any nonzero-value-transferring SELFDESTRUCT to a different account, at the time that the value transfer executes

Field	Value
`address` emitting log	`0xfffffffffffffffffffffffffffffffffffffffe` (`SYSTEM_ADDRESS`)
`topics[0]`	`0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef` (`keccak256('Transfer(address,address,uint256)')`)
`topics[1]`	`from` address (zero prefixed to fill uint256)
`topics[2]`	`to` address (zero prefixed to fill uint256)
`data`	`amount` in Wei (big endian uint256)

This matches the ERC-20 Transfer event definition.

ETH burn logs

A log, identical to a LOG2, is issued for:

Any nonzero-balance SELFDESTRUCT to self by a contract created in the same transaction, at the time the opcode is invoked
Any nonzero-balance account marked for deletion, at the time of removal during transaction finalization

Burn logs are emitted after all other logs created by EVM execution and the payment of the EIP-1559 priority fee to the coinbase. When multiple accounts are marked for deletion, burn logs are emitted in lexicographical order of account address.

Field	Value
`address` emitting log	`0xfffffffffffffffffffffffffffffffffffffffe` (`SYSTEM_ADDRESS`)
`topics[0]`	`0xcc16f5dbb4873280815c1ee09dbd06736cffcc184412cf7a71a0fdb75d397ca5` (`keccak256('Burn(address,uint256)')`)
`topics[1]`	`address` (zero prefixed to fill uint256)
`data`	`amount` in Wei (big endian uint256)

Rationale

This is the simplest possible implementation that ensures that all ETH transfers are implemented in some kind of record that can be easily accessed through making RPC calls into a node, or through asking for a Merkle branch that is hashed into the block root. The log type is compatible with the ERC-20 token standard, but does not introduce any overly-specific ERC-20 features (eg. ABI encodings) into the specification.

Open questions

Magic value used for address? For address: (a) 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee (same as eth_simulateV1), (b) 0xfffffffffffffffffffffffffffffffffffffffe (SYSTEM_ADDRESS), (c) zero address
Should fee payments trigger a log? It would ensure "completeness", in the sense that you can compute the exact current balance table by watching logs, but it would greatly increase the number of logs, perhaps to an unacceptably high amount.
Should withdrawals also trigger a log? They are not associated with transactions.

Backwards Compatibility

No backward compatibility issues found.

Test Cases

TODO

Security Considerations

ETH transfers already cost a minimum of 6700 gas, which is much more expensive than the LOG3 opcode (1500 gas). Hence, this EIP does not increase the worst-case number of logs that can be put into a block. It will somewhat increase the average number of logs.