Don't specify --stratum-port. Do not specify that the mining software should be using the stratum protocol. If anything, try to see if you can specify that it should use getblocktemplate (frequently shortened as gbt).
The version of bitcoind doesn't really matter. Bitcoind never supported stratum so stop trying to use stratum with it.
The version of bitcoind doesn't really matter. Bitcoind never supported stratum so stop trying to use stratum with it.
On the bitcoind server, I ran it again without the --stratum-port
slightly different error
[2021-03-27 01:17:09] Pool 0 slow/down or URL or credentials invalid
[2021-03-27 01:17:09] No servers were found that could be used to get work from
.
[2021-03-27 01:17:09] Please check the details from the list below of the serve
rs you have input
[2021-03-27 01:17:09] Most likely you have input the wrong URL, forgotten to ad
d a port, or have not set up workers
[2021-03-27 01:17:09] Pool: 0 URL: http://127.0.0.1:8332 User: tom Pass
word: secret
[2021-03-27 01:17:09] Press any key to exit, or BFGMiner will try again in 15s
I am not sure how to specify gbt but ran across this on luke-jr github site-
Code:
SOLO MINING
BFGMiner supports solo mining with any GBT-compatible bitcoin node (such as
bitcoind). To use this mode, you need to specify the URL of your bitcoind node
using the usual pool options (--url, --userpass, etc), and the --generate-to
option to specify the Bitcoin address you wish to receive the block rewards
mined. When you run Bitcoin Core on the same computer as your miner, the pool
itself will be automatically configured for you (on the default goal). Please be
aware that solo mining via GBT is at this time only supported for Bitcoin.
IMPORTANT: If you are solo mining with more than one instance of BFGMiner (or
any other software) per payout address, you must also specify data using the
--coinbase-sig option to ensure each miner is working on unique work. Note
that this data will be publicly seen if your miner finds a block using any
GBT-enabled pool, even when not solo mining (such as failover).
If your bitcoin node does not support longpolling (for example, bitcoind 0.8.x),
you should consider setting up a failover pool to provide you with block
notifications. Note that solo mining does not use shares, so BFGMiner's adjusted
hashrate (third column) may suddenly drop to zero if a block you submit is
rejected; this does not indicate that it has stopped mining.
Example solo mining usage:
bfgminer -o http://localhost:8332 -u username -p password \
--generate-to 1QATWksNFGeUJCWBrN4g6hGM178Lovm7Wh \
--coinbase-sig "rig1: This is Joe's block!"
If you want to solo mine on multiple GBT-compatible Bitcoin blockchains, you can
specify --generate-to multiple times with a goal name prefix followed by a
colon. Note that at this time, the coinbase sig is always shared across all
goals/pools.
Example multi-blockchain solo mining usage:
bfgminer -o http://localhost:8332 -u username -p password \
--generate-to 1QATWksNFGeUJCWBrN4g6hGM178Lovm7Wh \
-o http://localhost:7221 -u user2 -p password --pool-goal mychain \
--generate-to mychain:1QATWksNFGeUJCWBrN4g6hGM178Lovm7Wh \
--coinbase-sig "rig1: This is Joe's block!"
I tried the --generate-to switch but still get the same errors regarding can't find the pool.
