Skip to content
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

Closed
Roalkege opened this issue May 20, 2023 · 5 comments
Closed

Does the miner really work? #32

Roalkege opened this issue May 20, 2023 · 5 comments

Comments

@Roalkege
Copy link

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.

@alcar21
Copy link
Contributor

alcar21 commented May 20, 2023

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

@BitMaker-hub
Copy link
Owner

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).
Could you be able to reach me on twitter or telegram to start a conversation about this and then to know your setup scheme?
Are you using custom ckpool?

@fti7
Copy link

fti7 commented May 24, 2023

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

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?

@Roalkege
Copy link
Author

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.
At the moment, the miner then also tries to log in to the pool with two threads etc. I think there must still be changed a bit in the code.

@BitMaker-hub
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants