Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: update v0.5.0 changelog #236

Merged
merged 1 commit into from
Aug 28, 2024
Merged

doc: update v0.5.0 changelog #236

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,19 @@

## 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 and will be activated on opBNB testnet in later release.
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](https://github.com/bnb-chain/op-geth/releases/tag/v0.5.0) for more details.

### User Facing Changes

* The L1 fee calculation is optimized. Check this [spec](https://specs.optimism.io/protocol/fjord/exec-engine.html) 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
Expand Down
Loading