Skip to main content
The decoded.logstable contains decoded event logs based on the available contract ABIs. Users can identify the desired event logs by the contract address and event topic0.

Using Decoded Logs

Using Decoded Logs
  • In general, we recommend using this combination of params and params_keys_mapping on all of your production pipelines, since it guarantees that your query won’t break if the decoded key names ever change.
  • Logs are decoded via topic0, but they do not specify the name of the params. As a result, there may be inconsistencies in the decoded params field while the underlying values are correct.
Field name changes over time are influenced by contract ABIs used during log decoding. We prioritize contract-specific ABIs but may fall back to generic ABIs.Historical records aren’t retroactively updated to maintain query consistency.

Using Params Key Mapping

Using Uniswap v3 Swap() event params as an example, we first reference the params field:
Then look at the params_keys_mapping:
From there, rewrite the query using params[params_keys_mapping[index]] syntax:

Table Columns

Unique Key: transaction_hash, log_index