ei8ht187
ei8ht187
> Please update this issue when you got more information. We've found two blocks. Effort looks good now. Thanks a lot
Not in that way. Quote your question yes, but not my answer xD.
Do you use separate nodes for mining an payout? If so, did you set the mining pub key, the one starting with 88, in your mining nodes config?
Not much information, basically only "unknown message...error" 
> Would be helpful to see some pool logs showing the pool side of things. Erm, they are given in the screenshot part of your template: Screenshots [2022-02-25 21:27:14.1128] [I]...
Will this be fixed at all?
minDiff was set to 25000, difficulty itself to 500000. Since the hardfork with Monero 0.18.1.0 there is another problem. No miner can connect at all... Don't have a testenvironment ready...
> @ei8ht187 > > Like I said, `minDiff` must be set to `262144` or higher. This is according to Nicehash's [Pool Operator Guidelines](https://www.nicehash.com/pool-operators). The `minDiff` is a **Requirement** for compatibility...
> Well then you shouldn't have opened an Issue with the Title "XMR Poolverficator from Nicehash fails" b/c when you do that, it makes it sound a whole lot like...
> Did you get XMR working? > > I'm trying to discern whether you have a config issue or it's some issue being caused from the Monero hard fork on...