docs: add Solver7702Delegate docs

[igorroncevic]

Description

Adds a solver-facing guide for using Solver7702Delegate to keep the existing solver EOA while using auxiliary EOAs for parallel settlement submission.

Changes

• Add a new Solver7702Delegate tutorial under solver docs.
• Document the direct vs delegated transaction shape and packed calldata format.
• Cover setup, verification, monitoring, caller replacement, revocation, and compromised key handling.
• Link the guide from solver onboarding and driver submission docs.

Summary by CodeRabbit

• Documentation
  • Enhanced solver driver documentation with improved formatting for auction preprocessing steps and procedures.
  • Added guidance for solvers implementing parallel settlement submission capabilities using Solver7702Delegate.
  • New comprehensive tutorial documenting Solver7702Delegate implementation, covering setup procedures, verification requirements, deployment guidance, auxiliary account funding, and operational best practices with security considerations.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	May 25, 2026 9:14am

[coderabbitai]

Warning

Review limit reached

@igorroncevic, we couldn't start this review because you've used your available PR reviews for now.

Your plan includes 1 review of capacity. Refill in 57 minutes and 39 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: bc08c90d-2b73-4b3c-8e87-dd009fa66485

📥 Commits

Reviewing files that changed from the base of the PR and between b8dcd6e and becef24.

📒 Files selected for processing (1)

• docs/cow-protocol/tutorials/solvers/solver-7702-delegate.md

📝 Walkthrough

Walkthrough

This PR documents the Solver7702Delegate feature for parallel settlement submission under ERC-7702. It introduces a new comprehensive tutorial page explaining the nonce-lane model, setup procedures, verification steps, and operational guidelines, then cross-references this new feature in existing solver documentation with minor formatting improvements.

Changes

Solver7702Delegate Documentation

Layer / File(s)	Summary
New Solver7702Delegate tutorial page docs/cow-protocol/tutorials/solvers/solver-7702-delegate.md	Complete new tutorial covering parallel submission architecture with auxiliary EOAs, calldata packing format (bytes20(target) || targetCalldata), contract behavior (fallback-only, immutable caller bytecode, CALL-only forwarding), setup for reference and custom drivers, bytecode verification (computing expected runtime from artifact and caller set), submission guidance (direct vs. delegated, transaction simulation), and operational procedures (funding auxiliary EOAs, caller replacement/revocation, compromised-key response, warnings, and FAQ).
Cross-references and formatting updates docs/cow-protocol/tutorials/arbitrate/solver/driver.md, docs/cow-protocol/tutorials/solvers/onboard.md	Driver tutorial reformatted Preprocessing auctions steps to hyphen-prefixed list items and added a note in Submitting settlements section linking to Solver7702Delegate for parallel submission. Onboarding tutorial added guidance under API specifications mentioning Solver7702Delegate for parallel settlement while maintaining existing solver EOA with additional nonce lanes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A delegate arrives in style so neat,
Seven-seven-oh-two makes submissions fleet!
Parallel lanes for the solvers so keen,
New docs light the path to this ERC-7702 scene. 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely describes the main change: adding documentation for Solver7702Delegate.
Description check	✅ Passed	The description follows the template structure with clear Description and Changes sections, providing specific details about what was added.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/solver-7702-delegate

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/cow-protocol/tutorials/arbitrate/solver/driver.md`:
- Line 58: Update the wording in the sentence fragment "discarding orders that
can definitely not be settled (e.g. user is missing balances)" to improve flow
by replacing "can definitely not be settled" with "definitely cannot be settled"
or "cannot be settled" (e.g., change to "discarding orders that definitively
cannot be settled (e.g. user is missing balances)" or "discarding orders that
cannot be settled (e.g. user is missing balances)").

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0b6db3ef-bbe4-447c-94a1-6b2c9ddc530b

📥 Commits

Reviewing files that changed from the base of the PR and between 978e255 and b8dcd6e.

📒 Files selected for processing (3)

• docs/cow-protocol/tutorials/arbitrate/solver/driver.md
• docs/cow-protocol/tutorials/solvers/onboard.md
• docs/cow-protocol/tutorials/solvers/solver-7702-delegate.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Tighten wording at Line 58 for readability.

“can definitely not” reads awkwardly; use “definitely cannot” (or “cannot be settled”) for smoother flow.

🧰 Tools

🪛 LanguageTool

[style] ~58-~58: Adverbs do not typically appear between the words ‘can’ and ‘not’. To make your writing flow more naturally, try moving the adverb and using the form ‘cannot’.
Context: ...oken decimals) - discarding orders that can definitely not be settled (e.g. user is missing balanc...

(CAN_RB_NOT)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/cow-protocol/tutorials/arbitrate/solver/driver.md` at line 58, Update
the wording in the sentence fragment "discarding orders that can definitely not
be settled (e.g. user is missing balances)" to improve flow by replacing "can
definitely not be settled" with "definitely cannot be settled" or "cannot be
settled" (e.g., change to "discarding orders that definitively cannot be settled
(e.g. user is missing balances)" or "discarding orders that cannot be settled
(e.g. user is missing balances)").