Add CoW Protocol quote-verification debug skill#4369
Open
Conversation
Documents the end-to-end procedure for debugging why a CoW Protocol price
quote returned `verified: false` or "Insufficient Liquidity":
- Inputs and lookup paths: `quote_id` → `trace_id` (step 1), and the
no-quote-id case where the user only has a token pair (and optionally a
wallet address) → `trace_id` via `parsed.spans.calculate_quote.{sell_token,
buy_token}` cross-referenced against `request_summary` HTTP 404 (step 1b).
- Pulling per-estimator bids and identifying which solvers failed
verification (steps 2–3).
- Three replay options, with explicit requirements and tool-selection
guidance (step 4): reth `debug_traceCall` + an embedded `run_sim.py`
(programmatic; preferred for root-causing), Tenderly `/simulate` (saved,
shareable UI), and `cast call --trace` (foundry one-liner).
- Diagnosis (step 5): a 10-point reasoning playbook to anchor on the deepest
reverting frame, decode unknown selectors and revert payloads, account for
verifier overrides, and form testable hypotheses; a *non-exhaustive*
catalogue of common failure modes; and dedicated subsections for decoding
the solver's `interactions[3]`, OOG / gas binary search, and
balance/allowance forensics for silent reverts.
- Reporting (step 6): default output is a single sorted table over every
estimator, with Tenderly links + root cause for non-verified rows and
the `Err(...)` reason for no-quote rows.
- Cheat sheets for selectors and addresses commonly seen in verifier traces,
source-of-truth pointers, and gotchas (Tenderly upstream timeouts, the
`transaction_index=-1` rejection, MCP auto-saved query results, greedy
`extract`, the `0x…020000` precompile, 0x Settler revert bubbling, V4
Universal Router depth).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request introduces a comprehensive debugging guide for CoW Protocol quote verification failures. The documentation provides a structured workflow for resolving trace IDs, replaying simulations using Python scripts, Tenderly, or cast, and performing root-cause analysis on transaction reverts through call trace reasoning and interaction decoding. No critical issues were found.
MartinquaXD
approved these changes
May 5, 2026
Contributor
MartinquaXD
left a comment
MartinquaXD
left a comment
There was a problem hiding this comment.
Skill worked well when I tried it so I'm fine with merging it already. But some of the sections could use a bit more polish. I suspect the sections where I feel they lack context made sense together with the context window of the agent at the time. But when booting this into a clean context window I wonder if those parts can cause confusion.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Documents the end-to-end procedure for debugging quote competition
Changes
How to test
I also have the services as well as the infrastructure checked out so that claude can look at the implementation directly (which may help to do furhter root cause).