StakeSquid/ethereum-rpc-docker
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

zora-mainnet: add op-reth pruned-trace profile #20

Merged
sebastian merged 1 commits from issue-162 into main 2026-06-22 03:36:14 +00:00
Conversation 0 Commits 1 Files Changed 2 +150
claude commented 2026-06-22 02:12:53 +00:00
Collaborator
Copy Link

Summary

Adds zora-mainnet-op-reth-pruned-trace.yml — a new op-reth pruned-trace compose profile for Zora mainnet (chain ID 7777777).

Why: Zora is an OP Superchain member. The existing op-geth configs are broken post the 2026-06-19 Sepolia hardfork (op-geth can no longer follow the post-hardfork chain for Superchain members). op-reth is the correct replacement.

What changed:

  • New compose file: op/reth/zora-mainnet-op-reth-pruned-trace.yml
  • op-reth EL + op-node CL configured for Zora mainnet
  • OP_NODE_ROLLUP_CONFIG=/config/rollup.json in op-node env
  • Volume mount ./op/zora/mainnet:/config (rollup.json + genesis.json + reth.toml)
  • reth uses --chain=/config/genesis.json and --config=/config/reth/reth.toml
  • Standard Superchain setup, no custom DA

Verification: ./update.sh --filter op.zora.mainnet regenerated cleanly (0 errors). Full ./update.sh also clean (471 compose files, 0 errors).

rpc branch commit: 120c070a1e3b47c93d6a39bf5f89e6b7b8e6f219

(vibe-node issue #162)

## Summary Adds `zora-mainnet-op-reth-pruned-trace.yml` — a new op-reth pruned-trace compose profile for Zora mainnet (chain ID 7777777). **Why:** Zora is an OP Superchain member. The existing `op-geth` configs are broken post the 2026-06-19 Sepolia hardfork (op-geth can no longer follow the post-hardfork chain for Superchain members). op-reth is the correct replacement. **What changed:** - New compose file: `op/reth/zora-mainnet-op-reth-pruned-trace.yml` - op-reth EL + op-node CL configured for Zora mainnet - `OP_NODE_ROLLUP_CONFIG=/config/rollup.json` in op-node env - Volume mount `./op/zora/mainnet:/config` (rollup.json + genesis.json + reth.toml) - reth uses `--chain=/config/genesis.json` and `--config=/config/reth/reth.toml` - Standard Superchain setup, no custom DA **Verification:** `./update.sh --filter op.zora.mainnet` regenerated cleanly (0 errors). Full `./update.sh` also clean (471 compose files, 0 errors). rpc branch commit: `120c070a1e3b47c93d6a39bf5f89e6b7b8e6f219` (vibe-node issue #162)
claude added 1 commit 2026-06-22 02:12:53 +00:00
zora: add rollup.json and reth.toml for op-reth pruned-trace profile 120c070a1e
sebastian merged commit 0785ee5482 into main 2026-06-22 03:36:14 +00:00
sebastian deleted branch issue-162 2026-06-22 03:36:15 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude cursor rob sebastian
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#20
Delete Branch "issue-162"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?