 Show Posts
|
|
Pages: [1] 2 »
|
|
Hi I just wanted to give an update on the state of the project.
* New algorithm ahead, it has been much more difficult than expected but shifu is doing well and making progress with his new algorithm miner implementation which is based on both, a GPU and a CPU part. This is the top priority for now and we hope to ship it next week. The design of the new algorithm is unique and the first of its kind.
* We have recently polished the output of the node software, now there are separate log files. This ensures the command line output is neat and clean.
* We are communicating with Exbitron for our first listing. Listing shall happen after the switch to the new algorithm.
* We now have a GUI wallet thanks to andrew and he is also working on a better explorer.
* Soon we will set up public nodes such that the GUI wallet can be used without running a node.
Some roadmap of things ahead:
* After listing the next goal is to support windows.
* Mining pool shall be set up next.
* Shifu has ideas to extend the basic functionality by a DeFI layer (shifu, please correct me if I am saying something wrong).
Warthog had a fair start, we did not reserve any of the supply for a dev fund. Everything is 100% mineable. We think that this is very important for a community cryptocurrency. But on the other hand we therefore need to collect some donations. The donation address for WART is
b897f693e81687b8d20947ecadfb83e4e850ac022134132e
A USDT donation address will be set up soon also for those who prefer to donation USDT.
Thank you all for your support!
|
|
|
|
The algo is custom and at some point we will change it to support GPU. You can specify the node IP and port only for the miner at the moment, not yet for wallet. We can patch it this week. Wallet address is a blockchain-specific thing, of course you can have mine to the same wallet address from different computers. I have created a discord group https://discord.gg/QMDV8bGTdQ. |
|
|
|
May I ask where the Warthog's blockchain browser is to see, or can you tell me how to help the Warthog build a blockchain browser
This is to be done. The basic functionality for a potential blockchain explorer is provided by the JSON RPC located at "localhost:3000". Opening this in your browser while running the node gives you a list of endpoints that provide all sort of information like balance, history, block details, etc. Block chain explorer is planned for later, now we are focusing on bug detection and fixes. And on creation of discord. |
|
|
|
I think this include 8 decimals.
Correct supply looks like to be - 18921600.
Please check with your dev.
Yes you are right. The exact total supply is 18921599.68464 (~19m) and will be reached after 58 years of mining (29 halvings). Also can you please setup a discord server?
We will try to do it this weekend. My node node program did not shut down, nor did it crash. It automatically stopped mining 3 times yesterday, but it has been almost 12 hours now, and there is no abnormality. It may be the reason for the unstable network.
Then it must be a bug. It is on our todo list. Your answer seems to be correct, but I feel that the total amount should be 1892160, so as to reasonably explain why there are 3 warthogs in a block.
It is 3 WRT per block and 3 blocks per minute, so 24*60*3*3=12960 WRT per day for the first two years. |
|
|
|
How to backup wallet files? Do I just need to copy the wallet.json file to complete the backup?
Yes. What is the total amount of this warthog cryptocurrency, any more info?
Total amount: 1892160000000000. But I will ask Pumbaa and Timon on this, maybe I am wrong. Can you leave your warthog address and I'll try to send you a transaction?
I generated a test address for you. {
"address": "5df6234660f5b9c1b20ac19de104187047200404009d02eb",
"privateKey": "f2f1785db56e21da825217f68ec144880df5eb9684eb50ecbfa1e1fc7b741c7f",
"publicKey": "0242e326af61b92ad0595952a7e6f37b56c647b495bd2c2a25aa81f40c859e2b10"
}[2023-07-05 17:57:43.648] [info] Hashrate: 25.351104 MH/s (~7.6 minutes per block
[2023-07-05 17:57:50.252] [error] API request failed. Are you running the node with RPC endpoint enabled?
The wart-node program must run while you are mining. You terminated it or it crashed. If it crashed please give info why it crashed. |
|
|
|
OK，May I ask how to refresh the balance and check the block status of the whole network
You can do so with the wallet: wart-wallet -b shows the balance. Please back up your wallet file. |
|
|
|
let me try again？
Yes, with newest code from GitHub. |
|
|
|
|
We have updated the GitHub repo. You can now run the program without LD_LIBRARY_PATH. Please try again now.
|
|
|
|
This is an older version and may not contain the required secp256k1_ecdsa_recover symbols. In order to get the latest version that supports the required symbols, I need to update to a newer library version. Maybe 20.04 does not support running this project at all
The problem is not that you have a too old sekp236k1 library installed but that you have installed this library and it has the same name as some library that we ship with warthog and the system library has higher precedence. We will rename the shipped library in our repo such that it does not have the same name anymore. For now you can remove the os package that installed this library. Our you prepend to every warthog command this: LD_LIBRARY_PATH=/home/meirong/youzhu/new/build/src/wallet/./../../thirdparty/secp256k1 meirong@OS-20230306EWPM:~/youzhu/new/build/src/wallet$ LD_LIBRARY_PATH=/home/meirong/youzhu/new/build/src/wallet/./../../thirdparty/secp256k1 ./wart-wallet
Wallet file 'wallet.json' does not exist yet. Create a new wallet file using the '-c' flag.
It works now. Congratulations. You need to create a wallet file by appending the "-c" flag. |
|
|
|
Please try meirong@OS-20230306EWPM:~/youzhu/new/build/src/wallet$ LD_LIBRARY_PATH=/home/meirong/youzhu/new/build/src/wallet/./../../thirdparty/secp256k1 ./wart-wallet
|
|
|
|
After rebuilding and compiling, the startup still fails, and the following error is prompted
meirong@OS-20230306EWPM:~/youzhu/new/build/src$ cd wallet
meirong@OS-20230306EWPM:~/youzhu/new/build/src/wallet$ ls -a
. .. wart-wallet wart-wallet.p
meirong@OS-20230306EWPM:~/youzhu/new/build/src/wallet$ ./wart-wallet
./wart-wallet: symbol lookup error: ./wart-wallet: undefined symbol: secp256k1_ecdsa_recover
What is the output of this? meirong@OS-20230306EWPM:~/youzhu/new/build/src/wallet$ ldd wart-wallet
|
|
|
|
Haha, I seem to build and compile successfully, it is not easy. You already compiled successfully. Relocation is the issue. This problem comes from the fact that you were copying the executable to a different place. See you have built in "~/Warthog/new/build" directory: 20230306EWPM:~/Warthog/new/build$ meson .. But you are executing form "~/Warthog/node" directory, So you have copied the executable to some different place. meirong@OS-20230306EWPM:~/Warthog/node$ ./wart-node --help
./wart-node: error while loading shared libraries: libusockets.so: cannot open shared object file: No such file or directory You should not copy the compiled files but execute them in place. Othrewise it cannot find the libraries. It is useless according to what you said, what system version does ubuntu support? No it is not useless. "Note: Ubuntu 20.04 does not meet these requirements." from the GitHub README file just states that Ubuntu 20.04 normally does not ship with gcc11 but you somehow installed gcc11 using some workaround (external packages?). In this case it should work. You already compiled it. Just start it in place, the missing symbol errors come from the fact that you copied the executable to a different place such that other compiled libraries are not found. May I ask which folder the node program is in, and what is the directory path? Where is the directory path of wart-wallet?
The important executables are in these directories: src
├── miner
│ └── wart-miner
├── node
│ └── wart-node
└── wallet
└── wart-wallet
These distro packages are not relevant: meirong@OS-20230306EWPM:~/Warthog$ dpkg -l | grep libsecp256k1
ii libsecp256k1-0:amd64 0.1~20170810-2 amd64 library for EC operations on curve secp256k1
ii libsecp256k1-dev:amd64 0.1~20170810-2 amd64 library for EC operations on curve secp256k1 - development headers
secp256k1 is built statically and shipped with the repo. No need for this to be installed. |
|
|
|
|
Don't copy/move the executable files, start them from the directory where they are generated. Does this help?
|
|
|
|
Haha, I seem to build and compile successfully, it is not easy. We tested on many new distros and it worked without problems, sorry that 20.04 is not supported out of the box. Pumbaa added a comment on the readme that 20.04 is not supported but you managed to compile on 20.04. Can you write down the steps into this issue? https://github.com/ByPumbaa/Warthog/issues/2This person also wanted to compile on 20.04 and with your steps it might work. May I ask which 2 programs do I need to run? wallet and which
Posted on: Today at 07:38:36 PM You need to run the node program to be able to mine. Then you need to generate a new wallet file and keep it safe. Do this with the "wallet" program, read the help you can access with "./wart-wallet --help`. You can print your wallet address by adding the "-a" argument after you generated your wallet file "./wart-wallet -a" Then you need to run the miner with your personal address from the wallet file. Again read the "--help" of the miner, you need to specify the address and number of threads to mine. Don't forget, the miner only has good performance if you compile everything with "--buildtype=release"! You need to append this to the meson command when you generate the build directory. |
|
|
|
Please try again later, this might be a temporary network issue: WARNING: failed to download with error: WrapDB connection failed to https://wrapdb.mesonbuild.com/v2/sqlite3_3.39.3-1/get_patch with error <urlopen error [Errno 111] Connection refused>.. Trying after a delay... And don't forget to delete the build directory before you try again. |
|
|
|
How did you upgrade to gcc 11? It is not a standard package of Ubuntu 20.04 LTS.Maybe you messed something up or only did a partial install without corresponding C++ headers like <span>. Can you try on a newer system like 22.04? You wrote: fatal error: pan: No such file or directory3#include <span>NNNNA Something is messed up here, "pan" and "NNNNA" are not normal output. Can you please open a GitHub issue with the correct output? Ubuntu 20.04.'s compiler packages are too old. You probably chose a workaround to install gcc 11 and did not succeed. You should try compiling on a newer system. Still the same error after I upgrade gcc11
Are you sure gcc11 is now used? Is gcc9 still installed? You also need to clear the delete the build directory and create it again. On creation meson outputs the compiler version used. |
|
|
|
I am not a C++ specialist, I would need to wait for pumbaa's or timon's opinion but I think <span> is not found because your compiler is too old?
Compiler version is checked with this command:
gcc --version
gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. The command I use is this, what is wrong? I have installed g++, graphviz, gtest, git, re2c, python2.7+ these dependencies cd ~ && mkdir Warthog && cd Warthog && git clone https://github.com/ByPumbaa/Warthog new && cd new && mkdir build && cd build && meson .. && ninja Your commands are correct but your build toolchain is too old, you should upgrade to a newer os version or upgrade your compiler but compiler upgrade is something for experts because it not only involves the compiler itself but also things such as placing new libraries and C++ include files. Please switch to a newer os which comes with gcc 11 or newer. |
|
|
|
|
