Nethermind 2.2.0 adds a dedicated Aztec config

Nethermind released version 2.2.0. It adds a mainnet config made for Aztec: mainnet_aztec. It keeps the L1 history and the transaction traces that the Aztec node needs.

What to do

- Node that works with Aztec today (with or without the guide settings): upgrade in place, with no resync. Keep your current config. A move to mainnet_aztec starts a full resync.
From 2.1: no config change.
From 1.39: read the 2.0.0 and 2.1.0 breaking changes first. Some removed settings stop the node at startup.
- If JsonRpc.Host or JsonRpc.EngineHost is a host name (for example a Docker service name), read the Nethermind breaking changes first: JSON-RPC now binds only to the address of that name.
- New node or planned resync: you can use --config mainnet_aztec. It uses its own database folder, so it starts a full sync. Keep a second L1 endpoint for the Aztec node during that time.
- mainnet_aztec listens on 127.0.0.1 only. If your Aztec node runs in another container, set --JsonRpc.Host to an address that it can reach.