Skip to content

chore(deps): bump op-stack to op-reth/v2.3.1 (reth v2.2.0)#324

Open
seolaoh wants to merge 1 commit into
Layr-Labs:masterfrom
celo-org:seolaoh/v2.3.1-on-upstream
Open

chore(deps): bump op-stack to op-reth/v2.3.1 (reth v2.2.0)#324
seolaoh wants to merge 1 commit into
Layr-Labs:masterfrom
celo-org:seolaoh/v2.3.1-on-upstream

Conversation

@seolaoh

@seolaoh seolaoh commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Bumps the op-stack dependencies from kona-client/v1.5.2 to op-reth/v2.3.1 (paradigmxyz/reth v2.2.0).

Rebased on top of the merged #325 (kona to 1.5.2), so it is now a Cargo.toml-only change:

  • The 12 kona workspace deps and the 9 [patch.crates-io] op-alloy / alloy-op / op-revm entries: retagged from kona-client/v1.5.2 to op-reth/v2.3.1.
  • The five exact alloy network pins (alloy-consensus, alloy-genesis, alloy-provider, alloy-rpc-client, alloy-rpc-types): =2.0.4 to =2.0.5.

The kona crate versions are identical at both tags, so no code changes are needed; only alloy core/primitives differ (alloy-core 1.5.7 to 1.6.0). Cargo.lock is updated to match.

Why: celo-kona feeds both celo-reth (the L2 node) and the proving stack, and cargo unifies git deps by source (URL + tag), so hokulea and celo-kona have to point at the same optimism tag. celo-reth is moving to op-reth/v2.3.1, so an op-reth/v2.3.1 build of hokulea available upstream lets us share a single dependency graph.

@bxue-l2 bxue-l2 mentioned this pull request Jun 9, 2026
On top of the merged kona-client/v1.5.2 (Layr-Labs#325), moving to op-reth/v2.3.1
is a Cargo.toml-only change: retag the 12 kona deps and the 9
[patch.crates-io] op-alloy / alloy-op / op-revm entries from
kona-client/v1.5.2 to op-reth/v2.3.1, and bump the five exact alloy
network pins from =2.0.4 to =2.0.5. kona crate versions are identical at
both tags; alloy-core moves 1.5.7 to 1.6.0. Cargo.lock updated to match.
@seolaoh seolaoh force-pushed the seolaoh/v2.3.1-on-upstream branch from 6217bcf to 4c04618 Compare June 11, 2026 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant