op-node v1.13.7

Note

This is a required release for the arena-z-sepolia chain. It is optional otherwise.

🤝 The corresponding op-geth release is v1.101602.3.

What's Changed

• op-node: remove elSyncEnabled as it is a noop by @nonsense in #17425
• refactor: introduce IsFeature toggles for Jovian by @geoknee in #17424
• go: bump op-geth dependency to update SR for addresses cleanup by @serpixel in #17404
• chore: update SystemConfig doc for minimum base fee by @wlawt in #17481
• feat: add tests for min-base-fee by @wlawt in #17441
• chore: bump op-geth to include new superchain registry configuration of arena-z-sepolia isthmus hardfork by @jelias2 in #17437
• op-node: Skip L1 genesis hash check if block is not available from the L1 by @ajsutton in #17407
• min-base-fee: bring in op-geth code by @geoknee in #17307
• feat: bump op-geth by @jelias2 in #17323
• op-node: fix comment for l1.cache-size by @zhiqiangxu in #17107

New Contributors

• @devin-ai-integration[bot] made their first contribution in #17415
• @wlawt made their first contribution in #17330

Full Changelog: op-node/v1.13.6...op-node/v1.13.7

🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.13.7

op-conductor/v0.7.3

What's Changed

• op-conductor: p2p healthcheck fix and execution_p2p_healthcheck_api_type by @yashvardhan-kukreja in #17294

Full Changelog: op-conductor/v0.7.2...op-conductor/v0.7.3

op-up/v0.2.0-rc.2

Changelog

• 21d638b op-up: encode version information in binary (#17405)

op-up/v0.2.0-rc.1

Changelog

• e4c34ec op-up: add ascii art (#17205)
• 2951d4d op-up: add survey link (#17206)
• 691d92f op-up: add unit test (#17210)
• 5a4374c op-up: basic cli argument handling (#17208)
• aa4db40 op-up: upgrade default version in install script (#17078)

op-up/v0.2.0

This release includes some cosmetic improvements, including proper cli argument handling and ascii art upon startup.

op-node/v1.13.6

Note

This is a recommended release for all node operators, as the geth base of op-geth is updated from 1.15.11 to 1.16.2, containing many upstream bug fixes and performance improvements. It is required to update op-geth and op-node together.

This release adds the ability to configure the maximum age of p2p messages (the default remains at 60 seconds) and includes several bug fixes.

🤝 The corresponding op-geth release is v1.101602.0.

What's Changed

• feat[op-node]: p2p flag to configure maximum age of payload by @brg8 in #16718
• fix: add json keys to outputV0 type by @itschaindev in #16538
• op-service/eth: fix exec payload creation from block by @sebastianst in #17154
• op-service/event: trace and log emitting of events by @nonsense in #16793
• op-chain-ops: Reorder interop fork by @mslipper in #16792

New Contributors

• @brg8 made their first contribution in #16718
• @itschaindev made their first contribution in #16538

🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.13.6

op-batcher v1.15.0

Important

All chain operators are strongly encouraged to upgrade their batchers to improve throttling behavior and mitigate worst-case spam attack scenarios.

Overview

This release includes a major reworking of the batcher-sequencer DA throttling feature (allowing for smoother control of transaction and block size limits), a new admin RPC method to flush the batcher (causing it to submit a transaction as soon as possible) as well as several performance enhancements and bugfixes.

Sequencer throttling changes

Warning

This release changes the default throttling behavior. Chain operators should examine the new throttling documentation closely to ensure their batchers are configured appropriately for their chain. We deem the new defaults well suited for average OP Stack chains that use the default block gas limits and EIP1559 elasticity. Especially if you operate a high-throughput chain, you may want to change the throttling parameters, like the block-size-upper-limit and block-size-lower-limit.

The old batcher supported only a very simple form of throttling: once a threshold of DA backlog was reached, it would fully throttle the sequencer and other block builders. This would often lead to a clunky user experience, as throttling kicks in fully at once, and then eases fully once the backlog dips below the threshold.

This release introduces three new throttling controllers to allow for more smooth throttling behavior than this step controller. The three new controllers are linear, quadratic, and a PID-like controller (experimental, not recommended). The new default throttling controller is quadratic.

Instead of throttling getting activated at a single threshold, like the old step controller, there is now a lower and upper threshold at which throttling starts and then continually increases in intensity as the backlog grows. The intensity curve is determined by the throttling controller (linear, quadratic, step (old behavior), PID (experimental)). Throttling at the lower threshold is weak and at the higher threshold strong. Please review the defaults by running ./op-batcher --help.

Another important change is that the throttling threshold now takes all pending data into account, that is, all channels that are currently being submitted, the pending open channel that is currently being built, and the pending blocks that still need to be added to the pending channel. Before, throttling only took into account the pending blocks, which means that it may have triggered much too late if a high --max-pending-tx value was set (default: 1), which is common among high-throughput chain operators.

Please read the new throttling documentation carefully to understand the new behavior and how to tweak it, if necessary.

What's Changed

• op-batcher: improve default throttle parameters by @sebastianst in #17148
• op-batcher: overhaul throttling flags by @geoknee in #17032
• op-batcher: set throttling defaults by @geoknee in #16957
• fix(op-batcher): introduce unsafe_da_bytes metric for driving the throttling controller by @geoknee in #16950
• op-batcher: decrement pending bytes metrics when pruning pending blocks by @geoknee in #16940
• feat(op-batcher): add admin rpc to flush the batcher by @geoknee in #16837
• op-batcher: more consistent use of throttle multiplier and max threshold in logging by @geoknee in #16820
• feat(op-batcher): make max throttle threshold more visible in logs and API by @geoknee in #16804
• op-batcher: always use blobs while throttling by @joshklop in #16773
• feat(op-batcher): Enhanced DA Throttling with multiple control mechanisms by @tobidae-cb in #16588
• perf(op-batcher): start publishing and throttling sooner when loading a backlog of blocks by @geoknee in #16648
• perf(op-batcher): discard channel compressor after frames generated by @geoknee in #16597
• fix(op-batcher): remove duplicate check by @chuwt in #16696

New Contributors

• @tobidae-cb made their first contribution in #16588
• @chuwt made their first contribution in #16696

Full Changelog: op-batcher/v1.14.0...op-batcher/v1.15.0

🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-batcher:v1.15.0

op-deployer/v0.2.6

Changelog

• aefa90d Update op-deployer with op-contracts/v2.2.0 release (#17099)

op-up/v0.1.1-rc.10

Changelog

• 410351d op-up: emphasize adding the command to PATH (#17075)

op-up/v0.1.1

Changelog

• c42ceba op-devstack: run rust services as sub-processes in sysgo (#16726)