This is related to #603, but valid for Anubis v1.20.0.

We are seeing instances in our logs that indicate the internal hash is incorrect b/c it lacks the initial zeroes.

For example:

"err":"challenge: error when processing challenge: validate: challenge: user failed challenge: wanted response 922d7b4603098a21a161aad68046e4f469b455b40137580e064dec6ef198b10f but got 0000a95424cdf7e6102b96a7e86cad60d37ef93a3bfd66a62da833fa2f113f3d"

I'm not really sure how to troubleshoot this issue. In some cases, the agent is clearly a bot, but, in any case, I don't know what could make the expected hash come out wrong.