I have updated the github release page with a new build of the wallet. It contains new checkpoints and ups the protocol version to 72001 from 72000.
I added two rpc commands:
strictprotocol
strictincomingIf you are having trouble with high CPU and other peers trying to give you wrong chain data, or requesting data continuously the use "strictincoming true"
If you still have more problems, you can try strictprotocol.
Please do not use this unless you absolutely have to. It will drop your peer count low, and doesn't connect you to the main pool of peers.
https://github.com/hyperstake/HyperStake/releases/tag/v1.1 "strictincoming" is needed on my end and it works like a charm, cpu load is most of the time iddle.
But still often out of sync displayed so still many users on the wrong chain that get connected.
Maybe a more aggressive approach would be better ?
Simply ignoring/banning users that are on the wrong chain as it is done in some other projects.
Can you make these options work using command line and as conf options ?
Is update notification now active in latest versions or was it just a try out in one of the test build ?
Trololoh I included this, and I recommend you only use this rpc call if strictincoming is not doing the trick. "strictprotocol true"
And yes, alerts are active in all new wallet builds.