Repository navigation
Bump Base to v1.5.5 - #42
Merged
Merged
Conversation
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…ackport base#6477 to v1.5.5) (base#6484) * feat(builder): limit uncompressed block size in the native builder Add --builder.max-uncompressed-block-size to the native payload builder. It caps the cumulative EIP-2718 encoded size of a block's transactions. The Flashblocks builder already has this limit. Sequencer transactions always count toward the total. Pool transactions that would push the block past the limit are skipped for that block. The check uses the encoded length cached on each pooled transaction, so the build loop does no extra encoding. The limit is unset by default. (cherry picked from commit 6b14f87) * test(builder): cover sequencer bytes in the uncompressed block size limit (cherry picked from commit 20fbb91) * style: cargo fmt --------- Co-authored-by: Danyal Prout <git@dany.al>
* fix(tx-manager): compute transaction hash locally in publish_tx (base#5878) * fix(tx-manager): compute transaction hash locally in publish_tx Co-authored-by: Toshi <toshi-noreply@coinbase.com> * fix(tx-manager): address review round 1 findings Co-authored-by: Toshi <toshi-noreply@coinbase.com> * docs(tx-manager): document publish_tx local hash rule (review feedback) Co-authored-by: Toshi <toshi-noreply@coinbase.com> --------- Co-authored-by: Toshi <toshi-noreply@coinbase.com> (cherry picked from commit ec65d30) * feat(batcher): add min tip cap and min basefee flags (base#6427) The batcher always prices its L1 transactions with the priority fee its L1 node suggests, which is close to zero on Ethereum today. A fee bump doubles that tip, and doubling a near-zero tip keeps it near zero, so when L1 blocks are full a batch transaction can wait a long time before it is included. The tx manager already enforces a minimum tip cap and a minimum base fee, and the other services expose them through `define_tx_manager_cli!`. op-batcher has the equivalent `--txmgr.min-tip-cap` and `--txmgr.min-basefee` settings. Expose them on `base batcher` as `--min-tip-cap` / `BASE_BATCHER_MIN_TIP_CAP` and `--min-basefee` / `BASE_BATCHER_MIN_BASEFEE`, in gwei with decimal strings accepted, and pass them through `BatcherConfig` to the tx manager. Both default to 0, so nothing changes until an operator sets them. (cherry picked from commit 132bbc1) * feat(batcher): send a channel's blobs in one L1 transaction (base#6429) * feat(batcher): send a channel's blobs in one L1 transaction A blob transaction now takes the ready blobs up to and including the first one that holds a channel's last frame, at most max_blobs_per_tx. Blobs of a channel still open wait until they fill a transaction instead of each going out alone, since the safe head only moves once the channel's last frame is on L1. A ready calldata frame also ends the run, so blobs before it never wait behind it. DaEgress now builds new artifacts whenever the ready ones cannot be leased, instead of only when none is ready, so waiting blobs never stop the encoder from framing more output. * fix(batcher): keep a calldata cut when a blob run is requeued A calldata artifact now ends the blob run before it in any state, not only when ready. Once the calldata went out, a requeued run cut by it no longer waits for more channel output: it is leased again as the same transaction. Co-authored-by: Toshi <toshi-noreply@coinbase.com> --------- Co-authored-by: Toshi <toshi-noreply@coinbase.com> (cherry picked from commit 40a9ebf) * feat(tx-manager): add tx inclusion latency metric (base#6428) * feat(tx-manager): add tx inclusion latency metric Co-authored-by: Toshi <toshi-noreply@coinbase.com> * fix(tx-manager): record inclusion latency with the send latency Take the inclusion time from the canonical block that the receipt poller already reads, and record it in the same place as the confirmed send latency. Every confirmed send now records both, so the dashboard's included-to-confirmed series compares the same sends. This drops the extra block read and the case where it failed. * fix(tx-manager): export ConfirmedTx from the crate root Co-authored-by: Toshi <toshi-noreply@coinbase.com> * test(tx-manager): use mockall for the inclusion latency test Generate `MockTxMetrics` with `automock` instead of hand-rolling a `TxMetrics` double, as the repository testing rules require. The test now expects exactly one confirmed send latency of 0 ms and one inclusion latency of 19_700 ms. Co-authored-by: Toshi <toshi-noreply@coinbase.com> --------- Co-authored-by: Toshi <toshi-noreply@coinbase.com> (cherry picked from commit 3555800) --------- Co-authored-by: Jack Chuma <jack.chuma@coinbase.com> Co-authored-by: Toshi <toshi-noreply@coinbase.com>
…RE (base#6522) A mempool node forwards every transaction to every configured builder, and each builder that rejected it made the node journal a forward failure. The receiving builder already journals the same rejection as TXPOOL_VALIDATED_INSERT_REJECTED while it is the active sequencer, so the node-side row either duplicated the leader's verdict or recorded a standby or canary verdict that never decides inclusion. On mainnet (2026-11-08 09:00 UTC) these were 20.2M rows/hour, 17.6% of all transaction events, 88% of them from the two canary sequencers. Drop the emit and retire the event type; historical rows stay readable. Forwarding, failure reports to the reader, and the per-builder rejection metric are unchanged. TXPOOL_BUILDER_FORWARD_ATTEMPT and _DROPPED stay, since a send that never reaches a builder has no builder-side record. CHAIN-6721 (cherry picked from commit 34c165f)
… layer (backport base#6557 to v1.5.5) (base#6567) * feat(sequencer): seal payloads on execution freeze notifications Backport of base#6557 to releases/v1.5.5. * test(builder): exercise native payload-ready wiring * test(sequencer): cover searcher next-block inclusion with early broadcast * docs: update the docs index for frozen payload notifications * chore(payload): order the tokio dependency by line length * feat(sequencer): add early-seal metrics Count seals by trigger, record when getPayload and gossip happen relative to the slot start, and count frozen-payload hints sent by the builder and dropped by the sequencer. * docs(runner): note the exported prefix of early-seal metrics * fix(sequencer): seal early when a hinted rebuild reuses the last sealed payload id Track the frozen hint on the payload handle so it cannot outlive its build, and treat a hint as having lost to the deadline only when it matches no active build. * refactor(sequencer): drop the gossip offset metric It stopped at the handoff to the network actor rather than the publish, so it added little over the getPayload offset. * feat(sequencer): record when each block build starts in its slot A Denim build reads the transaction pool once, after the build is requested, so this offset is the deadline for landing in that block. * fix(sequencer): measure slot start from the parent timestamp on the release branch The isolated-sequencer schedule delay that block_deadline applies on main is not on releases/v1.5.5. * test(sequencer): pin when early-seal offsets are taken Cover build starts recorded outside the ticker, assert the getPayload offset is taken before the request, and describe the build start offset as part of the searcher reaction window. * docs: restamp the runner README in the docs index * test(builder): stop deriving multiplex smoke timestamps from wall clock (base#6455) Denim activated on mainnet, so the smoke test's wall-clock-based payload attributes became post-Denim attributes, which the engine rejects unless they carry the BaseTime update deposit at tx[1]. Anchor the build timestamp to the last legacy block slot before Denim activation instead: past every scheduled fork and still pre-Denim, so a single legacy block stays valid regardless of when the test runs. Amp-Thread-ID: https://ampcode.com/threads/T-09d6a81e-204d-45bb-a227-69764d686e37 Co-authored-by: Amp <amp@ampcode.com> (cherry picked from commit 407af44) --------- Co-authored-by: Julian Meyer <julian.meyer@coinbase.com> Co-authored-by: Amp <amp@ampcode.com>
…ase#6554, base#6555 to v1.5.5) (base#6569) Backport of base#6554 and base#6555 to releases/v1.5.5 as one change. The parking pool iterator now calls no_updates() on the reth standard pool, so every store (standard, sidecar, validity) is snapshotted when the iterator is created. A transaction that arrives mid-build waits for the next block instead of joining this one, closing bottom-of-block sniping by low-fee standard transactions and letting targeted backruns that arrive with their target compete on fee against resting validity transactions. Adds an integration-pool test that a late arrival waits for the next build in all three stores. (cherry picked from commit b8f6dfa) (cherry picked from commit c1cbcb4) Co-authored-by: Toshi <toshi-noreply@coinbase.com>
base-v2.5.2.11-fh3.1 points to the merge commit of the reth PR, whose tree matches the PR head the lock file held.
maoueh
approved these changes
Nov 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merges upstream Base
v1.5.5intorelease/1.x. Tagv1.5.5-fh3.1on the merge commit once merged.Upstream recommends this release for Base mainnet and Base Sepolia, with no deadline: it fixes the
eth_calllatency regression ofv1.5.4by returning--engine.memory-block-buffer-targetto reth's default of 5 blocks (70 inv1.5.4). It also makes the sequencer seal payloads as soon as they are built.v1.5.5keeps upstream's reth pin (base-v2.5.2.11) and alloy-evm 0.38, sostreamingfast/rethstays onbase-v2.5.2.11-fh3.1andstreamingfast/evmonv0.38.0-sf. No other StreamingFast repository needs a release first.firehose-tracerstays on 5.7.0 and the Firehose block model is unchanged, so the tag keepsfh3.1(v1.5.4-fh3.1with the upstream version replaced).Besides the merge:
crates/execution/payload/src/builder.rsonly. Intry_build, upstream sends a payload-ready hint for frozen sequencer builds (!no_tx_pool), and we trace blocks built from the payload attributes alone (no_tx_pool). Both are kept, along with upstream's comment in the closure. The two conditions never hold together.Cargo.toml: everystreamingfast/rethcrate and[patch]entry, and thealloy-evmpatch, is now pinned byrevwith the tag in a comment, instead of bytag.base-v2.5.2.11-fh3.1points to the merge commit of Bump Base reth to base-v2.5.2.11 reth#89 (24849d77d), whileCargo.lockheld that PR's head (9f9f5efa1). The two commits have the same tree, so no code changes.Cargo.lockchanges only those sources and the version of our Firehose crates.ACTIVATIONS.md: statuses refreshed againstv1.5.5; no new upgrade and no schedule change.Dependency table check: the fork pins
streamingfast/reth(release/base-2.x) andstreamingfast/evm(release/0.x), as the release tracker lists.release/base-2.xis still at the tagged commit. No public StreamingFast repository pins this fork: a code search forv1.5.4-fh3.1only finds our deployment configuration.CHANGELOG
Test Execution Summary
Branch
bump/base-1.5.5:release/1.xatv1.5.4-fh3.1+git merge v1.5.5, built againststreamingfast/rethbase-v2.5.2.11-fh3.1(24849d77d) andstreamingfast/evmv0.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 asDockerfile.sf): PASSED (4 min on a clean target directory, after the dependencies were fetched)cargo check --workspace --all-targets: PASSED, afterforge soldeer install && forge buildincrates/utilities/test-utils/contracts(without the compiled contracts,base-test-utilsfails on the missingcontracts/out/*.json)cargo clippy -p base-reth-node -p base-builder-multiplex -p base-execution-payload-builder --tests: PASSED. The warnings are incrates/firehose-flashblocks/src/processor.rs,crates/execution/firehoseandcrates/execution/flashblocks/src/traits.rs, which this merge does not change (same set as thev1.5.4-fh3.1bump).rustfmt --checkpasses on the resolvedbuilder.rs.Unit Tests
cargo test -p base-firehose-testscargo test -p base-firehose-flashblockscargo test -p base-reth-nodecargo test -p base-execution-firehosecargo test -p base-execution-chainspeccargo test -p base-common-genesiscargo test -p base-common-chainscargo test -p base-execution-payload-builderbuilder.rscargo test -p base-reth-clicargo test -p base-builder-multiplexpayload_readytests andin_process_smoke, which failed on thev1.5.4bump and passes nowcargo test -p base-node-runnerBaseNode::provider_factory_builderdoctest (crates/execution/runner/src/node.rs) does not compile: it setsReadOnlyConfig { watch_static_files }, a field that neither upstreambase/rethbase-v2.5.2.11nor our reth fork has (it iswatch). The doc example is the same in upstreamv1.5.4andv1.5.5, so it is broken upstreamcargo test -p reth-firehose -p reth-firehose-tests(instreamingfast/rethat24849d77d,base-v2.5.2.11-fh3.1)cargo test -p reth-engine-tree --test firehose_live_tracing --test firehose_live_tracing_bal(same checkout)Integration Tests
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 (afterforge soldeer install && forge buildincrates/utilities/test-utils/contracts):firehose_b20::b20_transfer_is_tracedfirehose_cobalt_b20::cobalt_b20_surfaces_are_tracedfirehose_denim::denim_activation_block_traces_base_time_installBattlefield Tests
streamingfast/battlefield-ethereumatadb1921(master),base-devnettarget, with this branch's releasebase-reth-nodeandbase-consensusas the Firehose node and the upstreamghcr.io/base/node:v1.5.5image as the sequencer:Header corresponds to RPCandCompare blocks: Firehose blocks match RPC blockspassed. No snapshot changed, and the node log has noERRORand no panic (about 900 blocks). The reader node reportedFIRE INIT 3.1 reth base-1.5.5.base-firehose-tests.Firehose bug patterns
BuiltBlock::tracefor blocks built from payload attributes alone is kept. None found.v1.5.4, and usually fewer. None found.v1.5.5changes nothing incrates/common/chainsorcrates/utilities/upgrade-signal, and defines no newBaseUpgrade. Denim is active on Base mainnet and Sepolia. Everest is still not scheduled: there is no timestamp in the code, andgetSchedule()on the configured L1protocol_versions_addressstill reverts on both L1s (checked 2026-11-13). Zenith is genesis-only.ACTIVATIONS.mdrefreshed.crates/commonthat feed the block, and no change to the reth mapper. The newPayloadReadytype is an engine notification and does not reach the block. None found.