Skip to content

fix: bump streamingfast/reth to v2.3.0-fh-7 #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sduchesneau merged 1 commit into from
Aug 10, 2026
Merged

fix: bump streamingfast/reth to v2.3.0-fh-7 #21

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions CHANGELOG.sf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,15 +10,26 @@
### Changed

* Bumped base to `v1.2.0`.
* Kept `streamingfast/reth` at `tag = "v2.3.0-fh-5"` — upstream `v1.2.0` did not move off reth
`v2.3.0`, revm `40.0.3` or alloy-evm `0.36.0`, so no new Firehose reth release is required.
* Bumped `streamingfast/reth` dependencies from `tag = "v2.3.0-fh-5"` to `tag = "v2.3.0-fh-7"`.
Upstream `v1.2.0` did not move off reth `v2.3.0`, revm `40.0.3` or alloy-evm `0.36.0`; the two new
Firehose tags carry balance-change fixes only (see below), so the `Cargo.lock` diff is purely the
git tag/rev of the `streamingfast/reth` source.
* Added `reth-eth-wire-types` to the `[patch."https://github.com/paradigmxyz/reth"]` table.
Upstream `v1.2.0` began depending on it directly; without the patch entry it would resolve to a
second copy from `paradigmxyz/reth` alongside the Firehose fork's copy.
* Stopped tracking the `.dev/` scratch directory and added it to `.gitignore`.

### Fixed

* The SELFDESTRUCT refund is now included when resolving an account's post-transaction balance
(`streamingfast/reth` fh-7). revm credits the beneficiary in place and records the move only
inside its `AccountDestroyed` journal entry on the truly-destroyed path (EIP-6780), so a coinbase,
sender or fee vault that received a suicide refund reported a `RewardTransactionFee` /
`GasRefund` `old_balance` contradicting the `SuicideRefund` event emitted moments earlier. The
same resolver backs the OP fee-vault credits.
* Value-transfer balance changes are now emitted when a transaction sends value to a precompile and
then fails (`streamingfast/reth` fh-6); the reverted callee had its `BalanceTransfer` journal
entry truncated before the journal walk ran, dropping both balance changes.
* Replaced the stale `base-firehose-tests` `nop_transfer` full-protobuf golden with a JSON
projection plus property invariants. The full-block golden recorded `gas_limit: 30000000` for the
EIP-4788 beacon-roots system call while the current tracer reports `31566720`; the projection
Expand Down
Loading
Loading