EIP-7906 gains two opcodes' worth of per-topic event views
Victoria Shinder1 min readA change to EIP-7906 has been merged into the Ethereum EIPs repository, adding per-topic-value event views under the TXDIFF parameters 0x0B and 0x0C. The commit came from AnkushinDaniil through pull request #12358 and was merged by EIP-Bot; it touches one file, EIPS/eip-7906.md, with 22 lines added and 2 removed.
The proposal's shape is visible in the diff. A single call returns one 256-bit value, and three stack inputs select which value: a param code, plus further selectors. The existing table includes entries such as 0x08, which takes no address and returns address_events_count. The new codes extend that table so a contract can read event data broken down per topic value rather than only in aggregate.
What it means
This is an incremental specification change, and it should be read as one. Nothing is deployed, no fork carries it, and an EIP in Draft can change again next week or stall permanently.
The direction is the interesting part. Giving contracts a structured read over transaction-level event data — counted and selectable by topic — moves work that is currently done off-chain by indexers into something a contract can query directly. That is attractive for anything that today needs an oracle or a trusted indexer to answer "how many times did this happen in this transaction", and it is exactly the kind of capability whose gas cost decides whether it is usable in practice. The diff does not settle that question, and neither does the merge.
For anyone tracking this: the useful signal is not the merge but whether the proposal acquires client implementations and a place in a fork's candidate list. Repository activity and consensus adoption are different measurements.