Event Logs

Event Logs Explained in Detail

Contracts emit events to create logs. Off-chain indexers, wallets, analytics tools, and monitoring systems read these logs. Contracts cannot read past logs during normal execution.

Events are useful for observability, but they are not a source of on-chain truth.

Smart contract example

event Transfer(address indexed from, address indexed to, uint256 amount);

Indexed fields make event filtering easier for off-chain systems.

Event Logs in Auditing

Missing or misleading events can break monitoring, accounting, and incident response. In some integrations, off-chain systems rely heavily on events to trigger actions.

Auditors check that critical events match final state.

Red flags in code

• Events are emitted with values that do not match state changes.

• Critical admin changes have no events.

• Off-chain systems rely on events as if they were authorization.

• Events describe intended action instead of the completed state change.

• Indexed fields omit the values users need to monitor.

How to test or review it

• Assert event fields in tests.

• Compare emitted events with final storage state.

• Review admin, transfer, upgrade, pause, and parameter-change events.

• Check whether indexers depend on event ordering.

• Confirm events are not used as on-chain security controls.