Quote from: Rob Andrews on July 10, 2021, 01:13:34 PM
1) On the sanc wallet resyncing, could be that it needs the "-erasechain=1" done once. The old block chain is no good to this code branch. Once its up and running and synced, it will not resync by itself again.
2) The command on the controller should be 'exec upgradesanc MN1'. Maybe the manual omitted that part.
3) Your sancs list will be empty until you get past the upgradesanc (then it will show a sanc with a bad IP address), then after the revivesanc, it should show the correct info.
Thanks. indeed, the "exec" is missing in the guide (with upgradesanc as well as revivesanc).
The upgradesanc worked fine now, but I was then stuck on the "revivesanc" with "masternode with proTxHash 87...." not found.
The issue was, that it used my old proTxHash (from when I did the deterministic sanc many months ago).
I then deleted the old output from deterministic.conf and now it is running.
Of course it's currently POOS_BANNED (700), but that's probably because it's basically a new sanc. I'll E-Mail Todd the new child-ID and everything should be fine.

1000 BBP


before anyone experienced this...... Argh, sorry about that...
