Topic: Solo Mining BFGMiner, Various standalones & bitcoin-qt/bitcoind (Read 2465 times)

Thanks for the response.  I've been wondering about a setting up a bitcoin-qt node and allowing some friends to connect using my bfgminer as the proxy rather than each of them having to run a node themselves.  Then came the question about who gets the block reward when it's found.

Correct.  Payouts go to the address defined in --coinbase-addr.

If you don't specify --coinbase-addr, bitcoind will try to use the old getwork protocol instead of GBT.  You'll find that the daemon has a hard time keeping up with more than 10GH or so with getwork, and will be utterly useless once it pegs your CPU.  FWIW if you can solve a block on getwork, the reward will go to one of the unused reserve addresses in your wallet.  The reward for each block found would go to a different "random" address in your wallet.

Also - You can try out your config on testnet by adding  testnet=1  in your bitcoin.conf file...

Changed original question to hopefully be more clear and precise.

So I was re-reading the readme file about solo mining:

"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 --coinbase-addr
option to specify the Bitcoin address you wish to receive the block rewards
mined. 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)"

So does this mean that if I use the --coinbase-addr option that the block reward will go to that address rather than my bitcoin-qt wallet address?  Is that a possible solution to multiple people solo mining with bfgminer connecting to a bfgminer as a proxy pointed to the bitcoind client?

What happens if bfgminer is pointed to the bitcoind without the --coinbase-addr and a block is found?

If these are stupid questions, I'll apologize in advance!

I've changed the topic for my followup question.  In a nutshell, I'm wanting to know if bfgminer will allow s3 & A1 units to connect to it with bfgminer being the instance that connects to bitcoind client.  And if so, by using the --coinbase-addr, can each one have a different payout address rather than a solved block reward going to the bitcoin-qt wallet?

Thanks.



So I was re-reading the readme file about solo mining:

"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 --coinbase-addr
option to specify the Bitcoin address you wish to receive the block rewards
mined. 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)"

So does this mean that if I use the --coinbase-addr option that the block reward will go to that address rather than my bitcoin-qt wallet address?  Is that a possible solution to multiple people solo mining with bfgminer connecting to a bfgminer as a proxy pointed to the bitcoind client?

What happens if bfgminer is pointed to the bitcoind without the --coinbase-addr and a block is found?

If these are stupid questions, I'll apologize in advance!