Bump reth latest→v2.1.0 (conduit-op-reth) + Karst hardfork config for op.superseed.sepolia #23
Reference in New Issue
Block a user
Delete Branch "vupd/671-reth-v2.1.0"
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?
Asset changes for op.superseed.sepolia — conduit-op-reth v2.1.0 + Karst
Related vibe-node PR: (companion source PR on StakeSquid/vibe-node with context.yml + node.env changes)
Issue: StakeSquid/vibe-node#671
Version
ghcr.io/conduitxyz/conduit-op-reth:latest→v2.1.0Release: https://github.com/conduitxyz/conduit-op-reth/releases/tag/v2.1.0
Hardfork: Karst — YES (was missing from vendored config)
Karst activated on superseed-sepolia at 2026-06-17T16:00:00Z (unix
1781712000).The fork time was missing from our vendored
rollup.jsonandgenesis.json; this PR adds it.The
fork-calendar.ymlentrykarst-op-sepolia-customwas already present (status: pending); this PRsupplies the actual timestamps for the superseed-sepolia custom-rollup assets.
Breaking changes
None in conduit-op-reth v2.1.0 itself. Changes: Proof History ExEx support added (#31).
Asset changes (this repo)
rpc/op/superseed/sepolia/rollup.json"karst_time": 1781712000rpc/op/superseed/sepolia/genesis.json"karstTime": 1781712000Source changes (vibe-node companion PR)
context.ymlop.superseed.sepoliarethclient_version: latest→v2.1.0env/op/superseed/sepolia/node.envOP_NODE_OVERRIDE_KARST=1781712000Developer verification
./update.shran clean (Errors: 0 files). Generated compose confirmed:SUPERSEED_SEPOLIA_RETH_VERSION:-v2.1.0OP_NODE_OVERRIDE_KARST=1781712000Rollout plan
force-recreate(required for bind-mounted rollup.json/genesis.json to take effect).sync-statusshows version stringv2.1.0, no crashloop, logs confirm Karst activation.Companion source PR (context.yml + node.env): StakeSquid/vibe-node#675
Both PRs must merge before deploy.