Transaction Event

Overview

A transaction event is generated while a transaction executes and records information intended for external consumers. Smart contracts may emit an event with a name, indexed fields, and encoded data. Indexers and applications use these records to detect transfers, deposits, configuration changes, and other state transitions without repeatedly scanning all contract storage. The event is linked to the containing transaction and block.

An event differs from the Transaction Result. The result states whether execution succeeded and may include return data or an error, while events describe occurrences within that execution. If a transaction reverts, its apparent events may be discarded or marked unsuccessful according to the protocol. Applications must therefore verify the receipt status before acting on a matching event.

Events are also not authoritative business records by themselves. A contract can emit misleading, incomplete, or duplicate-looking logs if its code is designed that way. The event schema and emitting program address must be verified, and relevant state changes may need independent confirmation. A token-transfer event from an imitation contract is not evidence that the expected asset moved.

Payment systems should store the chain, block, transaction ID, event index, emitter, decoded fields, and confirmation state. Event processing must be idempotent because nodes can resend logs and chain reorganizations can remove them. Fulfillment should wait for the required Protocol Finality, and reorganization handling should reverse effects associated with events that leave the canonical chain.

Production teams benefit from retaining the emitting program, block and transaction IDs, event index, decoded schema, and confirmation state. The record is especially useful because duplicate delivery, imitation contracts, reverted execution, and reorganizations can all create false business signals. Safeguards should process events idempotently and reverse derived records when their containing block leaves canonical history.