Skip to content

op-reth: Carry --txpool.enforce-tracked-nonce from reth#28526 #24321

Closed

Description

@aakoshh

Carry paradigmxyz/reth#28526 on the reth fork and repin the monorepo to the new tag, so op-reth can turn on --txpool.enforce-tracked-nonce. This follows the transaction-delay investigation behind ethereum-optimism/infrastructure-services#1767. That PR fixes the already known errors in proxyd through deployment config, and it treats the delayed inclusion as a separate txpool race on the sequencer.

Background

  • paradigmxyz/reth#26980: under sustained load, validation against a stale account snapshot can insert a transaction below the sender's tracked nonce as pending. The sender's later, valid transactions then stop being selected.
  • paradigmxyz/reth#26981 (75d5872086604ff3d84889ef3792df48e6955188) adds the opt-in fix PoolConfig::enforce_tracked_nonce. It is already in op-v2.7.0-1, which develop pins today, but it is off by default and TxPoolArgs::pool_config hard-codes it. The only way to turn it on is to replace the pool builder.
  • paradigmxyz/reth#28526 (3e88af42a04264f1ad32d1bde14f67025de152be, merged 2026-11-13) adds the --txpool.enforce-tracked-nonce flag, off by default. No upstream release contains it yet.

op-reth builds its pool from ctx.pool_config() (rust/op-reth/crates/node/src/node.rs), so the flag reaches the OP pool with no op-reth code change.

Tasks

Fork (ethereum-optimism/reth)

  • Cherry-pick 3e88af42a04264f1ad32d1bde14f67025de152be with -x onto op-v2.7.0. Its tip is op-v2.7.0-1 (ed91041f36b973eda3521ff90b3a25165087c133). A dry-run merge applies cleanly; it touches crates/node/core/src/args/txpool.rs and docs/vocs/docs/pages/cli/reth/node.mdx.
  • Open a fork PR, then merge it once reth-act passes.
  • Tag op-v2.7.0-2 on the merge commit.

Monorepo

  • Repin rust/Cargo.toml from op-v2.7.0-1 to op-v2.7.0-2, and update the op-v2.7.0-1 references in op-reth source comments (follow the update-reth skill).
  • Regenerate the op-reth CLI snapshot (rust/op-reth/crates/cli/tests/snapshots/cli.snap) for the new flag.
  • Add a test showing that --txpool.enforce-tracked-nonce reaches op-reth's final pool config, including through pool_config_overrides.

Downstream

  • Repin optimism-premium to the monorepo merge commit and the new reth tag.
  • Release op-reth with the new pin.

Rollout (out of scope for the code change, tracked here)

  • Decide with infra which nodes enable --txpool.enforce-tracked-nonce. Upstream recommends it mainly for chains without reorgs and with very short block times: a reorg can leave the tracked sender state older than the validation snapshot. The sequencer is the main candidate. Check what this means for replicas, and for the sequencer after an unsafe reorg.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

A-op-rethArea: op-rethR-depsOp-Reth: dependencies

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions