[flisko]

Merge this only after #112 is merged and its Release avado-dnp-nethermind.public.dappnode.eth 0.0.73 commit is on main. Then rebase this branch on main and push, so CI builds a fresh release patch (otherwise the release job fails with "patch does not apply"). That is why this PR is a draft.

Nethermind 2.1.0 (2026-10-01, release notes) lists no security fixes. It brings a faster EVM, lower engine_newPayload latency, dual-stack IPv4/IPv6 P2P by default, safety rails for the flat state backend (a flat DB that RocksDB repaired is re-synced; --FlatDb.Enabled=false on an existing flat DB is now refused instead of silently resyncing), RocksDB 11, and Merge.CompactMemory now defaults to No (steady-state RAM may be somewhat higher). The only Gnosis-specific item is an AuRa fix in BAL preprocessing (#13047). The breaking changes don't stop this package: start.sh already leaves out --FlatDb.Enabled=false when a flat folder exists, Gnosis keeps SnapSync: true in Nethermind's gnosis config, and none of the removed config keys are set. DAppNode released Nethermind 2.1.0 for their Gnosis package (nethermind-generic gnosis v1.0.82, 2026-10-05).

Package nethermind-gnosis.avado.dnp.dappnode.eth 0.0.59 → 0.0.60, Nethermind 2.0.0 → 2.1.0.

Changes (same flow as #109 / #110)

• build/dappnode_package-gnosis.json, build/docker-compose-gnosis.yml: version 0.0.60, upstream / VERSION 2.1.0.
• ./setNetwork.sh gnosis: the root dappnode_package.json, docker-compose.yml and avatar.png point to the gnosis files. main goes back to mainnet in a follow-up PR after the release commit (branched from main after Release nethermind-gnosis… 0.0.60). That follow-up re-publishes avado-dnp-nethermind 0.0.73 to staging at the same version, which boxes ignore.
• This branch is stacked on Release avado-dnp-nethermind.public.dappnode.eth 0.0.73: Nethermind 2.1.0 #112, so Gnosis also gets --Network.LocalIp=0.0.0.0 (2.1.0 would otherwise bind P2P to [::]). After Release avado-dnp-nethermind.public.dappnode.eth 0.0.73: Nethermind 2.1.0 #112 merges, only the gnosis commit is left in this PR's diff.
• While main is on Gnosis, the update bot skips (guard from Gnosis: nethermind-gnosis 0.0.59 on Nethermind 2.0.0 (maintenance release) #109).

Tested locally (Docker, linux/amd64 emulated on Apple silicon)

• docker build --platform linux/amd64 of build/ with VERSION=2.1.0 succeeds; the binary reports 2.1.0+b3e7e84c (.NET 10.0.12). Image about 532 MB.
• Started start.sh with the manifest env (NETWORK=gnosis, EXTRA_OPTS=--Sync.FastSync=true --Network.MaxActivePeers=50) on a fresh database: Chain ID: Gnosis, State backend: patricia (flat DB disabled)., Using the local IP override: NetworkConfig.LocalIp = 0.0.0.0, port 30305, no exceptions, no unrecognized options, state sync started. The full command line includes --FlatDb.Enabled=false --Network.LocalIp=0.0.0.0.
• Not tested: an update on an existing synced Gnosis database and a run at the head with teku-gnosis. Do that on the test box with the image CI builds before promoting (the synced database from the 0.0.59 tests, gnotest_nm_db, may still be on the box).

Merge with a merge commit, not a squash.

🤖 Generated with Claude Code