Ethereum EIP-7708 proposes standardized logs for ETH transfers

Reviewing transfer visibility

EIP-7708 lists November 1, 2026, as its Last Call deadline in the official document. Created on May 17, 2024, the Ethereum proposal still shows Last Call when checked. It would automatically generate a log for ETH transfers covered by its rules, letting services follow those movements through a common mechanism. This review milestone is distinct from a feature already activated on mainnet.

The starting point is a difference from ERC-20 tokens, whose events are often used to track transfers. ETH sent by ordinary accounts can be found in transaction lists, but transfers from smart-contract wallets are not automatically recorded in the same way. The document describes historical difficulties recognizing certain deposits, not a newly announced incident.

A common event for several operations

The proposal defines a log comparable to ERC-20’s Transfer event, identifying sender, recipient, and amount in wei, ETH’s base unit. A protocol system address would emit it, distinguishing automatic records from user-contract events. Standardization would not turn ETH into a new company-issued token.

Rules cover nonzero-value transactions to another account, certain internal calls, and value supplied during contract creation. The text also covers eligible SELFDESTRUCT-related transfers. Ordering matters: a transaction’s transfer event would precede other execution-generated logs. Zero-value cases, reverted operations, and rolled-back internal calls feature among the planned negative tests.

Explicit limits avoid duplicated data

The mechanism does not cover every balance change. Priority-fee payments and base-fee burning were considered but excluded from the described scope: clients can already derive those amounts from block and receipt information. Consensus withdrawals likewise lack a natural transaction attachment and already have accessible records. Clients could optionally provide an aggregated RPC view.

The document acknowledges an increase in average log count, while arguing that the mechanism does not raise the theoretical maximum per block under its stated conditions. Tests must cover ordinary and delegated wallets, contract creation, failures, and the rule transition. For tracking-tool developers, the issue is more uniform transfer records. November 1 marks consultation of an older proposal, not guaranteed integration across every service.