investigate-merkle-root-mismatch

Name: investigate-merkle-root-mismatch
Availability: InStock
Author: hyperlane-xyz

Diagnose merkle root mismatches between relayer and validators using endpoints, S3 checkpoints, and Grafana.

72|602|Updated Dec 13, 2021

Search Tags:#debugging #investigation #blockchain #validator #root-mismatch #relayer #merkle

Ready to run

npx skills add https://github.com/hyperlane-xyz/hyperlane-monorepo --skill investigate-merkle-root-mismatch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate-merkle-root-mismatch
Source: https://github.com/hyperlane-xyz/hyperlane-monorepo/tree/main/.claude/skills/investigate-merkle-root-mismatch
Command: npx skills add https://github.com/hyperlane-xyz/hyperlane-monorepo --skill investigate-merkle-root-mismatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables engineers to diagnose merkle root mismatch alerts between the relayer and validators, helping pinpoint where the divergence began and guiding remediation steps.

Core Features & Use Cases

Investigate alerts related to merkle root mismatch, checkpoint root mismatch, or merkle proofs.
Identify the first mismatched leaf by comparing validator checkpoints with relayer data and summarizing the findings for engineering teams.
Prepare an actionable remediation plan and ready data for the /fix-merkle-root-mismatch workflow.

Quick Start

Use the investigate-merkle-root-mismatch skill when a merkle root mismatch is detected to start the investigation, gather data, and prepare for remediation.

Frequently Asked Questions about investigate-merkle-root-mismatch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I investigate a merkle root mismatch between a relayer and validators?▼

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.

What causes checkpoint root mismatch alerts across blockchain networks?▼

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.

How do I find the first mismatched leaf in a merkle proof investigation?▼

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.

Does the merkle root mismatch investigation automatically fix validator divergence?▼

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.

Can I manually investigate merkle root mismatches without an alert trigger?▼

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.

What data sources do I need to diagnose a merkle root mismatch?▼

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.