Solo Mining
-
Which miner are you using?
-
Have used about 16 different versions of ccminer, hsrminer, nsgminer, cpu-miner variants, pretty much anything I can throw at it. My problem is I’m not sure what’s not working, so I’m not sure how to address what’s broken by changing specific settings.
-
So before I was running the new version of the wallet (0.13.1), solo mining was working fine with nsgminer. My hash rates are terrible because I am using crappy cards on this rig, but this was a test rig anyway to see if I could get it working. Even so I managed to hit a block after 2 weeks.
nsgminer -o http://localhost:9337 -u user -p pass --coinbase-addr XXXXXXXXXXXXXXXXXX --intensity d
But now with this wallet, localhost is not working. When i run it with the address 127.0.0.1 the miner acts as if I’m in a pool. For now I am going to point it to the IP address and see if I can hit another block.
But I think you are right that getwork is now not supported, and we need a new build of nsgminer, and other miners to support the changes in QT.
-
I read on a forum last evening someone suggested a miner with --no-getwork to compensate, however, en-light of the fact that my memory fails me and I stupidly did not bookmark the resolved post, I’m left wondering if that may have been a solution.
Is it possible launching / configuring the server (feathercoind.exe) by itself will resolve this issue, or is it just broken in general?
Or is it a situation where it is just better to use older software due to the possibility that “newer is not always better.”
-
GetWork seems obsolete in Bitcoin Core and derivatives. You have to use GetBlockTemplate instead. You can specify your own coin base or use one provided by the daemon.
-
In a very generalized way I think I understand what you’re getting at, but like my inability to resolve my own issue due to ignorance, I don’t know how to apply the generality of your resolution to my own dilemma. (I’m too stupid to fix my own shit because I just don’t know enough about the underlying technology and I can’t find relevant information fast enough to mix and match and patch everything together to get it working given how all of this mining software is morphing.)
Basically, whatigottado to fix this broke shit? How’d I screw it up? I’ve followed every working example and template every forum and person has provided me so far to no avail.
Your wisdom is greatly greatly appreciated and needed.
-
Anyone out there that can help a bit more specifically? I’m pretty sure I’m only a setting or two away but am not sure what to do to get things working. Any help is appreciated.
-
This could be related to an RPC bug that was recently reported to me that affects Windows, the fix for this was applied here.
https://github.com/FeatherCoin/Feathercoin/commit/e66a93d62ad4cd5ffb0e08eee288afb30513635c
This fix has yet to be compiled into a new release and with 0.16 almost complete it may never as this issue is already resolved in 0.16.
For the mean time please consider pool mining. The difficulty is very high at the moment and it might now be a much longer time before solo mining pays out.
-
Thank you for your feedback and possible resolution. I’m too frustrated at this point. I suppose I’m just going to give up. I haven’t compiled code since high school C++, I have too much going on to relearn a bunch of nonsense that otherwise should be working in the first place. If you’d like a few FTC for helping out just ask, I’ll pull the little I have out of the exchange and send it your way. It’s only a few bucks, I don’t have much, leave your address. Thanks anyway though for the help.
Back to work at the forge, have another 500 hours left swinging a hammer to finish this project… Later, -K
=-\
-
@bushstar I really don’t trust pool operators, that’s why I am trying to mine coins with the possibility to mine solo. FYI I tried to mine with rpcauth instead of user, and now I am getting the 401 error. When will .16 be available?
-
You can probably still use v0.8 for solo mining as it is known to work with both GW and GBT.
-
0.16 cannot be released until SegWit is active on the network as it defaults to SegWit addresses and supports bech32 addresses. The 401 error is the one fixed in the commit linked above.
To follow the progress of SegWit follow it on the page below.
https://www.feathercoin.com/segwit-csv-tracker/
I’d expect SegWit and in turn 0.16 in about three weeks.
0.8 cannot be used to mine blocks as it generates version 2 blocks which are no longer accepted by the network.
Donate: 6hf9DF8H67ZEoW9KmPJez6BHh4XPNQSCZz
-
@hitherhills Just as a reminder. If you don’t trust pool operators you can always setup your own p2pool and have all the advantages of solomining while you are actually pool mining.
I use my own p2pool too. Currently i am mining on miningpoolhub though because the difficulty is so high and i like frequent payouts. But normally i would use my p2pool too just because it’s more secure.
-
@tobi97l said in Solo Mining:
@hitherhills Just as a reminder. If you don’t trust pool operators you can always setup your own p2pool and have all the advantages of solomining while you are actually pool mining.
I use my own p2pool too. Currently i am mining on miningpoolhub though because the difficulty is so high and i like frequent payouts. But normally i would use my p2pool too just because it’s more secure.
This was my thought as well. I set one up years ago, its not too difficult to do, give it a try!
-
@bushstar said in Solo Mining:
0.8 cannot be used to mine blocks as it generates version 2 blocks which are no longer accepted by the network.
It’s a one line change to generate whatever version blocks.
main.h:1299: static const int CURRENT_VERSION=2;
