abi section is present in your pipeline configuration.
Applicability
ABI decoding only applies to the following topic entities:logs- raw event logs emitted by smart contracts.transactions- raw transaction calldata submitted to the network.
Decoders
The pipeline provides two decoders, each responsible for a different entity type:| Decoder | Input Entity | Output Tables |
|---|---|---|
| EventDecoder | logs | {chain_name}_evt_{event_name} tables |
| FunctionDecoder | transactions | {chain_name}_fn_{function_name} tables |
Data Flow
Configuration
Add theabi section to your pipeline configuration to enable decoding:
Fields
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
path | string | Yes | — | Path to the ABI JSON file. Must conform to the standard Solidity ABI JSON format. |
contract_addresses | list | No | — | Optional list of contract addresses to filter on. When omitted, all contracts are decoded. |
unmatched | string | No | skip | Strategy for records that do not match any ABI entry. skip drops the record; raw_table writes it to raw_logs or raw_transactions. |
Next Steps
Event Decoding
Decode event logs into structured evt_ tables.
Function Decoding
Decode transaction calldata into structured fn_ tables.
Reference
ABI file format, type mappings, and filtering behavior.