Skip to content

firehose: emit genesis block on empty-chain start - #4

Closed
sduchesneau wants to merge 1 commit into
firehose/v2.4.2from
fix/firehose-genesis-block
Closed

firehose: emit genesis block on empty-chain start#4
sduchesneau wants to merge 1 commit into
firehose/v2.4.2from
fix/firehose-genesis-block

Conversation

@sduchesneau

Copy link
Copy Markdown

Companion to streamingfast/reth#25 and streamingfast/optimism#13: bumps reth-firehose to op-rs-aef8d3e-fh-1, points reth-optimism-firehose at the genesis-emitting optimism branch (fix/firehose-genesis-block-wc — retarget to release/world-chain-2.4.x once optimism#13 merges), and wires emit_genesis_block_if_empty from on_node_started in both launch paths.

Verified end-to-end with the battlefield world-chain devnet: follower streams from block 0 (--common-first-streamable-block=0), genesis carries the full alloc, and the full suite passes — 79 passing, 6 pending, 0 failing.

🤖 Generated with Claude Code

Bump reth-firehose to op-rs-aef8d3e-fh-1 and reth-optimism-firehose to
the genesis-emitting branch, and wire emit_genesis_block_if_empty from
on_node_started in both launch paths (genesis only exists in the DB
after launch init). Blocks now stream from 0 with the full genesis
alloc; block 1 goes through the normal tracing path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@sduchesneau
sduchesneau deleted the branch firehose/v2.4.2 August 20, 2026 18:37
@sduchesneau
sduchesneau deleted the fix/firehose-genesis-block branch August 20, 2026 19:11
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.

2 participants