op-node v0.3.0 and op-geth v0.3.0 released #170
owen-reorg
announced in
Announcements
Replies: 1 comment
-
We deleted it because:
If you are using it, upgrade |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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
--pprof.port
).--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
Docker Images
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
--triesInMemory
is deleted.--db.engine=leveldb
if prefer leveldb)--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
Docker Images
Full Changelog
bnb-chain/op-geth@v0.2.2...v0.3.0
Beta Was this translation helpful? Give feedback.
All reactions