QBT's 30% Algorithm19 Feb 2023 19:53
I was thinking about QBT's 30% algorithm, to speed up bitcoin mining and wondering what it might do.
If I'm understanding things correctly, Bitcoin mining rigs calculate a valid hash, with a value below the Target, by inserting different values into the Nonce Field until they find a Nonce producing a valid hash. I'm guessing Mining Farms use software to simultaneously and continually allocate different Nonces to each rig in the farm, basically spreading the load.
The Nonce Field is 32 bits long, meaning there are 4,294,967,296 possible Nonces including all 0's, with a large percentage of Nonces suitable for producing a valid Hash.
If what I've just said is correct, to increase the speed of Mining Bitcoin by 30% QBT's software may work, in simple terms, by reducing the Nonce number pool from 4,294,967,296 down to around 3,006,500,000 possible Nonces, approximately 30% lower. From what I've read in other peoples posts, QBT's algorithm doesn't have a mathematical proof, so they're relying on testing the algorithm at various levels of Bitcoin difficulty, but the problem they're having is that testing is complicated because "testing this approach for the current level of difficulty, the leading zeros of the hash target, is computationally extremely demanding: each time we test at an higher level of difficulty from our current internal difficulty target, the amount of time/computing power needed, increases by 16 times."
I could be wrong in thinking QBT aren't mining on the Bitcoin network, and are in fact using test data with different Hash target's, but he uses the term "internal difficulty target" making me wonder. Possibly the only way to prove the algorithm works, at all difficulty levels, would be to find a large miner who'll incorporate the algorithm into their Farm setup, and prove it works as it should at the current Bitcoin difficulty level, thereby confirming the software does what it's supposed to do in the real world. Maybe it's an academic mentality to test something to death before it's put out there, but all software has bugs when it's first rolled out, then updated later to fix the bugs as they appear.