Event Log

Overview

Event Log is the protocol record created when EVM contract code executes a logging instruction. A log contains the emitting contract address, up to several indexed topics, and an arbitrary data field. The transaction’s Blockchain Receipt collects the logs produced during successful execution.

Applications use event definitions to decode topics and data into names and typed values. A token contract might emit a `Transfer` event identifying sender, recipient, and amount. Indexers can filter indexed fields efficiently, which makes logs useful for wallets, explorers, analytics, and payment monitoring.

Logs are not persistent contract state. They provide historical evidence for off-chain consumers but do not directly control future execution. A contract can update state without emitting an expected event, or emit a misleadingly named event if its code is malicious. Critical verification should compare logs with the contract and resulting state.

Failed or reverted execution does not leave the intended logs in the canonical receipt. Systems should first confirm receipt status, contract address, chain, and event signature. Decoding a log with the wrong interface can assign convincing but incorrect labels to raw bytes.

A blockchain event can be broader than an event log. Native transfers, block production, or state differences may be detected without an emitted log. Payment applications should state whether a record is directly emitted, inferred from a Transaction Trace, or derived from indexed Blockchain Data.

Log indexing must handle contract upgrades and chain reorganizations. A proxy can emit familiar events while changing implementation logic, and a replaced block removes its logs from the canonical history. Consumers should key records by chain, block hash, transaction hash, and log index, then reverse derived actions when that identity is orphaned.