-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does the miner really work? #32
Comments
Yes but the cpuminer don't have implemented the midstate and it's slower than nerdminer. Nerdminer(ESP32) can reach up to 80khs with the two threads but in this case we be able to only one thread for mining |
Hi Roalkege you are right. Currently NerdMiner is not submitting works based on current pool difficulty. It only tries to reach the block using the nbits param of stratum protocol. We directly omitted this part on code because we were unable to reach any pool difficulty. But it could be really interesting to really try this and could be the first step to setup a NerdMiner pool (just for fun). |
i've also seen that currently only one Mining Thread is active (mining.h:#define THREADS 1) Whats the exact reason for this? Theoretically there could be two independend Miner Threads or whats the issue here? |
The miner is not optimized to use two threads. |
Miner is optimized to use 2 threads and fixed some issues with merkle root calculations. Now can work properly good with any low share pool |
I have a own BTC Node and setup a pool on it with the mining diff 0.00001.
The Nerdminer is not able to find share with this diff. I find that a bit strange.
Now I tried a CPU miner on my PC that has only one thread (11-18 KH/s) and I find 5-10 shares per second with it. My NerdMiner has 21 KH/s.
The text was updated successfully, but these errors were encountered: