Quote from: inblue on December 05, 2019, 11:12:16 AM

Quote from: MIP on December 05, 2019, 11:04:51 AM

Rob said this:
" In the mean time, I enabled deterministic mode for all sancs, so please upgrade your sanctuary to deterministic if you have not yet.
(As I dont want to take any chances with the next superblock)."

Please follow this guide:

https://www.reddit.com/r/BiblePay/comments/clyxyc/upgrading_masternodes_sanctuaries_to/

I am aware of the DIP3 upgrade procedure. I read every post carefully, I think it's not time for classic sanctuaries to stop working yet, take a look at this:

Quote from: bible_pay on November 20, 2019, 05:57:22 PM

The most probable outcome is we will focus on a Christmas mandatory upgrade and release all of this at once.

The biggest disruption this will require is everyone will need to be on deterministic sanctuaries by Christmas. I am working with Apollon now to find out if they will support us during the cutover (or not). If we do not have support from Apollon and Satoshi, we will recommend users who are about to be left behind use the new non-standard port feature to start a sanc. But in the mean time I will do my best to set us up with a seamless path.

So I expected a mandatory release for classic sanctuaries to be deprecated.

But the most important point of my post is that something is wrong with governance right now, which doesn't have anything to do with my sanctuaries being classic or DIP3.

I wanted to wait til Christmas to force the cutover to DM also, as the last thing I wanted to do was add more instability.

However, I had no choice but to flip the spork for DM early after finding out the votes being cast by the classic sanctuaries are not being counted in DM mode once that switch was thrown (even though it was reverted).

So now we are running in pure deterministic mode in the mainnet branch.

Please upgrade to DM, Im sorry for the inconvenience.

EDIT: As far as the PAM hash not matching, this would not be a good time to check that, but to try to explain part of that now: The PAM hash does not necessarily have to match for the network to be healthy, but Yes it should match in certain circumstances. First, the supermajority does need to have a matching PAM hash. For yours to match you must be on the same version, with the node synced, and with 'mnsync status' showing 999. Then lets check it about 50% through the day (into the GSC contract). At this point, most of the vote levels should be counted. Then your PAM hash should match the supermajority of the sancs. The one with the highest vote levels has an affinity programmed in to be voted in. You would have to learn more about 'gobject listwild' to see if your sanc is #2 or #3 in the voting levels and those have different PAM hashes.