Skip to main content
Filters can come in many forms, but there are a couple primary use cases: wallet and contract addresses. Filters also work twice per pipeline:
  1. They are applied for each network beat to determine if a beat should even be processed.
  2. After processing, the resulting records are filtered again using the pipeline’s filterKeys.

Example

Let’s say we want to filter vitalik.eth’s token transfers. We’d first add a filter for his address, 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045. From there, we could test the following transformation against an Ethereum block containing a token transfer (e.g. block 22062886 with this tx):
NOTE: the above transformation does not have its own filter step. Instead, we can specify during testing and in the pipeline to filter by from, to, or both.
^ this will provide a filtered set of token transfers like this: