[ninglinLiu]

Summary

The Unichain node repository switched its execution client from op-geth to op-reth in Uniswap/unichain-node#48. The Node Snapshots page still describes the old op-geth setup, and both of its "Base image" links now return 404 because PublicNode no longer publishes Unichain geth snapshots.

Changes on Unichain → Technical Information → Node Snapshots:

What	Before	After
Mainnet base image	snapshots.publicnode.com/unichain-geth-base.tar.lz4 (404)	snapshots.publicnode.com/unichain-reth-base.tar.lz4
Sepolia base image	snapshots.publicnode.com/unichain-sepolia-geth-base-0-13772176.tar.lz4 (404)	snapshots.publicnode.com/unichain-sepolia-reth-base.tar.lz4
Data directory	./geth-data	./reth-data (the HOST_DATA_DIR default in unichain-node's .env)
Extract + organize steps	extract, then mv ./geth/* ./geth-data/	extract straight into ./reth-data with -C (the reth archives hold static_files/, db/, ... at the top level, with no wrapping geth/ folder)
Log command	docker compose logs -f op-geth	docker compose logs -f execution-client (the service name in unichain-node's docker-compose.yml)

Also on Set Up a Node: "configures op-node and op-geth" becomes "op-node and op-reth" in the sentence about the unichain-node repo. The manual op-geth flags below it are unchanged, since they're still valid for anyone running op-geth themselves.

Type of change

• Fix (typo, broken link, incorrect or outdated content)
• New content (guide, page, code example)
• Update to existing content
• Other

How has this been verified?

• curl -I returns 404 for the two old geth URLs. The new reth URLs return 302 to the signed PublicNode download, and both are listed on https://www.publicnode.com/snapshots under Unichain.
• I read the first few MB of unichain-sepolia-reth-base.tar.lz4 and confirmed the first entry is static_files/... at the archive root, so extracting with -C ./reth-data gives the right layout.
• I checked docker-compose.yml, .env (HOST_DATA_DIR=./reth-data) and op-reth-entrypoint.sh on unichain-node main.

Anything else reviewers should know?

Docs only: 2 files, 12 lines added and 21 removed. This doesn't overlap with #1173–#1179. I used AI assistance to prepare it, then reviewed the change and verified every link and command above myself.

[github-actions]

Thanks for contributing to Uniswap Docs! 🦄

Quick heads up on how this repo works: the docs you see on developers.uniswap.org are built from a separate source repo. When we accept a change here, we port it over there, so your fix might show up on the live site before it lands in this repo.

Updates to this repo come in batches on a regular cadence. When yours is included, you'll be credited as a co-author on the commit, so the contribution counts on your GitHub profile and in Uniswap/docs.

We review every PR but can't merge everything. Either way, someone from the docs team will follow up here once we've taken a look.

One legal bit: by submitting a PR you agree your contribution is licensed under the repo's MIT license.

[github-actions]

Flagging per review policy: these are changed download URLs (unichain-geth-base.tar.lz4 → unichain-reth-base.tar.lz4, and the Sepolia equivalent). The PR description says the author confirmed the old links 404 and the new ones return a 302 to a valid PublicNode download, and that both are listed on publicnode.com/snapshots. I wasn't able to independently re-verify these URLs from this review environment (no outbound network access), so a maintainer should do a quick curl -I confirmation before merge.

[github-actions]

Flagging per review policy: the docker-compose service name changed from op-geth to execution-client. The PR description says this was checked against docker-compose.yml on unichain-node main. I couldn't verify this independently from this review environment (no outbound network access), so worth a quick confirmation against the current unichain-node repo before merge, since a wrong service name here would just break this one command for readers following along.

[github-actions]

Review summary

Reviewed the op-geth → op-reth update for the Unichain Node Snapshots guide (content/unichain/technical-information/node-snapshots.mdx) and the one-word fix in set-up-a-node.mdx.

Looks good overall:

• Step renumbering is internally consistent after removing the "Organize the data" step (now 1–5, no gaps/dupes).
• The tar ... -C ./reth-data extraction target matches the mkdir ./reth-data created in step 1.
• The rationale given (reth's flat static_files/db layout vs. geth's nested geth/ dir) is technically sound and matches how reth organizes on-disk state.
• No contract addresses, chain IDs, or frontmatter touched. No broken Markdown/MDX syntax.
• Prose and formatting are clean; no spam/promotional content.

Flagged inline for human verification (per review policy, any changed URL/command needs a sanity check — I don't have outbound network access in this review environment to confirm these myself):

1. The two changed PublicNode snapshot URLs (mainnet/Sepolia *-reth-base.tar.lz4) — PR author states they verified 404 on old links and 302 on new ones.
2. The docker compose logs -f execution-client service name change from op-geth — PR author states this was checked against unichain-node's docker-compose.yml.

Neither is a correctness concern with the PR's reasoning, just links/identifiers worth a final confirmation before merge since they're easy to silently get wrong.

[ninglinLiu]

Re-verified the two items flagged for human review (2026-10-27 13:40 UTC):

• Snapshot URLs: curl -I https://snapshots.publicnode.com/unichain-reth-base.tar.lz4 → 302 and .../unichain-sepolia-reth-base.tar.lz4 → 302; the old unichain-geth-base.tar.lz4 and unichain-sepolia-geth-base-0-13772176.tar.lz4 → 404.
• Service name: docker-compose.yml on Uniswap/unichain-node main defines execution-client (plus op-node, healthcheck-init); there is no op-geth service anymore, so docker compose logs -f execution-client is the correct command.