add-timelock-monitoring

Onboarding a new DeFi governance timelock requires updating the Envio indexer configuration to index scheduling events and then updating the monitoring routing configuration to direct Telegram alerts to the correct channel. Deployment order is critical for end-to-end verification.

Event signature matching verifies the exact scheduling event signature from the on-chain contract ABI. If the signature matches an existing mapping, you reuse it; if not, you define a new contract type plus handler in the Envio indexer config.

A backfill verification run is needed to confirm the new timelock is functioning end-to-end. It backfills recent events using a specific lookback window and cache control to ensure the Envio indexer and monitoring script reliably produce Telegram alerts.

Yes, you can add additional timelock addresses for existing protocols across multiple chains and timelock event schemas. The process supports multi-repo changes, requiring coordinated updates in the Envio indexer config and event handler mapping.

Timelock contract addresses must use lowercase format in the monitoring configuration. Ensuring exact lowercase address configuration prevents routing mismatches when the monitoring script processes indexed events and sends Telegram alerts.

The correct deployment order for adding timelock monitoring is to first update and deploy the Envio indexer for the new timelock type or address, then update the monitoring timelock configuration, and finally verify with a backfill run using the provided command.