investigate-merkle-root-mismatch

To investigate a merkle root mismatch, compare validator checkpoints from S3 with relayer endpoints and Grafana data to identify the first mismatched leaf across origin chains and domains. This process gathers supporting data to prepare a remediation plan.

Checkpoint root mismatch alerts occur when merkle roots diverge between relayers and validators across origin chains, domains, or environments. Investigating involves pinpointing where the divergence began by comparing validator checkpoints with relayer data.

Finding the first mismatched leaf requires comparing validator checkpoints against relayer data to isolate the initial divergence point. The investigation leverages relayer endpoints, S3 validator checkpoints, and Grafana data to validate findings.

No, the investigation does not apply fixes during the process. It strictly diagnoses the merkle root mismatch, identifies the first mismatched leaf, and prepares an actionable remediation plan with supporting data for a separate fix workflow.

Yes, you can manually investigate merkle root mismatches across origin chains, domains, and environments. The process supports both alert-driven and manual investigations to identify the first mismatched leaf and collect supporting data.

Diagnosing a merkle root mismatch relies on relayer endpoints, validator checkpoints from S3, and Grafana data. These sources validate findings by comparing the relayer and validator states to identify the first mismatched leaf.