indexing-filters

Filter blockchain events by indexed parameters with configurable eventFilters options.

2|3|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-filters-moose-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: indexing-filters
Source: https://github.com/moose-code/polymarket-indexer/tree/main/.claude/skills/indexing-filters
Command: npx skills add https://github.com/moose-code/polymarket-indexer --skill indexing-filters-moose-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Filtering blockchain events by indexed parameters reduces the volume of events that must be processed, saving compute and allowing faster analytics.

Core Features & Use Cases

  • Indexed filters: filter by indexed event fields to downselect events.
  • Flexible forms: supports array form (static), single-object form, and function form per chain for dynamic logic.
  • Chain-aware filtering: per-chain logic that can enable/disable on specific networks; supports address-based filters for registered contracts.

Quick Start

Configure eventFilters to filter ERC20.Transfer events by indexed fields to minimize processed events.

Frequently Asked Questions about indexing-filters

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I filter blockchain events by indexed parameters?

You can filter blockchain events by indexed parameters using configurable eventFilters to reduce processing volume, which cuts compute and enables faster analytics.

What is the best way to filter ERC20 Transfer events across multiple chains?

For ERC20 Transfer events across multiple chains, use chain-aware per-chain logic to dynamically enable or disable event filters on specific networks.

Can I use wildcard event filters for contract addresses?

Yes, you can use wildcard support within event filters for contract addresses, combining multiple filters with OR logic to match registered contracts.

Does indexed-field filtering support dynamic per-chain configurations?

Indexed-field filtering supports dynamic per-chain configurations through a function form, allowing custom filtering logic to be applied for each specific network.

Why do my event filters not work with non-indexed fields?

Event filters do not work with non-indexed fields because the filtering semantics strictly enforce indexed-field filtering only, providing safe fallback behavior for unsupported fields.

What forms can eventFilters take to reduce event processing volume?

The eventFilters option can take an array form for static filtering, a single-object form, or a function form per chain to apply dynamic logic and reduce event processing volume.