v0.5.1

v0.5.1

This is a minor release and upgrading is optional.

What's Changed

• fix(ci): support building arm64 architecture by @welkin22 in #239
• fix(op-node): l1 client chan stuck when closed in ELSync mode by @welkin22 in #241
• fix: add sync status when newpayload API meet the specific error by @krish-nr in #240

Docker Images

• ghcr.io/bnb-chain/op-node:v0.5.1
• ghcr.io/bnb-chain/op-batcher:v0.5.1
• ghcr.io/bnb-chain/op-proposer:v0.5.1

Full Changelog: v0.5.0...v0.5.1

v0.5.0

v0.5.0

This release includes code merging from the upstream version v1.7.7 along with several fixs and improvements.

Fjord fork from upstream is included. It is set to be activated on both the opBNB Mainnet and Testnet environments according to the following schedule:

• Testnet: Sep-10-2024 06:00 AM +UTC
• Mainnet: Sep-24-2024 06:00 AM +UTC

All mainnet and testnet nodes must upgrade to this release before the hardfork time.
Also note that the op-geth should be upgraded to v0.5.0 accordingly, check this for more details.

User Facing Changes

• The L1 fee calculation is optimized. Check this spec for more details.
• New flag --wait-node-sync added to op-batcher (default false), indicates if during startup, the batcher should wait for a recent batcher tx on L1 to finalize (via more block confirmations). This should help avoid duplicate batcher txs
• New flag --wait-node-sync added to op-proposer (default false), indicates if during startup, the proposer should wait for the rollup node to sync to the current L1 tip before proceeding with its driver loop
• New flag --compression-algo added to op-batcher (default zlib), user can choose brotli algo after Fjord fork
• New flag --l1.rpc-max-cache-size added to op-node (default 1000), so user can config the the maximum cache size of the L1 client

What's Changed

• Merge upstream v1.7.7 by @bnoieh in #216
• feat(op-node): Keep consistent status when meet an unexpected el sync by @krish-nr in #222
• feat(op-node): add l1 cache size config by @welkin22 in #225
• feat(op-chain-ops): add Wright fork config into genesis file generation code by @welkin22 in #226

Docker Images

• ghcr.io/bnb-chain/op-node:v0.5.0
• ghcr.io/bnb-chain/op-batcher:v0.5.0
• ghcr.io/bnb-chain/op-proposer:v0.5.0

Full Changelog: v0.4.4...v0.5.0

v0.4.4

v0.4.4

This release includes important fixes to help pbss geth nodes automatically recover from ungraceful shutdowns.
We recommend upgrading to this version if you are using the pbss mode.

What's Changed

• fix(devnet): Modify the blob configuration of the bsc devnet by @welkin22 in #212
• feat: auto recover from pbss geth unclean shutdown by @krish-nr in #214
• fix: fix el bug by @krish-nr in #215

Docker Images

• ghcr.io/bnb-chain/op-node:v0.4.4

Full Changelog: v0.4.3...v0.4.4

v0.4.3

This is a minor release and upgrading is optional.

User Facing Changes

• Support choose economic DA type automatically for op-batcher. #209
• Add 2 configs for el-sync optimization and enable fastnode mode again. #201

What's Changed

• feature: add haber fork config in deployment script by @redhdx in #202
• feat(op-node): support multi clients to fetch blobs by @bnoieh in #199
• feat: fastnode support by trigger el-sync when needed by @krish-nr in #201
• fix(blob-client): don't append L1ArchiveBlobRpcAddr flag to config if not set by @bnoieh in #207
• fix(devnet): fork offset should be 0x by @welkin22 in #210
• fix(devnet): batcher uses its address to submit transactions by @welkin22 in #211
• feat: op-batcher auto switch to economic DA type by @bnoieh in #209

Docker Images

• ghcr.io/bnb-chain/op-node:v0.4.3
• ghcr.io/bnb-chain/op-batcher:v0.4.3
• ghcr.io/bnb-chain/op-proposer:v0.4.3

