indexing-filters

Name: indexing-filters
Availability: InStock
Author: Envio

Filter blockchain events with static arrays, dynamic per-chain functions, or address lists.

43|9|Updated Apr 8, 2026

Search Tags:#blockchain #dynamic-filters #event-filtering #indexed-parameters #address-filtering

Ready to run

npx skills add https://github.com/enviodev/polymarket-v2-indexer --skill indexing-filters

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: indexing-filters
Source: https://github.com/enviodev/polymarket-v2-indexer/tree/main/.claude/skills/indexing-filters
Command: npx skills add https://github.com/enviodev/polymarket-v2-indexer --skill indexing-filters

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Processing every blockchain event can overwhelm resources and increase costs. Developers need a way to limit handlers to only relevant events based on indexed parameters such as addresses or specific fields.

Core Features & Use Cases

Static array filters: Define fixed lists of indexed values to include or exclude events.
Dynamic per-chain functions: Generate filters at runtime based on the current chain identifier, allowing conditional activation.
Contract address filtering: Automatically limit events to a set of registered contract addresses.
Enable/disable logic: Return false to completely skip processing on unsupported chains.

Quick Start

Use the indexing-filters skill to apply static or dynamic filters to your event handler definitions.

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 to reduce processing load?▼

Filtering blockchain events reduces processing volume by applying static arrays, dynamic per-chain functions, or address lists to event handlers. This limits execution to relevant indexed parameters, preventing resource overload.

Can I dynamically generate event filters based on the current blockchain?▼

Yes, you can dynamically generate event filters based on the current blockchain. Dynamic per-chain functions evaluate the chain identifier at runtime to generate filters, allowing conditional activation or complete skips for unsupported networks.

How do I skip processing events on unsupported chains in HyperIndex?▼

You skip processing events on unsupported chains in HyperIndex by using enable/disable logic within dynamic filter functions. Returning a boolean false value completely disables event processing for that specific chain.

How do I limit blockchain event handlers to specific contract addresses?▼

You limit blockchain event handlers to specific contract addresses by using contract address filtering. This automatically restricts event processing to a registered set of addresses defined within your event handler options.

What is the best way to exclude specific indexed values from blockchain events?▼

The best way to exclude specific indexed values from blockchain events is by defining static array filters. These fixed lists explicitly include or exclude events based on specific indexed parameters or addresses without runtime evaluation.