debug-validator-checkpoint-inconsistency

To diagnose validator checkpoint inconsistencies, compare origin and destination validator sets against multisigIsm.ts configurations to identify stalled or misenrolled validators and report stall status.

Mismatched latest checkpoints occur when validators stall or fall behind. The diagnostic surfaces the difference between latest signed checkpoints and checks alias mappings to pinpoint the inconsistent validator.

To check quorum health during a checkpoint inconsistency, assess whether current healthy validators meet the required threshold and identify high-priority risks when quorum is compromised.

Yes, you can leverage Prometheus metrics and multisigIsm.ts configurations to investigate validator stalls, report stall status, verify alias mappings, and assess quorum health across origin-destination pairs.

You can filter checkpoint diagnostics by providing a specific origin_chain with optional app_context and environment filters to narrow the investigation of validator stalls and checkpoint mismatches.

The best way to resolve behind validator alerts is to run a diagnostic that compares validator sets against multisigIsm.ts, assesses quorum thresholds, and outputs a structured diagnostic report for remediation.