I've been having a hard time resyncing every time we have a mandatory upgrade. I know part of the problem is when we force a new protocol version, it knocks all the sancs offline. (I have an old biblepay classic feature I am going to port that prevents that, allowing us to sync easier but still forces us to upgrade), so I will need to put this in today.

Two other things, I have realized one of the reasons we have trouble syncing when the diff is < .02 is because the wallet is having a hard time figuring out which fork is valid (in its diff calculator). I believe we will need a couple consensus rules added. For one, we should only add and enforce ABNs when the diff is > 1.0 in testnet (and a higher number in prod). I think this would help us immensely (coming to consensus). The other is the same with anti-gpu. We shouldnt really be monitoring or enforcing that if the diff < 1.0.

what about checkpoints? I saw in some wallets using checkpoints for easier sync or what.

what about checkpoints? I saw in some wallets using checkpoints for easier sync or what.

A checkpoint will help the wallet get on the right chain after one particular block in history at a certain mandatory height that passed.

But what I wrote explains a things in a lot greater detail than a checkpoint.

We do use checkpoints in our wallet (we have about 10 in classic etc), I added one to testnet but I havent been adding them because they dont address the problem fully, but Ill add one during the next mandatory.

I was able to set up a cold masternode successfully,and was able to upgrade to a dip3 masternode successfully!

Masternode IP: 149.248.35.69

Thats great!

Hey everyone I want to mention something important.

Before we enable dip15 (deterministic masternodes), we need to copy our 'masternodeblsprivkey' to our cold sanctuary biblepay.conf file (just like we usually copy the masternodeprivkey over there).

This is not used until we flip dip15. As I believe the moment we flip dip15 the sancs will rely on this privkey to sign all the messages (and thats likely why we had hundreds of failed votes yesterday once I flipped it for a couple mins).

So either way its mandatory that we copy the key to the sanc before dip15, so lets make that part of the upgrade to deterministic process.

I also forgot to mention this is the main reason I added the deterministicsanctuary.conf file - so you can open it back up and get the value out of it (or write a script to copy the value to the sanc).

Before we enable dip15 (deterministic masternodes), we need to copy our 'masternodeblsprivkey' to our cold sanctuary biblepay.conf file (just like we usually copy the masternodeprivkey over there).

This is not used until we flip dip15. As I believe the moment we flip dip15 the sancs will rely on this privkey to sign all the messages (and thats likely why we had hundreds of failed votes yesterday once I flipped it for a couple mins).

So either way its mandatory that we copy the key to the sanc before dip15, so lets make that part of the upgrade to deterministic process.

I also forgot to mention this is the main reason I added the deterministicsanctuary.conf file - so you can open it back up and get the value out of it (or write a script to copy the value to the sanc).

I already put the 'masternodeblsprivkey' in the biblepay.conf when I set-up my Sanctuary. I'm don't remember it exactly, but I think there was something in the set-up notes about it (maybe in Togo's) and I think that my (legacy) Sanctuary didn't even want to start when I didn't have it in there?

Anyway, I'm om the right chain, my Sanctuary is in DIP3, so I'm ready to roll

I already put the 'masternodeblsprivkey' in the biblepay.conf when I set-up my Sanctuary. I'm don't remember it exactly, but I think there was something in the set-up notes about it (maybe in Togo's) and I think that my (legacy) Sanctuary didn't even want to start when I didn't have it in there?

Anyway, I'm om the right chain, my Sanctuary is in DIP3, so I'm ready to roll

Dash's notes have the instructions to do it, but those notes are very complicated (to create a deterministic sanc from scratch).Yes, the sanc throws a warning right now if the masternodeblsprivkey is missing, but it still starts. (Using the masternodeprivkey).

Dash's notes have the instructions to do it, but those notes are very complicated (to create a deterministic sanc from scratch).Yes, the sanc throws a warning right now if the masternodeblsprivkey is missing, but it still starts. (Using the masternodeprivkey).

Ah, right! I probably got the warning and then proceeded to google the Dash notes.