indexing-config

HyperIndex config.yaml files require specifying EVM chains, contract addresses, start_block values, and event selections. You validate the schema and apply per-contract overrides to ensure correct blockchain indexer setup for local or hosted environments.

Envio HyperIndex config files use environment variables prefixed with ENVIO_ for development and deployment scenarios. They allow dynamic configuration across local development, CI pipelines, and hosted Envio services without hardcoding sensitive values.

Selecting events and fields in a HyperIndex config.yaml involves specifying desired events under each contract and requesting transaction or block fields globally or per-event. Custom event naming helps structure the indexed data effectively.

Envio HyperIndex supports per-contract overrides for start_block selection, event definitions, and address format options. Individual contracts within the same config.yaml can target different blocks and use custom event names independently.

When editing an Envio config.yaml file, avoid deprecated options that conflict with current YAML schema validation. The reference identifies outdated structures and ensures you use supported fields for chains, contracts, and environment variable usage.