Full Changelog: v0.4.2...v0.4.3

v0.4.2

This is the mainnet hardfork release version.

Four hard forks are scheduled to launch on the opBNB Mainnet:
Shanghai/Canyon Time: 2024-06-20 08:00:00 AM UTC
Delta Time: 2024-06-20 08:10:00 AM UTC
Cancun/Ecotone Time: 2024-06-20 08:20:00 AM UTC
Haber Time: 2024-06-20 08:30:00 AM UTC

All mainnet op-node have to be upgraded to this version before 2024-06-20 08:00:00 AM UTC.
The op-geth also have to be upgraded to v0.4.2 accordingly, check this for more details.

User Facing Changes

If you are upgrading from v0.3.x to this version, please note that there are some configuration changes.

• Removed --l1.rpckind=bsc_fullnode
• Removed --l2.engine-sync
• Removed --l2.skip-sync-start-check
• To start engine-sync, use --syncmode=execution-layer (default value is consensus-layer)
• Added --l1.max-concurrency=20 to control the rate of requests to L1 endpoints.

After the Cancun/Ecotone hard fork, DA data will be submitted to the BSC network in blob format. Regular BSC nodes only retain blob data from the past 18 days. If you are syncing data from the genesis block or are more than 18 days behind the latest block, you will need to ensure that your configured L1 endpoint supports persisting blob data for a longer period of time. We will ensure that the snapshot provided by this snapshot repository is within the 18-day range, so you can also choose to use the snapshot to avoid relying on older blob data to start your new node.

What's Changed

• feature: update deployment script for opBNB by @redhdx in #196
• fix: fix CI after 4844 merge by @welkin22 in #198
• op-node: set finalityDelay to 15 to speed up finality update by @bnoieh in #200
• config: Mainnet canyon/delta/ecotone fork time by @welkin22 in #203

Docker Images

• ghcr.io/bnb-chain/op-node:v0.4.2
• ghcr.io/bnb-chain/op-batcher:v0.4.2
• ghcr.io/bnb-chain/op-proposer:v0.4.2

Full Changelog: v0.4.1...v0.4.2

v0.4.1

v0.4.1

This is a minor release and upgrading is optional.

User Facing Changes

• Add flag --txmgr.blob-gas-price-limit for op-batcher to limit the maximum gas price of submitted tx

Partial Changelog

• fix: fix devnet after 1.7.2 upstream merge by @welkin22 in #194
• op-batcher: optimize tx submitting and add metrics by @bnoieh in #195

Docker Images

• ghcr.io/bnb-chain/op-batcher:v0.4.1

Full Changelog: v0.4.0...v0.4.1

v0.4.0

This release includes code merging from the upstream version v1.7.2 to transition Testnet's DA data from calldata to blob format.

Four hard forks are scheduled to launch on the opBNB Testnet:
Snow Time: May-15-2024 06:00 AM +UTC
Shanghai/Canyon Time: May-15-2024 06:10 AM +UTC
Delta Time: May-15-2024 06:20 AM +UTC
Cancun/Ecotone Time: May-15-2024 06:30 AM +UTC

User Facing Changes

Nodes on the Testnet need to be upgraded to this version before the first hard fork time.
Note: This is a version prepared for Testnet, Mainnet nodes do not need to upgrade to this version.

Note: After the Cancun/Ecotone hard fork, DA data will be submitted to the BSC network in blob format. Regular BSC nodes only retain blob data from the past 18 days. If you are syncing data from the genesis block or are more than 18 days behind the latest block, you will need to ensure that your configured L1 endpoint supports persisting blob data for a longer period of time. We will ensure that the Testnet snapshot provided by this snapshot repository is within the 18-day range, so you can also choose to use the snapshot to avoid relying on older blob data to start your new node.

Changes in op-node configuration:

