OpenParable
Skip to content
← Back to skills

Update Reth

Development
update-reth

Update Reth is an Agent Skill for development published in the ethereum-optimism/optimism repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Update the pinned upstream reth dependency across the Rust workspaces — pin bump, shared dependency sync, compile-and-adapt loop, full verification, and PR. Use when asked to bump, update, or upgrade reth (e.g. "update to reth v2.4.0").

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/ethereum-optimism/optimism/blob/HEAD/.claude/skills/update-reth/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/update-reth, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Update reth

Bump the paradigmxyz/reth pin (normally to the latest release tag) and adapt the OP Stack Rust workspaces to upstream API changes.

The complete procedure — pin audit, the four manifests, shared dependency sync, lockfiles, the compile-and-adapt loop, and verification — lives in rust/UPDATING-RETH.md. Read it in full first and follow it exactly; this skill only adds the agent workflow around it. Don't restate the guide to the user — execute it.

Arguments

Optional target: a release tag (v2.4.0), a commit sha, or an upstream PR number. Default: the latest upstream release tag (gh release list --repo paradigmxyz/reth).

Workflow

  1. Orient. Read the guide. Find a local paradigmxyz/reth checkout (ask the user if you can't find one) and fetch its tags — you'll need it for tag resolution, API archaeology, and diffing replicated code.

  2. Isolate. Work in a fresh git worktree (or jj workspace) based on latest develop — never on the main checkout's working copy. Run mise trust in the new directory.

  3. Execute the guide's procedure, including the current-pin audit before moving off it. Iterate the compile loop to green rather than enumerating breakages up front; don't ask the user to confirm each adaptation.

  4. Verify everything the guide lists before any push. On memory-constrained machines, wrap heavy builds in systemd-run --user --scope -p MemoryMax=<n>G with reduced -j (not ulimit -v, which SIGABRTs rustc).

  5. Ship. One commit (rust: update reth to <version>) describing the pin move, each shared dependency sync, and every API adaptation. Run the AI review before pushing — code, security, and the reth-update-reviewer agent (docs/ai/reth-update-review.md), which catches upstream changes that should have forced an op- change but produced no diff in our tree. PR to develop with verification results spelled out.

  6. Compound. If this bump taught you something the guide doesn't cover, fold it into rust/UPDATING-RETH.md in the same PR.