Changing Bitaxe's starting difficulty? #1144
Replies: 5 comments 11 replies
-
Starting difficulty is set by the pool, the miner can suggest one, but the pool does not have to follow it. Setting the difficulty to "1" will just overload your local pool with worthless shares and traffic over your network. |
Beta Was this translation helpful? Give feedback.
-
That is exactly what I want, though. I've configured my pool to ignore any other block solution once it finds one. Have I understood right that it's the "256" number that I need to change? (Into 16 for example.) |
Beta Was this translation helpful? Give feedback.
-
You will not be able to solve a block with a difficulty of "1" for BTC, you will be just sending too many shares to the pool (I assume your running your own local node here to mine to). Research Stratum with VARDIFF to understand how it all works. |
Beta Was this translation helpful? Give feedback.
-
Post a screenshot of the logs from the miner here, lets see whats there for this. |
Beta Was this translation helpful? Give feedback.
-
I see nothing wrong here, it's working as expected. Testnet example where the network difficulty of the coin = 1 ![]() Stratum locked to 1 in the example. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm in a situation where I need Bitaxe's starting difficulty to be 1, because I need to solve a block with difficulty=1 and send it immediately (with the least delay possible) to my ckpool. Is it possible to configure the firmware to do that? I think there's a hardcoded minimum (256), because I've noticed my ckpool displaying solutions that are greater than 256. I was wondering, perhaps it's these four lines?
By "starting difficulty", I mean the difficulty that is minimum for the block solutions to be delivered to ckpool. As far as I know, all ASICs have a hardcoded minimum, like 65k, because otherwise it'd overwhelm the CPU.
Beta Was this translation helpful? Give feedback.
All reactions