They have it on the releases section of their GitHub page: https://github.com/bytepaydev/Bytepay/releases

Waiting on a fix for the coin daemon, I wouldn't mine on any pool unless it shows that it has successfully found any blocks at all (checked through the post and only 1 pool has this coin showing, it apparently has 800MH/s+ in which it should be fining a block every second and yet it hasn't mined a single block, not a great look for the pool or the coin)

Set system forward an 24 hours (took me awhile, is pretty late and was a setting on the system had not come across before that was immediately setting the date back via NTP after I set it.

Still same error.

I read the same bit earlier, tried upping the difficulty on the stratum to 1, same error, also skipped the check that was causing the error and then got an error about the merkle root, so think there is something deeper than just a difficulty error going on, other reading did on the error didn't sound promising but going further into the code the technical details of how it all operates was unfortunately beyond me.

Server is synced with NTP so time is good.

Hi,

Unfortunately still same error:

ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: CheckBlock() : CheckBlockHeader failed
ERROR: ProcessNewBlock : CheckBlock FAILED for block d339c33c53ba97081a4a89aa02a5e87dca97884ad09aa19bca0cf91d9e8ab146

AFAIK, the stratum proxy gets the information from getblocktemplate to provide to the miners and then submits any shares that come back above difficulty.

I would also be interested in seeing the changes on GitHub in the code to fix the 'CheckProofOfWork(): hash doesn't match nBits' error.

I saw the post in the Pools forum about someone asking for a pool for this coin and since it had low difficulty, was something I could solo mine on my pool thought would give it a go.