add-timelock-monitoring

What problem does it solve?

This Skill streamlines adding a new timelock contract to the monitoring system so Envio can index the right events and the monitoring script can reliably produce Telegram alerts.

Core Features & Use Cases

• Timelock type identification: Determine the correct timelock “type” by verifying the exact scheduling event signature from the on-chain contract ABI.
• Coordinated onboarding across repositories: Make the required Envio indexer changes first (to ensure events are indexed) and then update monitoring configuration (to route alerts to the correct Telegram protocol/channel).
• Support for both existing and new timelock types: Reuse an existing contract type mapping when the event signature matches, or define a new contract type plus handler when it does not.
• Operational verification: Provide a concrete validation run that backfills recent events to confirm the new timelock is functioning end-to-end.

Quick Start

Follow the deployment order by first updating and deploying the Envio indexer for the new timelock type or address, then update monitoring timelock configuration and verify with a backfill run using the provided command.