transaction event is emitted whenever the user performs a transaction.
It includes the transaction status (started, broadcasted, confirmed, reverted, rejected), recipient address, data, value, transaction hash, chain ID, and wallet address.
Properties
Each entry in
function_args is also flattened into the event’s top-level properties for easier querying. For example, function_args: { foo: "bar" } also adds foo: "bar" as a property.Builder Codes
The Formo data platform automatically detects and extracts ERC-8021 builder codes from transaction calldata. Builder codes are an onchain attribution standard that lets apps identify themselves in transactions. When a transaction includes an ERC-8021 data suffix, Formo parses it and includes thebuilder_codes field in the transaction event. For example, a transaction with the builder code "uniswap" would include "builder_codes": "uniswap" in the event properties.
This works automatically - no additional configuration is needed. If your app appends builder codes to transactions, Formo will detect and attribute them.