Quote from: bible_pay on December 04, 2019, 04:31:16 PM

Quote from: jaapgvk on December 04, 2019, 10:06:13 AM

Hi guys,

I was having some masternode trouble and upgraded all my wallets to the latest releases. My controller wallet is now on version 1.4.5.3 and the masternode wallet is on 1.4.5.4.
The problem is that I don't seem to be able to start my masternode, since the protocol version is different:

Controller wallet:

Code:

"version": 1040503,
"protocolversion": 70737,
"walletversion": 61000,

Masternode wallet:

Code:

"version": 1040504,
"protocolversion": 70749,
"walletversion": 61000,

I built the masternode wallet from source and downloaded the exe from the website for my controller wallet (windows 10 x64).

Any ideas on how to fix this? Can I 'downgrade' the masternode wallet to 1.4.5.3.? Of is that not possible in an easy way and is it easier to just install the controller wallet on a Linux box and build from source for the time being? Or (Rob) will the Windows wallet download on the website also be updated to 1.4.5.4. shortly?

Thanks!

I had that 70749 checked in (in mainnet) for about 12 hours; you probably upgraded during that time - but now its been rolled back to 70737.

Please just grab latest again and re-compile.

We seem to be OK now.

Affirmative; you can't start the sanc if the proto version is 70749, it must be 70737. (That was the main problem).

I'm moving to plan B in testnet today; we will need to modify the testnet branch to peer with prod for the rollout later this month.

Check! I re-compiled and now they are on the same protocol version

Thanks!

Also: thank you for the suggestion MIP, that was my plan-B.