Skip to content

Bump Base to v1.5.6 - #43

Open
dfuse-bot wants to merge 7 commits into
release/1.xfrom
bump/base-1.5.6
Open

dfuse-bot wants to merge 7 commits into
release/1.xfrom
bump/base-1.5.6

Conversation

@dfuse-bot

@dfuse-bot dfuse-bot commented Nov 19, 2026 •

Copy link
Copy Markdown

Merges upstream Base v1.5.6 into release/1.x. Tag v1.5.6-fh3.1 on the merge commit once merged (v1.5.5-fh3.1 with the upstream version replaced; the Firehose block model is unchanged, so fh3.1 stays).

Upstream recommends this release for Base mainnet and Base Sepolia, with no deadline and no hardfork. It changes deposit gas accounting in the EVM handler, keeps the consensus L1 watcher running through L1 RPC outages, and writes a merkle rebuild_threshold of 450,000 blocks when it creates a new reth.toml.

v1.5.6 keeps upstream's reth pin (base-v2.5.2.11) and alloy-evm 0.38 (revm 42), so streamingfast/reth stays on base-v2.5.2.11-fh3.1 and streamingfast/evm on v0.38.0-sf. No other StreamingFast repository needs a release first. firehose-tracer stays on 5.7.0.

Besides the merge:

  • Only Cargo.lock conflicted: kept ours, and cargo added upstream's new reth-config dependency. Cargo.toml gets a [patch] entry for reth-config, pinned to the same streamingfast/reth commit as the other reth crates (24849d77d, base-v2.5.2.11-fh3.1), so there is a single reth-config in the lock.
  • Deposit gas (upstream [backport] fix(evm): align deposit gas accounting base/base#6672). Deposits are now exempt from the EIP-7825 transaction gas limit cap (16,777,216, active since Azul) during execution, not only validation. A deposit with a higher gas limit runs with its whole limit, and only the gas it uses is reported. The Firehose tracer takes the root call's gas limit from the frame and gas_used from the execution result, so it follows with no code change. New test crates/execution/firehose-tests/tests/deposit_gas.rs traces deposits at 16,000,000, 16,777,216, 16,777,217 and 20,000,000 gas and checks the root call gas limit, gas consumed, return data (the GAS left), gas_used and the receipt. It fails on the v1.5.5 handler (root call capped at 16,756,216) and passes on v1.5.6.
  • ACTIVATIONS.md: statuses refreshed against v1.5.6; the Azul row notes the deposit exemption. No new upgrade and no schedule change.
  • CHANGELOG entry below.

Dependency table check: the fork pins streamingfast/reth (release/base-2.x, still at the tagged commit) and streamingfast/evm (release/0.x), as the release tracker lists. streamingfast/evm release/0.x has moved on to v0.39.0-sf (revm 43), which this release does not use, so the pin stays on v0.38.0-sf. No public StreamingFast repository pins this fork: a code search for v1.5.5-fh3.1 finds nothing, and for v1.5.4-fh3.1 only our deployment configuration. Battlefield has a base-devnet target, which the chain-update skill's notes still say is missing.

CHANGELOG

## v1.5.6-fh3.1

### Changed

* Rebased on upstream Base `v1.5.6`, recommended for Base mainnet and Base Sepolia with no
  deadline. Uses `streamingfast/reth` `base-v2.5.2.11-fh3.1`; `firehose-tracer` stays on 5.7.0 and
  the Firehose block model is unchanged.
* Upstream exempts deposit transactions from the EIP-7825 transaction gas limit cap during
  execution. The root call of a deposit with a gas limit above 16,777,216 now gets the whole gas
  limit minus the intrinsic gas, and its `gas_used` is only the gas it used.

Test Execution Summary

Branch bump/base-1.5.6: release/1.x at v1.5.5-fh3.1 + git merge v1.5.6, built against streamingfast/reth base-v2.5.2.11-fh3.1 (24849d77d) and streamingfast/evm v0.38.0-sf (0ac393245), both fetched from GitHub.

Build Status

  • cargo build --release --package base-reth-node --bin base-reth-node --package base-consensus --bin base-consensus (same command as Dockerfile.sf): PASSED (4 min)
  • cargo check --workspace --all-targets: PASSED, after forge soldeer install && forge build in crates/utilities/test-utils/contracts
  • cargo clippy -p base-reth-node -p base-execution-firehose -p base-firehose-tests -p base-common-evm -p base-node-runner --tests: PASSED. The warnings are in crates/firehose-flashblocks/src/processor.rs, crates/execution/firehose, crates/execution/flashblocks/src/traits.rs and crates/execution/runner/tests/firehose_live_tracing.rs, which this merge does not change. None in the new test.

Unit Tests

Package Status Notes
cargo test -p base-firehose-tests PASSED 15 tests: the new deposit_gas test, 12 EIP-8130 tests, 2 prestate replays
cargo test -p base-firehose-flashblocks PASSED 44 tests
cargo test -p base-reth-node PASSED 2 tests
cargo test -p base-execution-firehose PASSED no unit tests in the crate
cargo test -p base-common-evm PASSED 155 passed, 1 ignored; includes upstream's two new deposit gas tests
cargo test -p base-execution-chainspec PASSED 49 passed, 1 ignored (upstream)
cargo test -p base-common-genesis PASSED 103 tests
cargo test -p base-common-chains PASSED 52 passed, 1 ignored (upstream)
cargo test -p base-execution-payload-builder PASSED 148 passed, 1 ignored
cargo test -p base-reth-cli PASSED 16 passed, 1 ignored
cargo test -p base-builder-multiplex PASSED 16 tests, including in_process_smoke
cargo test -p base-execution-cli PASSED 128 passed, 1 ignored; covers upstream's snapshot download change
cargo test -p base-consensus-node PASSED 412 passed, 1 ignored; covers upstream's L1 watcher change
cargo test -p base-node-runner FAILED (not merge-related) 9 unit and integration tests pass, including upstream's 3 new merkle tests. The BaseNode::provider_factory_builder doctest (crates/execution/runner/src/node.rs) does not compile: it sets ReadOnlyConfig { watch_static_files }, a field our reth fork does not have (it is watch). Same failure as on the v1.5.4 and v1.5.5 bumps; the doc example is unchanged upstream
cargo test -p reth-firehose -p reth-firehose-tests (in streamingfast/reth at 24849d77d, base-v2.5.2.11-fh3.1) PASSED 35 + 2 tests

Integration Tests

  • Status: PASSED
  • RUSTFLAGS="-C debug-assertions=off" RUST_MIN_STACK=33554432 cargo test -p base-system-tests --test firehose_denim --test firehose_b20 --test firehose_cobalt_b20, Docker-backed:
Test Status Time
firehose_b20::b20_transfer_is_traced PASSED 139.9 s
firehose_cobalt_b20::cobalt_b20_surfaces_are_traced PASSED 51.3 s
firehose_denim::denim_activation_block_traces_base_time_install PASSED 51.4 s

Battlefield Tests

  • Status: PASSED
  • Pass/Fail: 91 passing, 47 pending, 0 failing
  • streamingfast/battlefield-ethereum at adb1921 (master), base-devnet target, with this branch's release base-reth-node and base-consensus as the Firehose node. Upstream has not published ghcr.io/base/node:v1.5.6 yet, so the sequencer runs the base target of upstream's v1.5.6 tag built locally (docker buildx bake -f etc/docker/docker-bake.hcl base) and served from a local registry, because the launcher always pulls the image:
    BASE_REPO=<this checkout> BASE_NODE_IMAGE=<local registry>/base-node:v1.5.6 ./scripts/base/run_base_devnet.sh
    BASE_RETH_NODE_BINARY=<this checkout>/target/release/base-reth-node \
      BASE_CONSENSUS_BINARY=<this checkout>/target/release/base-consensus \
      ./scripts/run_firehose_base_devnet.sh
    pnpm test:fh3.1:base-devnet
  • The devnet runs Base's own upgrades: Azul, Beryl and Cobalt at blocks 20 to 22, Denim at 25 (200 ms blocks from there on) and Everest at 30. Every Base test passed: the Denim BaseTime predeploy install, the BaseTime deposit and distinct Firehose times for blocks sharing a header timestamp, the B-20 precompile tests, the Everest nonce manager install, and both EIP-8130 transaction tests. Header corresponds to RPC and Compare blocks: Firehose blocks match RPC blocks passed. No snapshot changed, and the node log has no ERROR and no panic (about 900 blocks). The reader node reported base-1.5.6.
  • The 47 pending tests are gated on features this chain does not have (Amsterdam/BAL, slot number, Transfer logs, blobs, Arbitrum, and other chains' upgrades), plus "Reverted token creation keeps its writes in the trace", which the Battlefield README lists as a known pending case for this tracer.
  • Coverage of this release's change: the devnet's deposits (the L1 info and BaseTime system deposits) have gas limits far below 16,777,216, so Battlefield does not reach the deposit gas change. crates/execution/firehose-tests/tests/deposit_gas.rs covers it. Zenith is genesis-only and no devnet schedules it, so the Keystore account changes are covered only by the unit tests in base-firehose-tests.

Firehose bug patterns

  1. Serial order: the deposit gas change is per-transaction accounting in BaseHandler::tx_gas. The L1 watcher (consensus), the merkle stage threshold (pipeline trie stage, which executes nothing) and snapshot download do not run the EVM on the traced executor or reorder transactions. None found.
  2. Emit after accept: no change to engine validation, consensus checks or the reth fork. The merkle rebuild_threshold only decides whether the pipeline's merkle stage rebuilds the trie or applies the range's changes; the state root check that follows execution is unchanged. None found.
  3. Activations: v1.5.6 changes nothing in crates/common/chains, crates/common/genesis or crates/utilities/upgrade-signal, and defines no new BaseUpgrade. The deposit gas change is not fork-gated, but it only changes anything where EIP-7825 applies, which is from Azul on (active on mainnet and Sepolia): deposits with a gas limit above 16,777,216 now run with their full limit. Everest is still not scheduled: no timestamp in the code, and getSchedule() on the configured L1 protocol_versions_address still reverts on both L1s (checked 2026-11-18). Zenith is genesis-only. ACTIVATIONS.md refreshed.
  4. Fields: no change to the consensus, RPC or receipt types that feed the block, and no change to the reth mapper. None found.
  5. Hashes: no new transaction without a hash of its own. None found.

0x00101010 and others added 7 commits November 13, 2026 21:50
…base#6610 to v1.5.6) (base#6611)

* fix(runner): raise merkle rebuild threshold for 200ms blocks

* fix(runner): keep merkle default when changesets are pruned sooner; drop download hook

* fix(runner): restore merkle default if clean thresholds drop after a raise

* docs: restamp base-node-runner README in docs index

* fix(runner): write merkle rebuild threshold only when reth.toml is created

* fix(cli): set merkle default only on reth-generated configs; warn on failure
…kport base#6647 to v1.5.6) (base#6648)

* fix(consensus): keep the L1 watcher alive through L1 RPC outages (backport base#6647 to v1.5.6)

The L1 watcher gave up on a head's SystemConfig log fetch after 10
attempts and returned RetriesExhausted, which shut down the whole rollup
node. On base-sepolia-ha, a ~2 minute -32011 outage on the L1 proxy took
down two sequencers this way, and they then crash-looped on startup while
L1 was still unavailable.

Retry log fetches until they succeed or the node shuts down (backoff
50 ms to 5 s), since restarting cannot help when the new process needs
the same L1. While waiting, keep publishing safe and finalized L1 blocks
and hold the next head. Abandon a head only after L1 reports a different
block at its height (reorged out), so a canonical head's unsafe block
signer update is never skipped. Cancellation now also interrupts an
in-flight request.

Co-authored-by: Toshi <toshi-noreply@coinbase.com>

Adapted for v1.5.6, which has no L1 safe stream or safe/finalized watch
channels: while logs are failing the watcher keeps sending finalized L1
blocks to derivation.

Co-authored-by: Toshi <toshi-noreply@coinbase.com>

* docs: restamp consensus service README in docs index

Co-authored-by: Toshi <toshi-noreply@coinbase.com>

* fix(consensus): bound the L1 watcher's reorg check

The reorg check ran a bare get_block inside the select arm, so a slow L1
could hold up shutdown, the stream that keeps publishing during an
outage, and the log fetch. Race it against cancellation and a 2 s
timeout. A timed-out check keeps the head, as a failed one already does.

Co-authored-by: Toshi <toshi-noreply@coinbase.com>

---------

Co-authored-by: Toshi <toshi-noreply@coinbase.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Backport to releases/v1.5.6.
Deposits are exempt from the per-transaction gas limit cap, but the handler
applied the default transaction gas accounting to them. Deposits now use their
declared gas limit; non-deposit transactions are unchanged.

Adds regressions for deposit execution gas and for gas used when a deposit
calls a stateful precompile.
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.

4 participants