First, you need a BiblePay receiving address for mining reward funds to go… I recommend you send them to your own wallet instead of an exchange. Not your keys, not your funds.
Get your wallet at the official BiblePay site: https://www.biblepay.org/wallet/
These instructions will be specific to Windows 10 64-bit.
Once you download the wallet, run the setup.
Wait for your wallet to start syncing after after a few minutes. If your wallet does not start syncing, click here for step by step instructions on how to allow incoming connections and uPnP.
Once the wallet is syncing, go to File, Receiving addresses…
Click on New
Give it a label such as NOMP and click OK
This is your new receiving address for the BiblePay NOMP pool.
Make sure you highlight nomp label and click copy. This will copy the address to your clipboard. Use it later when you enter the user name for external miner.
Now download the BiblePay external CPU miner
bbpminer-x86.exe is for Windows 64-bit
bbpminer32.exe is for Windows 32-bit
Go to the version you want then click on Download
It is common for Windows 10 to say crypto CPU miners is a virus (false positive). If this is the case for you, you can exclude the BiblePay miner from the virus check.
Go to your Downloads folder (or wherever you have your browser save files to)
In the File Explorer, type
cmd (this is short for Command Prompt)
In the Downloads directory, you can start the miner by running the following command on any of the three pools.
You can replace the user name with your BBP receive address.
Pool run by me:
bbpminer-x86 -o stratum+tcp://188.8.131.52:3032 -u BEXTU6iVeBdoqgwbP8rmzYNoKhQgwz5BGs -p x
Pool run by TheRogue:
bbpminer-x86 -o stratum+tcp://leopool.biblepay.org:3032 -u BELmnDtPLJqcCUNR6hGhPuM6Bswmb11iRu -p x
Pool run by Rob Andrews:
bbpminer-x86 -o stratum+tcp://nomp.biblepay.org:3032 -u BA9dgF5BKMcNqyaPJimd7s8V4DdovDpF8B -p x
Remember the address you copied to the clipboard? You can use it here.
Give the external miner a few minutes to start hashing. If you see yay!!! after a few minutes this means the miner is sending shares to the pool.
|By default the cpu miner will use all the CPU threads to start mining.||If you have 4 threads and only want to use 2, then you would add before -o |
|-o is the pool you want to connect to||This will connect to the BiblePay NOMP pool on port 3032 (where difficulty is set to 3)|
|-u is the BiblePay receiving address you want your mining reward to be sent to||You will only receive a portion of the mined reward after 12 hours (the reward needs to confirm 102 blocks)|
|-p is the password you sent to the pool||You can make it whatever you want, such as |
Common messages on the external cpu miner
accepted: 1/1 (100.00%), 143410 khash/s (yay!!!)
yay!!! means your miner was able to generate a share with enough difficulty and sent it in the pool.
accepted: 1/2 (50.00%), 79.16 khash/s (booooo)
booooo means you submitted a share to the pool but it was not accepted. It could be a duplicate share, stale share, etc but it was not accepted by the pool. This is normal and should stay under 1% most times (e.g. Your percentage over time should stay 99.0% or higher).
Stratum requested work restart
The pool sent you new work. This is normal and occurs several times a minute. This occurs whenever the pool wants new work to start, or when the current block is mined and every miner needs to start work on a new block
This error message by itself without Stratum connection interrupted means you are temporarily banned. You’ve submitted too many rejected shares as a total percentage of acceptable shares. Ask the pool owner to look at the logs and see if your miner worker is being banned temporarily.
Shares submitted to the pool are rejected because of errors such as:
- duplicate share
- ntime out of range
- difficulty too low (low share difficulty)
- job not found (aka stale share). The miner submitted a share too late belonging to the previous block. New block found and pool sending out work for new block height.
Stratum connection interrupted
Connection to the pool was interrupted. This should occur infrequently. If this occurs often, then your connection to the pool is not stable. It could be your connection, the pool is having stability issues (maintenance, server issues, etc), or the network route to the pool is unstable. On your local computer, using wired ethernet connection is preferred over wireless if possible.
thread 0: 94190 hashes, 17.63 khash/s
the miner will report back to you what the average hash rate is for each thread
If you want to report your hash rate, I will be running a bounty to collect external miner hash rate. Comment below if you want to be contacted about bounty.
biblepay external cpu miner help file
C:\bbp> bbpminer32.exe --help KJV Loaded Using bbpminer version 1009 Usage: bbpminer [OPTIONS] Options: -a, --algo=ALGO specify the algorithm to use scrypt scrypt(1024, 1, 1) scrypt:N scrypt(N, 1, 1) sha256d SHA-256d pobh proof-of-bible-hash (default) -o, --url=URL URL of mining server -O, --userpass=U:P username:password pair for mining server -u, --user=USERNAME username for mining server -p, --pass=PASSWORD password for mining server --cert=FILE certificate for mining server using SSL -x, --proxy=[PROTOCOL://]HOST[:PORT] connect through a proxy -t, --threads=N number of miner threads (default: number of processors) -r, --retries=N number of times to retry if a network call fails (default: retry indefinitely) -R, --retry-pause=N time to pause between retries, in seconds (default: 30) -T, --timeout=N timeout for long polling, in seconds (default: none) -s, --scantime=N upper bound on time spent scanning current work when long polling is unavailable, in seconds (default: 5) --coinbase-addr=ADDR payout address for solo mining --no-longpoll disable long polling support --no-getwork disable getwork support --no-gbt disable getblocktemplate support --no-stratum disable X-Stratum support --no-redirect ignore requests to change the URL of the mining server -q, --quiet disable per-thread hashmeter output -D, --debug enable debug output -P, --protocol-dump verbose dump of protocol-level activities --benchmark run in offline benchmark mode -c, --config=FILE load a JSON-format configuration file -V, --version display version information and exit -h, --help display this help text and exit C:\bbp>