Bump Base to v1.5.1

ACTIVATIONS.md

@@ -7,15 +7,15 @@ and refresh the statuses when an activation is announced.
 Denim and Everest are contract-backed: an L1 upgrade signal (`crates/utilities/upgrade-signal`) can
 schedule them on a network with no new node release. Zenith can only be set in genesis.
 
-Statuses checked 2026-10-16 against Base `v1.5.0` (`crates/common/chains/src/config.rs`).
+Statuses checked 2026-10-28 against Base `v1.5.1` (`crates/common/chains/src/config.rs`).
 
 | Upgrade | Base mainnet | Base Sepolia | Effect on the Firehose block |
 |---------|--------------|--------------|------------------------------|
 | Bedrock … Jovian | Active (Jovian 2025-12-02) | Active | Already in the stream. Canyon's `create2deployer` install is a direct DB write in `apply_pre_execution_changes`; it is emitted as a block-level code change when the block is traced with `v1.5.0-fh3.1` or later. |
 | Azul | Active 2026-05-28 18:00 UTC | Active 2026-04-20 18:00 UTC | Already in the stream. |
 | Beryl | Active 2026-06-25 18:00 UTC | Active 2026-06-18 18:00 UTC | Already in the stream. |
 | Cobalt | Active 2026-09-30 18:00 UTC | Active 2026-09-23 18:00 UTC | B-20 V2 precompiles. Covered by `etc/systems/tests/firehose_cobalt_b20.rs`. |
-| Denim | Not scheduled | 2026-10-21 18:00 UTC (`1_792_605_600`) | See [Denim](#denim). |
+| Denim | Scheduled 2026-11-05 18:00 UTC (`1_793_901_600`) from `v1.5.1`; first Denim block is 53_556_127 at `1_793_901_601` | Active 2026-10-21 18:00 UTC (`1_792_605_600`) | See [Denim](#denim). **Mainnet nodes must run `v1.5.1-fh3.1` or later before activation.** |
 | Everest | Not scheduled | Not scheduled | See [Everest](#everest). Traced from `v1.5.0-fh3.1-2` as `TRX_TYPE_ACCOUNT_ABSTRACTION`. **Earlier versions stop on the first EIP-8130 transaction.** |
 | Zenith | Never (genesis only) | Never (genesis only) | Gates the EIP-8130 keystore (account configuration changes, non-k1 authenticators). Unreachable on real networks. Traced from `v1.5.0-fh3.1-2`: create and config change entries in `account_changes`, non-k1 sender authentication in `sender_auth`. |
 
@@ -39,6 +39,14 @@ Statuses checked 2026-10-16 against Base `v1.5.0` (`crates/common/chains/src/con
 - B-20 precompiles switch to V3 (new policy rules). Same storage and event paths as V2.
 - New post-execution checks (base time schedule) run before the Firehose block is printed on the
   live and pipeline paths.
+- The FIRE BLOCK line time, which becomes the Firehose block time, has millisecond precision from
+  the activation block on, computed from the chain's Denim schedule (`bin/node/src/firehose.rs`).
+  RPC adds `timestampMs` and `blockTimestampMs` to blocks, transactions, receipts and logs; they
+  carry the same value, which the Firehose block has only as its block time.
+- Flashblocks stop. From the activation timestamp the sequencer builds with the basic builder and
+  publishes no flashblocks (`crates/builder/multiplex/src/router.rs`), so a node started with
+  `--firehose-flashblocks-url` emits no partial blocks after the last pre-Denim block. Full blocks
+  are unaffected and come every 200 ms.
 
 ## Everest
 

CHANGELOG.sf.md

@@ -1,3 +1,14 @@
+## v1.5.1-fh3.1
+
+### Changed
+
+* Rebased on upstream Base `v1.5.1`. It schedules the Denim hardfork on Base mainnet at
+  2026-11-05 18:00:00 UTC, so mainnet operators must run this release before then.
+  `streamingfast/reth` stays on `base-v2.5.2.8-fh3.1-2` and `firehose-tracer` on 5.7.0; the
+  Firehose block model is unchanged.
+* From Denim on, Base publishes no flashblocks, so a node started with `--firehose-flashblocks-url`
+  emits no partial blocks after the activation; full blocks come every 200 ms instead.
+
 ## v1.5.0-fh3.1-2
 
 ### Added