Bitcoin Forum
May 11, 2024, 06:56:19 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin Core 12.1 Solo Mining Problem  (Read 1872 times)
krile (OP)
Hero Member
*****
Offline Offline

Activity: 746
Merit: 500



View Profile
May 10, 2016, 07:43:59 PM
 #1

Since the update to 12.1 I can not solo mine anymore.

I am solo mining (as a joke of course) with one usb antminer u1 on the same machine that is running the node, it worked so far but with the new version I am getting this in bfgminer:

Code:

 [2016-05-10 21:33:30] No servers were found that could be used to get work from

 [2016-05-10 21:33:30] Please check the details from the list below of the servers you have input

 [2016-05-10 21:33:30] Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers

Funny thing is, the bitcoind log reports a "create new block" message when I start the miner, not an "unauthorized rpc user/password error":

Code:
2016-05-10 19:32:41 CreateNewBlock(): total size 172240 txs: 323 fees: 5817514 sigops 960

But thats it, that is the one and only message I get regarding mining.

I know about this:

Code:
2016-05-10 19:29:21 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.

But it says soon, so not yet right?

Why is bitcoind not accepting a valid rpcuser and pasword that is in the bitcoin.conf file?


1715410579
Hero Member
*
Offline Offline

Posts: 1715410579

View Profile Personal Message (Offline)

Ignore
1715410579
Reply with quote  #2

1715410579
Report to moderator
1715410579
Hero Member
*
Offline Offline

Posts: 1715410579

View Profile Personal Message (Offline)

Ignore
1715410579
Reply with quote  #2

1715410579
Report to moderator
The network tries to produce one block per 10 minutes. It does this by automatically adjusting how difficult it is to produce blocks.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715410579
Hero Member
*
Offline Offline

Posts: 1715410579

View Profile Personal Message (Offline)

Ignore
1715410579
Reply with quote  #2

1715410579
Report to moderator
1715410579
Hero Member
*
Offline Offline

Posts: 1715410579

View Profile Personal Message (Offline)

Ignore
1715410579
Reply with quote  #2

1715410579
Report to moderator
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6635


Just writing some code


View Profile WWW
May 10, 2016, 08:12:46 PM
 #2

That is interesting. It is hard to tell if it is related to bfgminer or Bitcoin Core. I suggest that you open an issue with both projects on github. bfgminer: https://github.com/luke-jr/bfgminer/issues Bitcoin Core: https://github.com/bitcoin/bitcoin/issues

I think this may be due to the CSV soft fork that Bitcoin Core 0.12.1 is deploying, but I shouldn't be causing any problems.

krile (OP)
Hero Member
*****
Offline Offline

Activity: 746
Merit: 500



View Profile
May 11, 2016, 06:00:19 AM
 #3

That is interesting. It is hard to tell if it is related to bfgminer or Bitcoin Core. I suggest that you open an issue with both projects on github. bfgminer: https://github.com/luke-jr/bfgminer/issues Bitcoin Core: https://github.com/bitcoin/bitcoin/issues

I think this may be due to the CSV soft fork that Bitcoin Core 0.12.1 is deploying, but I shouldn't be causing any problems.

I think it might be bfgminer. If you check this bit-coin.pw which is a simple info page for bitcoind in php it obviously works. And it also uses rpcuser/pass. But this one just uses the getinfo rpc call.

But still bitcoind caused the problem since it changed something in the mining code that bfgminer does not like.

Strange that nothing is mentioned in the change log regarding mining...

Luke-Jr
Legendary
*
Offline Offline

Activity: 2576
Merit: 1186



View Profile
May 17, 2016, 07:45:06 PM
 #4

GBT/mining is broken in Core 0.12.1. I am actively working on getting this fixed for 0.12.2 and Knots 0.12.1, but for now, solo miners will need to downgrade to 0.12.0 or alternatively hack their 0.12.1 code.

If you want to hack the code, edit src/rpcmining.cpp and find the line:
Code:
aMutable.push_back("prevblock");
Add another line immediately before this, with:
Code:
aMutable.push_back("version/force");
Then recompile to have the changes take effect.

Note that this hack will ONLY work for CSV/0.12.1, and WILL NOT work with segwit or future softforks.
If you use this change after segwit is active, you will be mining INVALID blocks.

krile (OP)
Hero Member
*****
Offline Offline

Activity: 746
Merit: 500



View Profile
May 17, 2016, 08:17:12 PM
 #5

GBT/mining is broken in Core 0.12.1. I am actively working on getting this fixed for 0.12.2 and Knots 0.12.1, but for now, solo miners will need to downgrade to 0.12.0 or alternatively hack their 0.12.1 code.

If you want to hack the code, edit src/rpcmining.cpp and find the line:
Code:
aMutable.push_back("prevblock");
Add another line immediately before this, with:
Code:
aMutable.push_back("version/force");
Then recompile to have the changes take effect.

Note that this hack will ONLY work for CSV/0.12.1, and WILL NOT work with segwit or future softforks.
If you use this change after segwit is active, you will be mining INVALID blocks.

Thank you for your answer. I will downgrade to 12.0 for now.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!