fix-merkle-root-mismatch

To fix a relayer merkle root mismatch, you apply corrections via the merkle_tree_insertions API after supplying the origin, domain_id, environment, and payload details. This aligns the in-memory state with canonical sources to prevent inconsistencies.

A merkle root mismatch occurs when the relayer database diverges from canonical sources. Patching is needed after an investigation identifies the inconsistency, requiring explicit user confirmation before inserting corrections to ensure safe remediation.

Yes, applying merkle tree insertions to fix root mismatches may require kubectl port-forwarding and relayer access. This setup ensures you can safely reach the database to apply corrections and restart the relayer if needed.

You must supply the origin, domain_id, environment (default mainnet3), and a merkle_tree_insertions payload containing leaf_index, insertion_block_number, and message_id to correct a merkle root mismatch.

Yes, you can patch merkle root mismatches across relayer deployments including different environment scopes like mainnet3 and testnet4. You must specify the target environment when supplying the correction payload.

A relayer restart may be needed after applying merkle root corrections to ensure the in-memory state fully reloads and aligns with the patched database. This prevents lingering inconsistencies across the system.