v0.2.2

[owen-reorg]

This is the Fermat Hardfork release for opBNB Mainnet.
It will be activated at block height 9397477, expected to occur on November 28, 2023, at 6 AM UTC.

All mainnet nodes must upgrade to this release before the hardfork.

User Facing Changes

• Support reading private keys from AWS Secret Manager for op-node, op-batcher, and op-proposer. Refer to PR feat: support AWS key manager #72 for additional information.

Partial Changelog

• feat: support AWS key manager #72: feat: support AWS key manager

Docker Images

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

Full Changelog

v0.2.1...v0.2.2

---

This discussion was created from the release v0.2.2.

[m-e-m-f-i-s-19]

In case, node hasn't been upgraded to the specified version, what will happen? I did node upgrade after hardfork, should I start node setup from scratch?

[owen-reorg]

Your node will fork from the canonical chain and stop at the height after the fork number.
If you are familiar with the engine API, you can upgrade your node and then reset op-geth to the block before the fork height.
Otherwise, it is easier to start the node from scratch.
If you don't need historical data, you can enable the snap sync of op-geth, which will make starting from scratch much faster. Refer to this manual for more details.

[leotese]

Really nice, i think this will be a great chain!