op-node v0.3.0 and op-geth v0.3.0 released

[owen-reorg]

op-node v0.3.0

https://github.com/bnb-chain/opbnb/releases/tag/v0.3.0

This is a recommended release for op-node. This release brings in upstream updates, see #121 for the contents. This is also a ready release for the next planed fork, which will bring in canyon fork from upstream as well.

User Facing Changes

• The default address for the metrics, rpc, and pprof servers will be changing from 0.0.0.0 to 127.0.0.1, and pprof server will change to use 6060 port by default(you may encounter panic due to port conflict, if so you could change it to another value via --pprof.port).
• op-node enable p2p score feature, and with --p2p.scoring=light, --p2p.ban.peers=true by default(to keep previous config, you could set --p2p.scoring=none, --p2p.ban.peers=false).

Partial Changelog

• fix(op-node): pre-fetching handle L1 reOrg #115: fix(op-node): pre-fetching handle L1 reOrg
• fix(op-node): pre-fetching handle L1 reOrg round 2 #117: fix(op-node): pre-fetching handle L1 reOrg round 2
• fix(op-node/op-batcher/op-proposer): the fallback client should always try recover #118: fix(op-node/op-batcher/op-proposer): the fallback client should always try recover
• Merge upstream v1.3.0 #121: Merge upstream v1.3.0
• fix(op-node): fix basefee when start new chain with fermat #127: fix(op-node): fix basefee when start new chain with fermat

Docker Images

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

Full Changelog

v0.2.4...v0.3.0

op-geth v0.3.0

https://github.com/bnb-chain/op-geth/releases/tag/v0.3.0

This is a recommended release for op-geth. This release brings in upstream updates, see bnb-chain/op-geth#58 for the contents. This is also a ready release for the next planed fork, which will bring in canyon fork from upstream as well.

User Facing Changes

• Feature of config tries layer number in memory is removed, and related flag --triesInMemory is deleted.
• If start a fresh node, will use pebble db as default(set --db.engine=leveldb if prefer leveldb)
• You can start opbnb mainnet or testnet without init genesis.json, and use flag --opBNBMainnet or --opBNBTestnet to start new node. If you have already inited genesis.json, you can still use these two flags, which will check whether the content of your init is correct.

Partial Changelog

• #64: fix(op-geth):fix static peer cannot reassign header tasks
• #60: feature: add opbnb networks' genesis
• #58: Merge upstream op-geth v1.101304.1
• #51: feat: sync pebble db from bsc
• #50: fix: fix task stuck and not reassign bug in concurrent-fetch logic
• #49: fix: ignore errors that caused by gap to keep peer connection
• #46: fix: prune uses the latest block height as the target by default

Docker Images

• ghcr.io/bnb-chain/op-geth:v0.3.0

Full Changelog

bnb-chain/op-geth@v0.2.2...v0.3.0

[owen-reorg]

Why is --triesInMemory flag deleted? What if we are currently using it?

We deleted it because:

1. Customized triesInMemory conflicted with upstream code.
2. Deleting this flag had minimal impact on performance in our tests.

If you are using it, upgrade op-geth to v0.3.0 and remove the flag.