-
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
What is "normal" in time or amount of 16bit shares to get a 32bit share? #62
Comments
My miner ran 137h and only found 2 32bit shares with over 151k 16bit shares. I need todo some more trial and error checks with the pools, my worry is also as yours, I know small device but want to make sure its functioning 100percent. |
In the current code, this "Parsed JSON: unknown" is always returned as default, when no expected pattern is matching. No need to worry in that case, it's just a plain ACK response from the pool. I should be getting my device today, then I will do a testnet setup first. Unless this has been already done and miner verified on testnet? Didn't see a note about that yet, though. |
Good idea to test this on testnet. I hope if I change the pool settings and use a testnet wallet address will be enough... |
After 30 hours I found 1 32bit share (at ±25kh/s via CkPool) |
After 72 hours the second 32bit share. |
after 3.5 hour my first 32bit share doesnt seem so bad lol |
After 12 hours I have many 16bit shares, but still 0 32bit shares. What is likely normal to get a 32bit share of the amount of 16bit shares, or in time?
I get a feeling that the issue about parsing JSON, mentioned here, could be a problem why it doesn't get 32bit shares? Or am I wrong?
The text was updated successfully, but these errors were encountered: