-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rejected 2 stakes; #1478
Comments
Your beacon key is missing. Did you have to restore the wallet from backup? |
Can you give me your CPID? |
ce2a4b70c866643a115da634fc7f06fc |
Ok. You advertised a beacon about a week ago. Please fully unlock your wallet and then run beaconstatus and give me the result. |
"CPID": "ce2a4b70c866643a115da634fc7f06fc", |
I am going to delete your beacon and I will have you readvertise your beacon. Give ma a few minutes. |
I just deleted your beacon. Wait 10 min and then with a fully unlocked wallet, do advertisebeacon. |
Did you do the advertisebeacon? |
tyvm james... "ConfigKeyImported": true, |
still getting fail on beaconstatus, does it take a while to register? |
Yes. You need another 10-15 minutes. It has to go in the blockchain and be confirmed. |
its good now |
You should be good. Back on why this happened. Did you do anything with your wallet before? |
last month I did the upgrade to 4.0.4.0... that's all I recall doing. I do not recall messing with the wallet. |
Hopefully it will hold. BTW you can quickly search in the debug for staking problems by looking for the word "kernel". This is how I know your key was missing from your debug log... 06/10/19 03:12:47 {SBC} new best {fd0c4b20cf40f2667766c350e290bc7e100b687e5143ae264284f8f0a6f5ff48 1625180} ; |
Let's keep this issue open for tracking until you successfully stake. |
again, thanks for always solving my issues James. will let you know next stake. |
I think he did not loose the beacon key, but it was not imported into the wallet. |
I think you are probably right, although he successfully advertised the beacon a week before. Something doesn't make sense... anyway... looks like problem solved. |
Looks like you staked successfully! :) |
Yes I did …Thanks James
Victor Giaime
vic@veneer1.com
Ph: (516) 536-6480
From: James C. Owens <notifications@github.com>
Sent: Saturday, July 6, 2019 5:18 PM
To: gridcoin-community/Gridcoin-Research <Gridcoin-Research@noreply.github.com>
Cc: vgiaime <vic@veneer1.com>; Author <author@noreply.github.com>
Subject: Re: [gridcoin-community/Gridcoin-Research] Rejected 2 stakes; (#1478)
Looks like you staked successfully! :)
https://www.gridcoinstats.eu/cpid/ce2a4b70c866643a115da634fc7f06fc
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1478?email_source=notifications&email_token=AKE3EB4E6CLIV6KR4SGKOM3P6EDXZA5CNFSM4HW6VIX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZLANCQ#issuecomment-508954250> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AKE3EB4V2GLKGLZKH23N2O3P6EDXZANCNFSM4HW6VIXQ> . <https://github.com/notifications/beacon/AKE3EB2T6KIJGGH4IIGKZPDP6EDXZA5CNFSM4HW6VIX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZLANCQ.gif>
|
So, i'm apparently rejecting stakes again. idk why. I will try to post the debug file but it appears to be too big to post
The text was updated successfully, but these errors were encountered: