good news, I think I figured out what was going on, and there is an easy fix
when I replied that using ustx_balance vs. mstx_balance should not matter as long as it matches the code, I was assuming that the node would panic when reading the configuration file like it tends to do when anything is not right in that file if you did not use the expected keywords
but what happens instead is that it just ignores any values with [[...]] it does not know about, so you end up starting the miner without these balances, which results in a different consensus calculation (what I was suspecting all along), and why some nodes where mining off a different fork, and sure enough looking at your log, that's exactly when the consensus started to diverge while creating the genesis block
so, for either version 23, or 24.0, you must use the [[mstx_balance]] flavor
This PR includes an update to the configuration file as well as a check in the script that will update an existing config file to the correct format.
From @psq in Discord:
This PR includes an update to the configuration file as well as a check in the script that will update an existing config file to the correct format.