-
Notifications
You must be signed in to change notification settings - Fork 221
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
Genesis block failed to add #33
Comments
same here, I thinks its because the hardcoded the GTx. You have to adapt manually the Generate Genesis function from the old version. |
how to do that? just copy & paste ? |
Thats the question, but i think that wont work. I hope for a little update from the devs or an explanation for this tiny thing. |
same here the problem this one. any follow updates? |
bugged we need hardcode that genesis self xD |
I know this is a long issue, but here we go.
Yes!! That's the way. But frankly, I don't know if it worked correctly or not! The daemon started okay without any issues but the simplewallet bugged and froze the entire system over and over again, so idk. |
The problem genesis locked. Maybe bcn already changed core.
Shiro Mahiro
…On Thu, Feb 15, 2024, 04:32 Primo ***@***.***> wrote:
I know this is a long issue, but here we go.
You have to adapt manually the Generate Genesis function from the old
version.
Yes!! That's the way.
But frankly, I don't know if it worked correctly or not! The daemon
started okay without any issues but the simplewallet bugged and froze the
entire system over and over again, so idk.
—
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIFMP2R3GTAFKGW4A7JV5OTYTUUQNAVCNFSM4EXNIBGKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJUGQ3DMNZSGA3Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi, I manage to compile bytecoin binary. So then I want to run the bytecoind, I got genesis error as per subject.
Can someone help explaining what is going on in here?
The text was updated successfully, but these errors were encountered: