Troubleshooting - No PoR or Interest payments in a month
I've got about 7000 GRC in my wallet and was staking once every 3-4 days all the way up until November 12. Now it's been nearly a month and I haven't staked even once since then. CPID beacon is on the neural network. Beacon's about 3 months old. Wallet is fully unlocked (not just for staking only), I've confirmed through gridcoinstats that there are rewards waiting for me, client is fully updated, and logs look good... what gives?
I've run out of ideas and I'm hoping someone here can provide some insight. Did something change with staking, and I missed the news? What could be the problem?
Posted Dec 6, 2017, 1:06 AM UTC
75
What block is the wallet up to? I found sometimes the wallet hangs.
It's fully synced up...as of this writing it's at 1099448
Can you try the command
in the debug console and tell us if it says
in the last line of the output? Do not post the whole output here as it contains private keys
"Beacon Exists" : "Yes"
"Block Signing Test Results" : true, and...
"Configuration Status" : "SUCCESSFUL"
Thanks for trying to help!
thanks, this command got me an error and that can finally mean i can narrow down why i get no payments at all. I have two addresses so this prob caused the beacon sending on the wrong one. I cannot remove the second empty one. Have also opened a message on github, hopefully they read it. This is what i got:
23:30:43  [ { "Command" : "beaconstatus" }, { "CPID" : "87ea9070ad53177b876a7d0607fc91a3", "Beacon Exists" : "Yes", "Beacon Timestamp" : "09-09-2017 16:32:20", "Public Key" : "04da3270a7fe281fabc6408419e6b90cc35ff12073318e544243c2cdfb87ea576abb462a65fb86b0446ee39e3a6c7795e52600fb70ee740ad5f5283a16f097b6fb", "Private Key" : "", "Local Configuration Public Key" : "", "Magnitude (As of last superblock)" : 3.00000000, "Block Signing Test Results" : false, "Errors" : "Private Key Missing. Local configuration file Public Key missing. Local configuration public key does not match beacon public key. This can happen if you copied the wrong public key into your configuration file. Please request that your beacon is deleted, or look into walletbackups for the correct keypair. Failed to sign POR block. This can happen if your keypair is invalid. Check walletbackups for the correct keypair, or request that your beacon is deleted. ", "Help" : "Note: If your beacon is missing its public key, or is not in the chain, you may try: execute advertisebeacon.", "Configuration Status" : "FAIL" } ]