v1.1.0-fh

Caveats

This new release generates a difference in system calls' gas limit:

  -      "gasLimit": "30000000",
  +      "gasLimit": "31566720",

this is due to how reth upstream changed that limit to that new value, which we reflect in our tracing.

Changes

• Bumped base to v1.1.0
• Bumped streamingfast/reth dependencies to tag = "v2.3.0-fh" (reth v2.3.0, revm 40, alloy-evm 0.36)
• Patched alloy-evm to the StreamingFast fork (streamingfast/evm branch sf/v0.36.0), which routes EVM system calls (EIP-4788, EIP-2935, etc.) through the Inspector so Firehose traces them — fixes the missing EIP-4788 beacon-roots pre-execution system call
• Added Beryl hardfork activation timestamps (Sepolia: 1_781_805_600, Zeronet: 1_780_678_800)
• Added Cobalt hardfork plumbing
• Added /app/base-consensus to docker build

v1.0.0-fh

• Bumped to base 1.0.0

Note

When bumping from 0.9.x, you will need to delete the content of data/exex/wal before starting this version,
because the storage format of the ExEx Write-Ahead-Log has changed in reth 2.2.0.
It will recover quickly.
Example error: called `Result::unwrap()` on an `Err` value: failed to decode notification 1389790 from /var/lib/reth/exex/wal/1389790.wal: wrong msgpack marker FixArray(2)

v0.9.1-fh-1

• Fixed flash blocks to arrive in the right order and be 100% identical to the canonical blocks

v0.9.0-fh

Changes

• Update workspace version to v0.8.0.
• Update all streamingfast/reth dependencies from branch = "release/reth-1.x" to tag = "v1.11.4-fh-1".

v0.8.0-fh-1

Changes

• Update workspace version to v0.8.0.
• Update all streamingfast/reth dependencies from branch = "release/reth-1.x" to tag = "v1.11.4-fh-1".

v0.7.6-fh

Operator Notes

This is the initial integration of the Firehose instrumentation into base-reth, enabling Firehose 3.0 block production from a Reth-based Base node.

Due to the block model changes which we couldn't record in a backward compatible way, this release uses block version 5 of the Firehose Ethereum Block protobuf model.

Changes

• Initial integration of the Firehose instrumentation to base-reth.

  Coming from op-geth instrumentation, this release brings a new Ethereum Block version (ver = 5 in the Firehose Ethereum Block protobuf model) that has the following semantic changes versus version 4:

  • GasChanges has been removed from the Call object and is not traced anymore, this was announced in January and is now effective in block version 5.
  • Bug fix where some CodeChange were emitted without a real code change (e.g. that CodeChange.prev == CodeChange.new), those are not emitted in block version 5.
  • Self destructs tracing is now handled drastically differently than in block version 4 fixing some bugs along the way.
    • While in block version 4 all self-destruct related changes (CodeChange, BalanceChange, etc) were all done at time of SELFDESTRUCT opcode, this is not true anymore in block version 5 where some changes are now deferred to when the transaction is finalized. This fixes some inconsistencies that could happened, for instances some self-destructs did not properly emit 'nonce changes' to 0, they now do.
  • State change hooks no longer record entries when old and new values are identical (no-op state changes are dropped).
  • System Calls may be emitted in a different order (the same final state is produced regardless of the order of those calls)

  Outside of GasChanges, there is no major differences in the actual output more around in which order some of the changes are emitted so everyone should be able to accept version 5 like if this was version 4.