Solo mining question/ new member =)
-
what am i doing wrong here in this miner config?
ccminer.exe -a neoscrypt -i 16 -o http://127.0.0.1:9337 -u pocketduece.1 -p x
everything else is pretty much set up to solo mine. i have synched the blockchain/wallet, i have added a server file to run the wallet in server mode. but when i start my miner up with that config
all it shows is this https://gyazo.com/a075987d287d4b4d977943eaabc0e01c.
it doesnt look like it is correctly solo mining, can anyone help me with this issue please? -
It looks okay so far there should be something like block number … in the console about every minute…
But I think with a single GTX1070 you should mine in a pool.
-
@milkeyway said in Solo mining question/ new member =):
ccminer.exe -a neoscrypt -i 16 -o http://127.0.0.1:9337 -u pocketduece.1 -p x
That means, that you have set up a rcpuser=pocketduece.1 and a rpcpass=x in your feathercoind configuration file.
Is that the case?
-
yes i have, im now trying to manually connect to my ip address and have a rig connect to it as well. running into a lot of hardships right now figuring it out, trying to be persistent tho, read somewhere that i might need to enable port fowarding so i am trying to do that
-
so i just tried to port forward, but didnt really do anything i dont think.
My config file looks like this currently
server=1
rcpuser= pocketduece.1
rpcpassword= x
rpcallowip=127.0.0.1
rpcallowip=192.168..
rpcport=9337this is my bat file on the server
ccminer.exe -a neoscrypt -i 16 -o 127.0.0.1:9337 -u pocketduece.1 -p x
i could not get it to work directly with a specific ip address. I tried to manually put all my ips and even did another persons suggestion of rcpipallow=0.0.0.0
This leads me to my biggest problem that i cant put my finger on how to solve which is how do i get my rig (client) which is also connected to the same router by another ethernet cable to connect to my servers ip. (it is either refusing to connect or timing out the connection)
-
The line is
rcpallowip=192.168.*After thinking again, I think that I hear, that the getTemplate function doesn’t work anymore for 0.9.x.
getTemplate is used for solo mining :(I didn’t solo mine for years, always used pools to get a more constant payout, so I’m not up to date here.
-
and this is the bat file for the miner on the rig,
ccminer.exe -a neoscrypt -i 16 -o http://192.168.1.7:9337 -u pocketduece.1 -p x
and this is the error im receiving https://gyazo.com/55e110a6fa414349932f0bc8f27bbabb
-
@milkeyway I move the thread to the mining section.
You can post there too now.
-
@Milkyway We’ve noted the problem with solo mining in the 0.9.x series. Although solo mining is only just viable for FTC, it has been moving up the priority list.
Other problems have been higher priorities because, there is a recommended workaround,
- Running your own private p2pool node on your miner PC.
https://github.com/wellenreiter01/p2pool-neoscrypt - using a P2pool server.
P2pool is similar to solo mining except the mining group find blocks more regularly.
So, it has not been treated as a stopper issue to the release of 0.9.6.(1) .
The natural out come of the current procedure will be, release of a “bug fix” 0.9.6.2 once a number of significant fixes or more likely, release of 0.11 series.
- Running your own private p2pool node on your miner PC.
-
@wrapper so in other words solo mining is broken and all these things im doing to try to fix it, is pointless? Am i correct in assuming this?
-
@Milkyway All life is pointless to some extent. I am not able to confirm solo mining is broken, because I can’t test it. You are reporting a fault, there is an issue someone else had a similar problem. Your experience seems to confirm there is a problem. I informed you of a way forward and that I would raise the priority. To do that, I checked and confirmed with others the issue exists on the “0.9.6.1 release chat”.
-
@wrapper thankyou wrapper, for i am not that experienced in this field yet as u can tell. i really appreciate your guys fast responses and meaningful tips and advice. Thankyou again and i will continue to keep trying and update this thread if i come to any sort of resolve
-
I was just reading this commit, it reminded me solo mining was moved to Feathercoin-cli …
https://github.com/litecoin-project/litecoin/issues/333#issuecomment-315607256
i.e. It’s not as simple as you do have the Feathercoin client running as well as the miner? to try solo mining.
-
Hi,
any update on this? I’m trying to solo mine with ccminer and 5 gtx 1070 but i got the same error.
Is there any way to manage it?
thanks
-
What guide are you using? are you using feathercoin-cli? may help someone answer the query/issue.
Otherwise, it may come up in some development were doing. We’d still need someone who can try any fixes, and be able to say, Phoenixcoin works but FTC doesn’t so we are sure (there is a problem).
-
Hi,
I’m just using the wallet and tried to solo mine as I’m doing with other coin pointing the miner to the wallet.
I don’t know how to use the -cli, is there any guide to follow?
thanks
-
What guide or instructions are you using? which coins have you successfully mined solo?
-
OK, I am trying to get some information about your set up. I have already mentioned that the problem may be that you need to run that (feathercoin-cli) to mine.
If that test doesn’t work - It then may be a fault we can fix. I have never solo mined (always used p2pool for ease and facility) so would have liked to look at a guide …
Instead of running the wallet you run feathercoin-cli
-
@greven said in Solo mining question/ new member =):
I don’t know how to use the -cli, is there any guide to follow?
The -cli has the same set of commands previously contained on feathercoind.
The whole rpc client has moved.I think you need 3 parts of software running to mine:
- feathercoind handling the block chain.
- feathercoin-cli accepting the incoming requests for m the miner
- the miner
I didn’t check that, it’s just my assumption
-
thanks,
it’s just that I don’t know how to run the -cli in Windows, if I launch it from cmd lines it’s just popup but I don’t the next steps