• Removed --l1.rpckind=bsc_fullnode
• Removed --l2.engine-sync
• Removed --l2.skip-sync-start-check
• To start engine-sync, use --syncmode=execution-layer (default value is consensus-layer)
• Added --l1.max-concurrency=20 to control the rate of requests to L1 endpoints.

What's Changed

• feature(op-node): update opBNB qanet info by @redhdx in #187
• feat: update qanet config by @redhdx in #188
• feature(op-node): add opBNB qanet hard fork config by @redhdx in #189
• Fix blob parsing problem by @welkin22 in #190
• chore: fork config for 4844-2 qanet by @welkin22 in #191
• Merge upstream v1.7.2 by @bnoieh in #184
• config: Testnet 4844 fork time by @welkin22 in #192

Docker Images

ghcr.io/bnb-chain/op-node:v0.4.0
ghcr.io/bnb-chain/op-batcher:v0.4.0
ghcr.io/bnb-chain/op-proposer:v0.4.0

Full Changelog: v0.3.3...v0.4.0

v0.4.0-alpha

This pre-release includes code merging from the upstream version v1.7.2 to transition Testnet's DA data from calldata to blob format.
Four hard forks are scheduled to launch on the opBNB Testnet:
Snow Time: May-15-2024 06:00 AM +UTC
Shanghai/Canyon Time: May-15-2024 06:10 AM +UTC
Delta Time: May-15-2024 06:20 AM +UTC
Cancun/Ecotone Time: May-15-2024 06:30 AM +UTC

User Facing Changes

Nodes on the Testnet need to be upgraded to this version before the first hard fork time.
Changes in op-node configuration:

• Removed --l1.rpckind=bsc_fullnode
• Removed --l2.engine-sync
• Removed --l2.skip-sync-start-check
• To start engine-sync, use --syncmode=execution-layer (default value is consensus-layer)
• Added --l1.max-concurrency=10 to control the rate of requests to L1 endpoints.

What's Changed

• feature(op-node): update opBNB qanet info by @redhdx in #187
• feat: update qanet config by @redhdx in #188
• feature(op-node): add opBNB qanet hard fork config by @redhdx in #189
• Fix blob parsing problem by @welkin22 in #190
• chore: fork config for 4844-2 qanet by @welkin22 in #191
• Merge upstream v1.7.2 by @bnoieh in #184
• config: Testnet 4844 fork time by @welkin22 in #192

Docker Images

ghcr.io/bnb-chain/op-node:v0.4.0-alpha
ghcr.io/bnb-chain/op-batcher:v0.4.0-alpha
ghcr.io/bnb-chain/op-proposer:v0.4.0-alpha

Full Changelog: v0.3.3...v0.4.0-alpha

v0.3.3

This is a minor release and upgrading is optional.

User Facing Changes

To simplify the process of starting op-node for users, default configurations for opBNB mainnet and testnet have been added. Users can now select the network configuration by setting --network=opBNBMainnet or --network=opBNBTestnet. Check details in PR #179.

Partial Changelog

• #179: feature(op-node): simplify op-node start

Docker Images

• ghcr.io/bnb-chain/op-node:v0.3.3

Full Changelog

v0.3.2...v0.3.

v0.3.2

This is a hardfork release for the opBNB Mainnet called Snow. It will be activated at April 15, 2024, at 6 AM UTC.
All op-node of mainnet nodes must upgrade to this release before the hardfork.

If you are on v0.3.1, you need to upgrade to v0.3.2 by April 9, 2024, at 6 AM UTC.

User Facing Changes

• The L1 gas price of all L2 transactions will be optimized after the snow hardfork. The price will be calculated based on the median of the last 21 blocks' gas prices on BSC. The L1 gas price for the opBNB Mainnet is expected to be decreased to 1 Gwei after the hardfork. And it will adjust automatically if the gas price on BSC changes.

Partial Changelog

• #169: feat: optimize l1 gas price calculation after snow hardfork

Docker Images

• ghcr.io/bnb-chain/op-node:v0.3.2

Full Changelog

v0.3.0...v0.3.2