skills.rest
moose-code
moose-codeCOMMUNITY
Explore all skills by this author →
𝕏@jonjonclarkGitHub

indexing-wildcard

Index events matching a signature across all contract addresses on a chain.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Index events matching a signature across all contract addresses on a chain, enabling complete coverage without per-address configuration.

Core Features & Use Cases

  • Wildcard indexing by using no-address configuration to capture all relevant events.
  • Handler usage with event.srcAddress to identify which contract emitted the event.
  • Manage high event volume with eventFilters to refine results and control throughput.
  • Refer to deep documentation for comprehensive HyperIndex guidance.

Quick Start

Configure a wildcard ERC20 Transfer handler to index all matching events across every contract address on the chain.

Frequently Asked Questions about indexing-wildcard

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

FAQPage Schema
How do I index blockchain events across all contract addresses on a chain?▼

Wildcard indexing captures all events matching a specific signature across every contract address on a chain. By using a no-address configuration, you ensure complete coverage without needing to specify individual contract addresses.

How do I identify which contract emitted an event during wildcard indexing?▼

You identify the emitting contract by accessing the event.srcAddress property within your wildcard-enabled handler. This allows you to pinpoint the exact contract address that generated the event during full-chain indexing.

What is the best way to manage high event volume when indexing all contract events on a chain?▼

The best way to manage high event volume during chain-wide indexing is by applying eventFilters. This refines the captured results and controls throughput, preventing overload when processing vast amounts of blockchain data.

When should I use wildcard indexing instead of per-address configuration for blockchain events?▼

Use wildcard indexing instead of per-address configuration when you need full coverage of an event signature across an entire chain. It is ideal for auditing all activity or capturing events from every token contract without listing individual addresses.

Does wildcard event indexing work for auditing activity across an entire blockchain?▼

Yes, wildcard event indexing works for auditing activity across an entire blockchain. By capturing all events matching a signature without per-address configuration, it provides complete chain coverage for comprehensive auditing tasks.

Related Skills

Explore More Software Engineering Skills→
enviodevenviodev
43

indexing-filters

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

Official
Intermediate
bendruckerbendrucker
16

json

Process JSON data with jq filters for parsing, filtering, and transforming.

Community
Basic
enviodevenviodev
43

indexing-wildcard

Index contract events across all blockchain addresses using wildcard configuration.

Official
Intermediate
yearnyearn
12

add-timelock-monitoring

Configure Envio indexing and monitoring routing for new timelock contracts.

Official
Advanced