Quote from: capulo on December 24, 2019, 10:26:30 PM

Quote from: togoshigekata on December 24, 2019, 06:58:49 PM

Hey capulo,

1. Are you upgraded to the latest version 1.4.8.4?
https://www.reddit.com/r/BiblePay/comments/echya3/biblepay_v1484_mandatory_christmas_2019_upgrade/

2. What does your config file look like?
(I had an issue using litemode=1 two weeks ago and had to remove it)

not yet, it should still work with older wallet no? but i'll try

nothing special in config,only gen=0

Enough masternodes upgraded that you will need to upgrade now

Quote from: bible_pay on December 23, 2019, 06:36:32 PM

Quote from: sunk818 on December 23, 2019, 05:07:56 PM

Quote from: bible_pay on December 23, 2019, 02:20:05 PM

Can you please try upgrading next? Ive already upgraded my sancs and home node, and the exchanges have upgraded, so at this point it would be counterproductive for me to downgrade just to see if they are on a fork. We can ask others, if anyone else is running the old version if they are going on a fork?

Upgrade works fine. The expectation from the previous communication about 1.4.8.4 was that 1.4.5.3 should work until the mandatory cutover block height. This doesn't seem to the case. Its not a big deal because the cutover height will arrive shortly, but it'd be nice to help wallet users plan better.

Correct, the code was supposed to be compatible until the cutover height; there is no flaw in the code. In addition it was written so to remain compatible even with the upgraded sancs.

However there is a DASH rule, where once 60% upgrade to the new governance protoversion, the old governance protoversion is no longer respected.

So, I believe this is a unique case, because we had a mandatory for the gov-protoversion to increase at the same time the wallet version increased.

If this ever comes up again, we will say: "By the height" or "when 60% of the sancs upgrade" whichever comes sooner- and we will have to monitor the progress.