sherwood-vault-monitor

You can detect on-chain vault anomalies by configuring a cron job to run scheduled checks with a vault address and chain, outputting a single anomaly alert when redemptions are locked or the vault is unmanaged.

An anomaly alert triggers when read-only calls detect specific issues like redemptions locked without an Executed proposal, or an unmanaged vault with zero active agents, ensuring alerts surface only for genuine problems.

Vault anomaly monitoring relies entirely on read-only on-chain calls to assess vault health and governance states, requiring no write access or transaction signing to detect issues and output silent or alert results.

To stop false alerts when monitoring vault health across chains, the system outputs a silent result by default and surfaces alerts only when specific anomaly conditions like locked redemptions or zero agents are met.

Checking for locked redemptions requires reading the redemptionsLocked state and cross-referencing governance proposal states to identify if an Executed proposal exists, alongside checking getAgentCount for unmanaged vaults.

You can use cron to schedule cross-chain vault health checks by configuring the job with a specific vault address and chain, enabling automated monitoring across multiple networks to detect anomalies.