1
General Support - Solved / Re: wallet 1.5.1.4 hi cpu usage
« on: June 08, 2020, 04:16:38 AM »
ok, thanks for the info.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
We should technically re-sync better on this version (I mean the initial sync after upgrading only), as now we have classic's code for mandatory upgrades in.ha, to late. I deleted everything and now I have a problem, no peers
BTW: Please dont erase any files, just upgrade.
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.what about checkpoints? I saw in some wallets using checkpoints for easier sync or what.
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.
After resyncing my sancs and starting them I see this hash:
11:21:31

getblockhash 40668
11:21:31

9c1b6d67d8737b9976eed162b8edce7018430a9f2d16cfd97e4c83b14943baf6
Anyone agree with mine?