What problem does it solve?
When an OP Stack fault dispute game misbehaves — a challenger disagreeing with proposals, making excessive moves, or contradicting itself — operators need a structured, read-only way to determine which op-node is at fault, whether proposals are valid, and who ultimately wins the bonds.
Core Features & Use Cases
- Incident Triage: Identify which games and claims are involved, whose node is responsible, and whether in-progress proposals are valid.
- Root Cause Diagnosis: Cross-check output roots, super roots, and block hashes against canonical reference nodes to pinpoint a faulty op-node or incomplete safe-head database.
- Post-Incident Analysis: Determine bond outcomes after a game resolves.
- Use Case: During a live incident where a challenger keeps countering a proposal, use the skill to enumerate games with
op-challenger list-games, verify the canonical output root with check-output-root, and explain which node diverged — all without making any on-chain moves.
Quick Start
Ask the assistant to investigate why the challenger is disagreeing with the current dispute game proposal and which op-node is at fault.
