To solo mine, you need two things: 1) external BBP miner, and 2) correct biblepay.conf file.
To get the external BBP miner, you can follow the directions mid-way here to download the BBP external miner. You can use the wallet to mine, but you will get less hashes for the same hardware so we do not recommend it.
Download external CPU miner
https://whitewalr.us/2019/biblepay-nomp-pool-mining.html#Download_BiblePay_external_CPU_miner
BiblePay-QT wallet needs correct biblepay.conf
The second part is needing the correct biblepay.conf
To edit your biblepay.conf, open the BiblePay-QT wallet, and go to Tools, Open Wallet Configuration File
It should open up in Notepad.
Your biblepay.conf should contain the following:
server=1
rpcport=40031
rpcuser=user
rpcpassword=password
rpcallowip=127.0.0.1
server=1 allows the miner to talk to the wallet and get work for solo mining
rpcport can be any unique port of your choosing
rpcuser is the user name you use to connect to the biblepay wallet
rpcpassword is the password you use to connect to the biblepay wallet
rpcallowip states what IPs can connect to the wallet.1
After you have edited your biblepay.conf, you must restart your wallet.
Generic Smart Contracts? (PoG, POOM, Healing)
I participate in Generic Smart Contracts (GSC)
With the current version, 1.4.5.2, you still need to add more things to biblepay.conf
for Generic Smart Contract (e.g. PoG, Healing, POOM). I would use the following values:
gen=1
genproclimit=1
minersleep=1950
I don’t participate in Generic Smart Contracts.
Does the QT wallet still need to have a mining thread running?
If you plan to solo mine with no GSC participation, you don’t need a mining thread running inside the wallet.
Command to solo mine with bbpminer
Using the biblepay.conf
listed above, below is the command you would use to solo mine.
bbpminer-x86.exe -o http://127.0.0.1:40031 -u user -p password
-o is URL and port you are connecting to. In our case, we are connecting to the wallet locally on port 40031
-u user is our user name (use something more complex in your setup)
-p password is our password (use something more complex in your setup)
If you are connecting to the correct URL and port, you will get number of hashes after a minute or two.
Error Messages
wrong port
Below is an example where we are connecting to a port that is not the same as biblepay.conf –
You get an error that says HTTP request failed[1]: Empty reply from server
json_rpc_call failed, retry after 30 seconds
wrong ip address
If you connect to an IP address that is wrong, you may get:
HTTP request failed[1]: Failed to connect to 222.0.0.1 port 40030: Timed out
json_rpc_call failed, retry after 30 seconds
hash rate not appearing
After you solo mining, the hash rate does not appear. This is normal and should not take more than 5 minutes as the Bible verses are being “memorized” into memory. You can also have a delay in mining hash rate show up if you have many threads. As you see in the screenshot below, it took about 3 minutes and 30 seconds for the hash rate to appear.
How many block can I earn with solo mining?
There is currently a solo miner that is mining most of the blocks that used to be a BOINC whale (eternal envoy).
Unless you are a hashing whale, you should not expect earn many blocks. With 10 megahash/s (MH/s), the nomp.biblepay.org pool is earning about 10% of the blocks per day (20 out of 205). If you have have 1 megahash/s (MH/s), perhaps you may earn a few blocks a day on average.
Rabinovitch said:
BTW, who need mining pools when any can get several blocks per day with only single Ryzen 7 3800X? ))
For now there are 3 CPUs with all available threads occupied. AMD FX-8350, 8 threads (don’t know how to measure the hashrate accurately, but apparently 15-16 khash/s per thread), Ryzen 7 3800X (16 threads, 31.5 khash/s per thread) and Ryzen 7 1700 (16 threads, 20 khash/s on average, when BURST miner does not occupy CPU). So totally I’m at about 952 khash/s. 7.5% of total network hashrate.
But I repeat, even with single R7 3800X I was getting a few blocks a day. And only after that I have switched my other CPUs to BBP solo.
- You can also remote computers to connect to the wallet, but that is outside the scope of this tutorial.[↩]
Sun, this does not mention the qt wallet. Is the qt wallet no longer needed for solo mining? If it is needed does qt wallet need to have a mining thread running still?
hi jsheets1970 – I’ve updated the article to be more clear about needing the QT wallet. I hope it makes more sense. Let me know if anything else is unclear or you want more details. I added a section about needing to mining threads internally or not (e.g. gen=1 yes mine internally, vs gen=0 no internal mining)
What if I get another error message under Ubuntu 19.10?
./bbpminer_linux: line 7: syntax error near unexpected token
newline'
‘./bbpminer_linux: line 7:
No matter whether I start it with parameters or without any.
I have not tested the binary in Ubuntu 19.10, only Ubuntu 16 and Ubuntu 18 personally. Perhaps the version is too new. I know Rob compiled the binary in Ubuntu 18 I think.
Rob suggested:
These are the dependencies mentioned by code:
apt-get install automake autoconf pkg-config libcurl4-openssl-dev libjansson-dev libssl-dev libgmp-dev zlib1g-dev make g++
Sorry, don’t have enough time (nor have I wish, sorry again) to make tests for developers. I have just compiled the miner from sources and it is working now. Windows binaries are OK though.
Hola el minero en solitario para windows 64 solo es compatible hasta windows 8, tengo w10 y no arranca
Hi, the solo miner for windows 64 is only compatible until windows 8, I have w10 and it doesn’t start
It should work fine in Windows 10. Many people use miner with Windows 10 just fine. Make sure you download correct 32-bit or 64-bit version.
Debería funcionar bien en Windows 10. Muchas personas usan miner con Windows 10 muy bien. Asegúrese de descargar la versión correcta de 32 bits o 64 bits.