Update komodod & KDF

[smk762]

Removes VOTE2024
Updates komodod to 0adeeab
Updates mm2 to latest release

[DeckerSU]

I think we should add a comment here that ./m_notary_main should be launched for mainnet nodes and ./m_notary_3rdparty for third-party nodes only. Operators should launch the corresponding file based on the node type, meaning they should not run both files in sequence on the same node.

[DeckerSU]

Also I guess we should include the following "HOW-TO" about error in HDD data. And it's especially important to emphasize to the NN operators that service disruptions are unacceptable. If you experience the error in HDD data error for any chain, you should sync from another node and then bootstrap without stopping the production node for an extended period. The bootstrap process should only take a few minutes, and this is the expected downtime.

HOW-TO

If your blockchain data folder contains data from an older daemon version (before we switched to the 0.7.x versioning, such as 3.x.x), you might encounter this error when starting the 0.9.0 daemon:

2024-08-21 18:49:12 ERROR: LoadBlockIndex() : failed to read value
2024-08-21 18:49:12 : Error loading block database.
error in HDD data, might just need to update to latest, if that doesn't work, then you need to resync.

In this case, you have several options:

1. Resync from scratch (slowest but most accurate, allowing your node to recalculate value pools).
2. Bootstrap from dexstats.info (fastest, but since the initial sync version is unknown, value pools might be incorrectly calculated). Value pools refer to the stats for transparent, sprout, sapling, and burned chain values.
3. Reindex with -reindex, but options (1) and (2) are recommended.

Future upgrades shouldn’t have these issues, but for now, we should recommend that users who encounter the error in HDD data error after updating resync their nodes. This error seems to affect "veteran nodes" with data written by older daemon versions. Nodes that were on 0.8.2 or synced from scratch with this or a newer version should update smoothly.

p.s. To simplify the upgrade process, we also offer (optional) this script: restart_kmd_daemons.sh. Just run it on a host with launched Komodo daemons within a directory containing the new version of komodod and komodo-cli, and all launched instances will be stopped and re-launched with the new version of the daemon. Very convenient!

[DeckerSU]

It seems the only thing left to fix is this:

dPoW/doc/update0716.md

Lines 73 to 74 in 3b41c6a

	./m_notary_main
	./m_notary_3rdparty

It shouldn't be interpreted by operators as a single sequence of commands.

[DeckerSU]

After the latest changes, LGTM.