[dependabot]

Bumps reth-testing-utils from v2.5.0 to v2.8.0.

Release notes

Sourced from reth-testing-utils's releases.

Reth v2.8.0

Reth v2.8.0 schedules the Amsterdam hardfork on Hoodi, adds opt-in snap/2 sync and prewarm result reuse, and hardens peer-to-peer networking and RPC.

With the opt-in --engine.prewarm-reuse, reth commits prewarmed transaction results instead of re-executing them. This reduced mean latency by 12.35% and raised Mgas/s by 18.58% over 500 replayed blocks (#27894). Per-block proof-worker sizing reduced mean execution time on 300M-gas BAL blocks by 8.41% (#27196). RPC response compression no longer cuts throughput by up to 22x (#27863).

Action Required

Hoodi operators must upgrade before 26 October 2026 at 17:42:48 UTC. This release schedules Amsterdam on Hoodi at timestamp 1793036568 (epoch 132352) and extends the Hoodi fork IDs through Amsterdam. (Reth change, Hoodi schedule)

All operators should review the default and behavior changes under Breaking Changes, especially those affecting the gas price oracle, WebSocket origins and the minimum priority fee.

Update Priority

User Class	Priority
Payload Builders	Medium
Non-Payload Builders	Medium

Breaking Changes

Runtime and Configuration

• Changed the default gas price oracle ignore threshold (--gpo.ignoreprice) from 0 to 2 wei to match Geth, so zero-tip transactions no longer pull eth_maxPriorityFeePerGas down to 0. Set --gpo.ignoreprice 0 to restore the previous behavior (#27895).
• Enforced --ws.origins on WebSocket handshakes. Disallowed or duplicate Origin headers are now rejected with HTTP 403 on both separate and shared HTTP/WS listeners, so make sure every browser origin that connects over WebSocket is listed (#27952).
• Applied --txpool.minimum-priority-fee to legacy and EIP-2930 transactions by comparing their gas price against the floor, matching Geth. Previously only dynamic-fee transactions were checked (#27720).
• Pinned --engine.storage-worker-count and --engine.account-worker-count values now apply to every block and bypass the new per-block proof-worker sizing, and 0 now means unset. Unset them to use automatic sizing (#27196, #27660).
• Stopped compressing HTTP RPC responses on servers bound to a loopback address, including the default 127.0.0.1, even when clients request compression. If you rely on compression behind a local reverse proxy, enable it at the proxy (#27865).
• The metrics endpoint now serves at most four concurrent requests and returns HTTP 503 to the rest. It also gzips responses for clients that send Accept-Encoding: gzip (#27766).
• Renamed the trie cursor duration histograms to trie.cursor.overall_duration_seconds and trie.hashed_cursor.overall_duration_seconds, and moved hashed-cursor spans to the trie::hashed_cursor tracing target. Update dashboards, alerts and log filters that use the old names (#27771, #27772).
• Offline commands such as prune, stage drop and db clear now fail on a config file that exists but cannot be loaded, instead of falling back to defaults. reth p2p enode no longer creates a missing key file (#27982).

RPC

• engine_forkchoiceUpdated now returns -32603 with the builder's error when a payload job fails to start, instead of always returning -38003. Only invalid payload attributes still map to -38003 (#28015).
• Changed Parity trace_* output to match other clients. Deleted accounts report empty stateDiff storage, vmTrace ops and subs reflect only what executed, and reverted CREATEs return {gasUsed, output} without an address (#27668).
• testing_buildBlockV1 now returns an ExecutionPayloadEnvelopeV6 with blockAccessList and slotNumber for Amsterdam blocks. Pre-Amsterdam responses are unchanged (#27883).

SDK

• Added a required cause: Span field to BeaconEngineMessage::{NewPayload, RethNewPayload, ForkchoiceUpdated}, so tracing context follows Engine API requests into the engine and its workers. Pass Span::current(), or Span::none() when there is no context (#27529).
• Changed OnForkChoiceUpdated::Output to Result<ForkchoiceUpdated, BeaconForkChoiceUpdateError>. Custom payload builders that reject attributes should return the new PayloadBuilderError::InvalidAttributes to keep answering -38003 (#28015).
• Changed StorageRootMerkleCheckpoint::new to take an Account instead of separate nonce, balance and bytecode-hash arguments (#27501).
• Narrowed the trie APIs. Removed ComputedTrieData in favor of SortedTrieData, removed unused sparse-trie types and the rayon re-export from reth_trie_common, renamed the borrowing into_sorted_ref conversions to to_sorted_ref, made RangeProofError opaque, made several reth-trie-parallel internals private, removed Proof::multiproof_v2 and DbProof::overlay_multiproof_v2, and changed StateProofProvider::multiproof_v2 to take the targets and a requires_masks flag (#27794, #27793, #27792, #27769, #27789, #27785, #27791, #27770, #27790, #27788, #27945).
• Keyed PreservedSparseTrie by block hash. state_root() became block_hash(), pending() changed signature, and PreservedSparseTrieCompleter was removed (#27270).
• Custom BackfillSync implementations must handle the new BackfillAction::UpdateTarget variant (#27541).
• Reworked the test utilities. The reth-network test-utils testnet helpers are rebuilt around a PeerConfig builder, and the reth-e2e-test-utils payload submission helpers now fail on INVALID payloads (#27453, #27713).

Features

... (truncated)

Changelog

Sourced from reth-testing-utils's changelog.

Releases

Release cadence

reth does not currently have a regular release cadence while it is still experimental software.

For maintainers

This section outlines how to cut a new release.

It is assumed that the commit that is being considered for release has been marked as stable, i.e. that there is an expectation of no major bugs.

Release PR

• Create a new branch (e.g. release/vx.y.z) and open a pull request for it
• Ensure all tests and lints pass for the chosen commit
• Version bump
  • Update the version in all Cargo.toml's
• Commit the changes
  • The message format should be release: vx.y.z, substituting x.y.z for the semver.
• The PR should be reviewed to see if anything was missed
• Once reviewed, merge the PR

Releasing

• Tag the new commit on main with vx.y.z (git tag vx.y.z SHA)
• Push the tag (git push origin vx.y.z)[^1]
• Update Homebrew Tap
• Run the release commit on the testing infrastructure for 1-3 days to check for inconsistencies and bugs
  • This testing infrastructure is going to sync and keep up with a live testnet, and includes monitoring of bandwidth, CPU, disk space etc.

Note

The v prefix for the tag is important! If it is missing, the release workflow will not run.

When the tag is pushed, the artifacts are built automatically and a draft release is added to the repository. This draft release includes a template that must be filled out, including:

• A summary of the release (highlights etc.)
• The update priority (see below)
• An auto-generated changelog

The release artifacts are automatically added to the draft release. Once ready, simply publish the release.

Release summaries

The release summary should include general notes on what the release contains that are important to operators. These changes can be found using the https://github.com/paradigmxyz/reth/labels/M-changelog label.

[^1]: It is possible to use git push --tags, but this is discouraged since it can be very difficult to get rid of bad tags.

Commits

• 05ba481 fix(trie): complete range changesets (#27615)
• 2ce3552 chore: release 2.8.0 (#28039)
• f3fd194 chore(deps): bump revm-inspectors to 0.44.3 (#28034)
• fd936f9 chore(hive): regenerate no_sim_build.diff for hive's simulator build configs ...
• f88813a perf(trie): reuse known storage roots in proofs (#28016)
• b9a8eb3 feat(evm): customize executor in block builder (#28011)
• 482bdb0 refactor(trie): centralize multiproof v2 logic (#27945)
• 186af6d fix(engine): report payload job start errors (#28015)
• 49d736d chore(deps): bump astral-sh/setup-uv from 10.2.0 to 10.3.0 in the ci-weekly g...
• 3c9260d fix(era): share strict Snappy RLP decoding (#27997)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: rust. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4a6489c7-0cab-43af-ae8e-cf26073bb568

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.