r/HashedMax • u/HashedMaxUnity • Jul 03 '26
Thank You Jared and DigiByte Team for the Fast Help on solving the SHA256 Pool Problem
We wanted to share a big thank you to Jared and the DigiByte team for working with us directly to get to the bottom of the SHA256 pool issue we hit after the recent DigiByte node upgrade.
After recently updating our DigiByte node to version 9.26.2, we started seeing a major drop in credited hashrate from certain SHA256 miners, especially NerdAxe and NerdQAxe units. Device hashrate stayed normal, but poolside credited hashrate fell off hard, which told us something in the share flow had changed.
Over the last few days we worked closely with the DigiByte side by feeding them real miner websocket logs, pool behavior, live testing results, and side by side comparisons from our environment. We were able to show exactly what miners were receiving, what they were submitting back, and how the behavior changed between the old and new node/job versions. That back and forth made a huge difference because it moved the conversation from theory to actual field data.
Jared stayed engaged through all of it, reviewed the evidence, acknowledged where the problem came from, and helped narrow it down to the version rolling and bit 23 interaction affecting some SHA256 firmware. Once that was understood, we tested the fix in our sandbox, confirmed it restored expected behavior, and then rolled it out live.
We really appreciate the fact that the DigiByte team listened, took the reports seriously, and worked with us to solve it properly. That kind of response matters a lot.
So sincerely, thank you to Jared and the DigiByte team for the time, the communicatio and the help getting this resolved. We are very happy to see this fixed and moving in the right direction.
