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
Warning genesis coin not found #152
Comments
try reinstalling your node |
I think this problem is not about Node! +Same Issue |
well if it was an issue with the refrence code then mine wouldn't be working |
I tried with a fresh install of the node but it is still there. |
I said you. @jack60612 gave wrong info. This problem about Chia Pool Reference. We have to wait @mariano54 's reply. |
Listen if there is something wrong with the reference code how is it
working for me
…On Sun, Jul 11, 2021 at 8:01 AM Chiarex ***@***.***> wrote:
I tried with a fresh install of the node but it is still there.
I said you. @jack60612 <https://github.com/jack60612> gave wrong info.
This problem about Chia Pool Reference. We have to wait @mariano54
<https://github.com/mariano54> 's reply.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADRJMYOUF4EAI6MMZZH6VW3TXGB2HANCNFSM5AC4APRA>
.
|
We didn't say it doesn't work! We are just faced with such a meaningless error! |
That error means that the node cant find the first coin or genesis coin that is specified in the source code |
But does this have any negative consequences? Because 8 xch won in the pool. |
it can but it might not |
Thanks for your reply and interest. I installed "latest" branch. Maybe that's what's causing the problem. I'm going to switch to the main system. |
Your node needs to be synced up on the latest version (1.2+). |
Hello, I have a warning that keeps coming back in the pool logs.
2021-07-09T11:12:31.065 pool root : WARNING Can not find genesis coin fcf24cb4c229b9700
Does anyone have an idea what this is about?
The text was updated successfully, but these errors were encountered: