-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Start the daemon to print out the genesis block #337
Comments
It is not possible to do this from within the Github website itself. You will have to compile the code on your computer and run the daemon locally in order to generate your genesis block. Currently there is an active issue when trying to build the source on a more modern compiler that results in an error for "writing to an object of non-trivially copyable type" and until someone is able to propose a fix we won't be able to build the daemon to generate the genesis block. |
How to Compile a CryptoNote Coin on Windows 10/11There has been an active issue for over 5 years now when trying to build the source on modern compilers. Here is how I was able to compile my CryptoNote Coin using Windows 10. I made this guide on Windows 10 in October, 2023. If you need help compiling on Linux, then you can check my Ubuntu 14/16 guide. WINDOWS DEPENDENCIES FOR CRYPTONOTEWe are going to build for 64-bit Windows. Download the Build Tools for Visual Studio 2019 Installer COMPILING CRYPTONOTE ON WINDOWS WITH VS2019From the start menu, open Developer Command Prompt for VS 2019. |
Start the daemon to print out the genesis block Run your daemon with --print-genesis-tx argument. It will print out the genesis block coinbase transaction hash. Example: furiouscoind --print-genesis-tx.
I have been trying to understand how to do the this step in github.com
I have been able to go to the src/daemon then I go to Regulus/src/Daemon/Daemon.cpp but from there I'm lost, I'm new and if you can explain step by step I would appreciate it a lot.
The text was updated successfully, but these errors were encountered: