Update: the snapshot got me synced. The problem in the image below is the same, except that it says that the sync check passes. Important thing is done, but if anyone has an answer to the other problem I'd be interested.
Hi everyone, I'm looking for some help with my wallet. I was on a good fork on version 3.7 for MacOS until about a week ago, so I reorganized to a prior block that had the correct hash. Unfortunately, every time I reorganize to a block it's just stuck there, the wallet doesn't sync beyond that block. Before downloading the snapshot anew, I decided to run diagnostics and the result is above. I've checked my gridcoinresearch.conf folder and added PrimaryCPID=(mypublicCPID), and the wallet still couldn't find my CPID. I also checked the .conf folder before and after the last beacon was sent (earlier in January, before this was a problem) - they were the same, and neither one of them had the entry PrimaryCPID, meaning it was working fine before then without that entry. I'm assuming that the "Verify CPID is valid" and "Verify CPID is in Neural Network" are failing because the CPID couldn't be found; according to gridcoinstats.eu my CPID is in the neural network.
In debug console, list cpids command gives correct, up-to-date information and list rsa command is also correct. I'm currently on v3.7.7.0. Any ideas? Has anyone else had this problem?
Can you post the output of getinfo and getmininginfo? I am interested in what block you are at. Also run getblockhash on the block listed in the "blocks" line and post it here. Let's see if you are actually on the main chain or not. Also, please post the block number/hash that you used to reorg on.
I reorganized on the same block/hash as what's listed in the "blocks" line below, although I did this several times, this block is the furthest I had gone back, as it was the last time I received minted GRCs.
That hash is on the main chain. Can you restart the wallet and then post the contents of the debug log post restart? Interesting that your IP is blank yet you have 47 connections. You are running a full node? You do not need that CPID entry in your conf.
We need to concentrate on getting you synced first...
What nodes do you have in your .conf file? I was able to sync by first downloading blocks, waiting for that to complete, and then rebuilding the block chain.
I find the reorganize command to be somewhat glitchy so I prefer to do the complete rebuild with the rebuild block chain command.
Nodes:
addnode=node.gridcoin.us
addnode=gridcoin.asia
addnode=grcmagnitude.com
I tried the Advanced > Rebuild Block Chain, but nothing happened after.
My next step was to download the snapshot and search for valid nodes, but the Find CPID failure made me think the problem was due to something else.
You could try adding
addnode=gridcoin.crypto.fans
which is the gridcoinstats.eu node to your .conf file.
Rebuild block chain needs a bit of time to work, so it's best to let it sit for a while after you have downloaded blocks or have the snapshot in place.
I've let download blocks run for a really long time, probably at least a day, but maybe that wasn't enough. I'm going to try the snapshot and see what happens. If it's the CPID I guess I'll find out.
Is your email correct in the config file? Also is your public and private key entry for your beacon in your config file? What does the command execute beacon status result in? (Please don't post this unredacted as it has sensitive info.)
Yes, the e-mail is correct. The public and private key entries for the beacon are in .config file. The execute beaconstatus command yields the same public and private keys as in the .config file, otherwise the beacon exists and all the other information there is correct and up-to-date.
There may be some info here that could help:
https://www.gridcoin.us/Guides/earn-grc.htm
You might try sending out beacons again with
execute advertisebeacon
and waiting to be included in the next superblock.
Unlocked my wallet (not just for staking) and tried that, got the following:
"Errors" : "ALREADY_IN_CHAIN"
Out of curiosity, do you have the same problem when you run diagnostics?
Seems like everything is in order. You might want to open a new issue on github. https://github.com/gridcoin/Gridcoin-Research/issues
Thanks for the advice. Out of curiosity, do you have the same problem when you run diagnostics?