Skip to content

Releases: flashbots/rollup-boost

rollup-boost/v0.7.10

18 Nov 16:36
501ae74

Choose a tag to compare

Summary

Recommended Jovian ready release. Reth dependency bump to 1.9.3 which updates the calculation of the payload id in rollup-boost for the Jovian fork.

What's Changed

Full Changelog: rollup-boost/v0.7.9...rollup-boost/v0.7.10

rollup-boost/v0.7.9

18 Nov 16:33
6dbc3a2

Choose a tag to compare

rollup-boost/v0.7.9 Pre-release
Pre-release

Summary

Reth dependency bump to 1.9.2.

What's Changed

Full Changelog: rollup-boost/v0.7.8...rollup-boost/v0.7.9

rollup-boost/v0.7.8

18 Nov 16:32
1b66d7d

Choose a tag to compare

rollup-boost/v0.7.8 Pre-release
Pre-release

Summary

Dependency bump for reth to 1.9.1

What's Changed

Full Changelog: rollup-boost/v0.7.7...rollup-boost/v0.7.8

rollup-boost/v0.7.7

06 Nov 18:28
0e4f60b

Choose a tag to compare

Summary

  • Includes breaking changes in the websocket reconnect cli params, please see below for details on the cli changes.
  • Also introduces a separation between the rollup-boost binary and library components, allowing rollup-boost to be imported into a rust workspace as a standalone service.
  • Bug fixes in the health check when the l2 execution client is unhealthy but the builder is healthy

CLI Changes

  • --flashblock-builder-ws-reconnect-ms was changed, now it consists of 2 params:
    • --flashblock-builder-ws-initial-reconnect-ms and --flashblock-builder-ws-max-reconnect-ms that are used in exponential back off with a 1.5 multiplier (timeout increased by 50% every unsuccessful re connections and reset on successful connection)
      New CLI Params:
  • --flashblock-builder-ws-ping-interval-ms - how often rollup-boost send pings to the builder websocket
  • --flashblock-builder-ws-pong-timeout-ms - timeout for pong. We close the connection if we haven't received a pong for ping that we send after the timeout

We send proper data (uuid v7) in pings and expect correct pongs with the uuid.

What's Changed

New Contributors

Full Changelog: rollup-boost/v0.7.6...rollup-boost/v0.7.7

rollup-boost/v0.7.6

04 Oct 12:55
33f276a

Choose a tag to compare

rollup-boost/v0.7.6 Pre-release
Pre-release

Warning

This version have known issue with op-batcher, that causes batcher stall when op-geth is down, we are working on a fix

Release Notes

Added support for websocket connections between op-node and rollup-boost.
Improved reliability of health checks with external_state_root enabled.

What's Changed

  • fix: improve builder health updates in get_payload by distinguishing L2 vs. builder failures by @cody-wang-cb in #411
  • Fix docs, specify correct flashblock-rpc repo by @SozinM in #418
  • Websocket support by @SozinM in #410

Full Changelog: rollup-boost/v0.7.5...rollup-boost/v0.7.6

websocket-proxy/v0.0.2

29 Sep 17:12
b86af43

Choose a tag to compare

Release Notes

  • Allows rate limits per API key for the --api-keys flag in the form <app1>:<apiKey1>:<rateLimit1>,<app2>:<apiKey2>:<rateLimit2>,... Rate limits must be specified
  • --per-ip-connection-limit is no limit if set to 0

What's Changed

Docker Image: flashbots/flashblocks-websocket-proxy:v0.0.2
Full Changelog: websocket-proxy/v0.0.1...websocket-proxy/v0.0.2

rollup-boost/v0.7.5

29 Sep 15:15
b86af43

Choose a tag to compare

Release Notes:

  • Rollup-Boost now sends engine_getPayload for every block even when flashblocks are enabled in this PR. The result from the call is not used by rollup-boost but is needed to cancel the builder's block building job so the flashblocks gets saved into the builder cache. Previously it would only get the builder payload when constructing the block from the websocket stream fails. Rollup-boost ignores it result, and this acts as builder jobs cancellation.
  • New flag --external-state-root that allows rollup-boost to delegate the local execution client to calculate the state root
  • New flag --ignore-unhealthy-builders that does not allow engine API calls to go through when health checks fail
  • Added rollup_boost_execution_mode metric to inspect rollup-boost execution mode

What's Changed

New Contributors

Full Changelog: v0.7.4...rollup-boost/v0.7.5

v0.7.4

22 Jul 07:49
03ea8f8

Choose a tag to compare

What's Changed

Breaking changes

Renamed flashblocks metrics.
flashblocks_used was depricated
flashblocks_gauge, flashblocks_counter, flashblocks_missing_histogram, flashblocks_missing_gauge, and flashblocks_missing_counter were added

Full Changelog: v0.7.3...v0.7.4

v0.7.3

11 Jul 17:53
64be33f

Choose a tag to compare

What's Changed

  • E2E tests for flashblocks RPC by @ferranbt in #365
  • chore: simplify rollup-boost args by @0xKitsune in #358
  • chore: minor cleanup flashblocks logic by @0xKitsune in #357
  • Use arcswap to speed things up by @SozinM in #371
  • Skip "Payload ID mismatch" error if rollup-boost is inactive (not serving FCU with attributes) by @SozinM in #375

Breaking changes

Execution mode now controlled via debug interface only.
Removed the --flashblocks boolean flag. Instead, Flashblocks configuration is now optional via Option. Flashblocks is enabled if any related --flashblocks-* flags are specified.

Full Changelog: v0.7.2...v0.7.3

v0.7.2

08 Jul 05:53
33f55e8

Choose a tag to compare

Release Notes

  • Metrics for flashblocks
  • Adds Flashblocks RPC overlay

What's Changed

New Contributors

Full Changelog: v0.7.1...v0.7.2