Bump reth latest→v2.1.0 #10

claude · 2026-06-19T06:02:50Z

claude commented

2026-06-19 06:02:50 +00:00

Bump reth latest → v2.1.0

Closes StakeSquid/vibe-node#53.

What changed

Bumps reth.Dockerfile from latest to v2.1.0 (image: ghcr.io/conduitxyz/conduit-op-reth:v2.1.0).

Note: latest and v2.1.0 resolve to the same digest (sha256:0a998950…) as of 2026-06-17 — no-op image change, but pins to an explicit tag going forward.

Changelog / release notes

https://github.com/paradigmxyz/reth/releases/tag/v2.1.0

Hardfork?

No — reth v2.1.0 does not introduce a new hardfork. (The Karst fork activated 2026-06-17 under separate op-node config; not in scope here.)

Breaking changes?

SDK-level only — node operators on default configurations are unaffected:

revm bumped to v38 (EIP-8037 state gas support)
alloy bumped to 2.0.0
CachedStateMetrics decoupled from SavedCache
WorkerPool is now lazy by default
next_available_nonce_for is now modifiable

Custom payload, transaction pool, or consensus integrations should review the reth v2.1.0 changelog before upgrading.

Storage v2 migration tooling is included — worth reviewing at rollout, but no operator action needed for this bump.

Asset

This PR carries the reth.Dockerfile change only. The companion context.yml bump rides a vibe-node PR on the same branch (vupd/53-reth-v2.1.0). Both must merge before deploy.

Rollout plan

After both PRs merge:

deploy-compose-repo scoped to one host running op.superseed.sepolia (identify via run-show-status at deploy time).
Verify: sync-status on test host — container reports v2.1.0, no crashloop, block height advancing.
Close issue #53, then fleet roll fire-and-forget.

## Bump reth latest → v2.1.0 Closes StakeSquid/vibe-node#53. ### What changed Bumps `reth.Dockerfile` from `latest` to `v2.1.0` (image: `ghcr.io/conduitxyz/conduit-op-reth:v2.1.0`). > **Note:** `latest` and `v2.1.0` resolve to the same digest (`sha256:0a998950…`) as of 2026-06-17 — no-op image change, but pins to an explicit tag going forward. ### Changelog / release notes https://github.com/paradigmxyz/reth/releases/tag/v2.1.0 ### Hardfork? No — reth v2.1.0 does not introduce a new hardfork. (The Karst fork activated 2026-06-17 under separate op-node config; not in scope here.) ### Breaking changes? SDK-level only — **node operators on default configurations are unaffected:** - `revm` bumped to v38 (EIP-8037 state gas support) - `alloy` bumped to 2.0.0 - `CachedStateMetrics` decoupled from `SavedCache` - `WorkerPool` is now lazy by default - `next_available_nonce_for` is now modifiable Custom payload, transaction pool, or consensus integrations should review the reth v2.1.0 changelog before upgrading. Storage v2 migration tooling is included — worth reviewing at rollout, but no operator action needed for this bump. ### Asset This PR carries the `reth.Dockerfile` change only. The companion `context.yml` bump rides a vibe-node PR on the same branch (`vupd/53-reth-v2.1.0`). **Both must merge before deploy.** ### Rollout plan After both PRs merge: 1. `deploy-compose-repo` scoped to one host running `op.superseed.sepolia` (identify via `run-show-status` at deploy time). 2. Verify: `sync-status` on test host — container reports `v2.1.0`, no crashloop, block height advancing. 3. Close issue #53, then fleet roll fire-and-forget.

claude added 1 commit 2026-06-19 06:02:50 +00:00

reth: bump Dockerfile RETH_VERSION from v1.4.3 to v2.1.0 bcdd950eb6

sebastian merged commit 5076c90a12 into main

2026-06-19 06:23:21 +00:00

sebastian deleted branch vupd/53-reth-v2.1.0

2026-06-19 06:23:22 +00:00

sebastian referenced this issue from a commit

2026-06-19 06:23:22 +00:00

Merge pull request 'Bump reth latest→v2.1.0' (#10) from vupd/53-reth-v2.1.0 into main

Sign in to join this conversation.