Dual GLEEC

[smk762]

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

[DeckerSU]

As far as I know (@ca333 can correct me if I'm wrong), GLEEC wants to keep both chains notarized for now. So, we should have both the old GLEEC and the new GLEEC running simultaneously. However, since two chains with the same "ticker" (GLEEC) can't exist at the same time due to data folder conflicts, my suggestion is to move the old chain to the GLEEC.old folder while the new chain remains in the standard GLEEC folder.

The old chain would need to be launched with the -datadir argument, pointing to GLEEC.old. Additionally, we may need to differentiate the coin files, using GLEEC.old_7776 for the old GLEEC and GLEEC_7776 for the new one.

[DeckerSU]

It might also be a good idea to separate the komodod update from the GLEEC introduction. The komodod update should be the priority right now, so we can start that process to ensure that every NN is updated in time. We can then handle the GLEEC preparations in a separate PR.

[DeckerSU]

I also noticed that the new iguana/coins/gleec_7776 file for the new GLEEC contains an incorrect netmagic value. I’m not sure if Iguana actively uses it, but here are the parameters once again for checking/comparison:

OLD:

docker run --rm deckersu/komodo-chainparams:latest -ac_name=GLEEC -ac_supply=210000000 -ac_public=1 -ac_staked=100 | jq .

{
  "chainname": "GLEEC",
  "magic": 1824725725,
  "magic_bytes": "dd1ac36c",
  "magic_hex": "6cc31add",
  "p2pport": 23225,
  "rpcport": 23226
}

NEW:

docker run --rm deckersu/komodo-chainparams:latest -ac_name=GLEEC -ac_supply=1000000000 -ac_end=1 -ac_public=1 -ac_staked=50 | jq .

{
  "chainname": "GLEEC",
  "magic": 1193402844,
  "magic_bytes": "dce12147",
  "magic_hex": "4721e1dc",
  "p2pport": 23344,
  "rpcport": 23345
}

[DeckerSU]

The PR simply replaces the old GLEEC with the new GLEEC, instead of keeping both—you can see the details here.

@ca333 We should keep both GLEEC chains notarized, right?

[ca333]

The PR simply replaces the old GLEEC with the new GLEEC, instead of keeping both—you can see the details here.

@ca333 We should keep both GLEEC chains notarized, right?

yes, both chains will remain active / dPoW protected.

Once Gleec "sunsets" GLEEC-OLD we ll update things accordingly. But that will likely take some time.

[DeckerSU]

GLEEC and GLEEC_OLD should be running on the main server. This restriction is related to komodod, as the old GLEEC chain is a regular AC and cannot follow the notarisations (checkpoints) set by 3P nodes since komodod only has mainnet nodes' pubkeys hardcoded. Therefore, if we run it as suggested in this PR, it will not be protected by dPoW. To ensure proper protection, we need to run it as proposed here on mainnet servers with a separate data folder specified by -datadir.

Additionally, I highly recommend separating the GLEEC update from the komodod update. The komodod update is crucial and needs to be implemented as soon as possible, and it's ready to go. Therefore, my suggestion is to remove all GLEEC-related changes from this PR and open a separate PR for the GLEEC update after the komodod update is completed on all nodes.