indexing-wildcard

Wildcard indexing captures ERC-20 Transfer events across every contract address on a chain. You declare a contract in your configuration without specifying addresses, allowing the indexer to match that event signature network-wide for analytics and monitoring.

During wildcard indexing, you identify the emitting contract by passing wildcard:true to your handlers and reading event.srcAddress. This attribute provides the actual contract address that fired the event for accurate storage and attribution.

To reduce event volume during chain-wide indexing, apply eventFilters to your wildcard configuration. You can filter by parameter values, address lists, or functions to limit captured events, reducing noise and indexing cost.

No, wildcard contract configuration removes the need to pre-list contract addresses for blockchain event monitoring. It matches a specific event signature across the entire chain, enabling token activity aggregation without maintaining exhaustive address lists.

Common use cases for chain-wide event indexing include capturing all ERC-20 Transfer events for token analytics, monitoring builder-attributed order fills across an exchange, and aggregating on-chain metrics without managing address lists.

The best way to aggregate on-chain metrics without address lists is wildcard indexing. By configuring a wildcard contract to match event signatures chain-wide, you capture relevant activity across all addresses for comprehensive analytics.