Author

Topic: Solo mining, 0 accepted (Read 2867 times)

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
April 10, 2013, 10:23:16 PM
#8
solo mining = hashes accepted only if it matches the network difficulty, which will take forever.

Ah, that makes sense... going to be a long while never before I see an "Accepted" then Smiley
There, FTFY.
sr. member
Activity: 389
Merit: 250
April 10, 2013, 10:20:04 PM
#7
sorry, missed the "Connected to server" line.  Good luck!
legendary
Activity: 2058
Merit: 1452
April 09, 2013, 04:56:02 PM
#6
solo mining = hashes accepted only if it matches the network difficulty, which will take forever.

Ah, that makes sense... going to be a long while before I see an "Accepted" then Smiley
it might be smart to verify your configuration is correct by mining a few testnet blocks.
member
Activity: 63
Merit: 10
April 09, 2013, 10:52:17 AM
#5
solo mining = hashes accepted only if it matches the network difficulty, which will take forever.

Ah, that makes sense... going to be a long while before I see an "Accepted" then Smiley
member
Activity: 63
Merit: 10
April 09, 2013, 10:50:49 AM
#4
do you have a bitcoin.conf file in your bitcoin data folder with a RPC password set?

something like (this may not be exactly correct):

server=1
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=8332

Yes, the bitcoin.conf file is configured, otherwise the client wouldn't connect to the server, right?

Here is the bitcoin.conf file:
Quote
server=1
rpcuser=bits
rpcpassword=*****
rpcallowip=192.168.0.*
rcpport=8332
paytxfee=0.00

I enabled verbose mode, here is the output:


Thanks!
legendary
Activity: 2058
Merit: 1452
April 09, 2013, 10:47:05 AM
#3
solo mining = hashes accepted only if it matches the network difficulty, which will take forever.
sr. member
Activity: 389
Merit: 250
April 09, 2013, 10:42:27 AM
#2
do you have a bitcoin.conf file in your bitcoin data folder with a RPC password set?

something like (this may not be exactly correct):

server=1
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=8332
member
Activity: 63
Merit: 10
April 09, 2013, 10:09:46 AM
#1
Dorking around with solo mining on a spare rig and it never accepts any hashes even though it is running full tilt.



Ignore the low hash rate, I haven't optimized the client with flags yet.  Yes I know that that'd likely take years to find a block solo these days.

Running a Phoenix 2.0 client and connected to Bitcoin-qt v0.8.1-beta running in -server mode that has downloaded the full blockchain.

Where have I gone wrong?
Jump to: