search

oliverw / miningcore

Miningcore is a high-performance Mining Pool Software for Linux and Windows.
https://store.miningcore.pro
MIT License
730 stars 676 forks source link

Asicboost compatibility with nicehash #1549

Open goodthebest opened 1 year ago

goodthebest commented 1 year ago

Hey, asicboost is working fine with local asic machine, however it's not going through with nicehash pool verification. Any clue, what needs to be done? anyone worked it around?

zvenimir commented 1 year ago

It worked fine two years ago. But now with last release can't go through verification

nicehash issue

But my local workers start mining from second connection attempt. First connection attempt always closing. Maybe here is no any issue, and working well? Will mine some btc to nicehash and check later...

zvenimir commented 1 year ago

It is not working. Only connection accepting... connection accepted... connection closed... Maybe because nicehash do not trying reconnect with the same IP which connection was closed before. It looks like that. First connection to Miningcore always closing, as I see, but after working well in my local network. Because local workers do not change they IP's?

papagruz commented 1 year ago

I to have this problem with asicboost nicehash. How can help with fix this problem?

goodthebest commented 1 year ago

@zvenimir two years ago what miningcore version did it work well with asicboost (nicehash)?

zvenimir commented 1 year ago

@zvenimir two years ago what miningcore version did it work well with asicboost (nicehash)?

Can't remember. That system wiped many times ago. This version was iinstalled in second half of 2020, as I remember.

XIII39 commented 1 year ago

I think it happened between Release 53 & 54 when the NiceHash API was introduced. Seems that the NiceHash Algorithm is called 'SHA256AsicBoost' as opposed to 'SHA256' so perhaps Miningcore doesn't know what to do with that.

Just a thought.

EDIT: Never mind, I was wrong. SHA256AsicBoost was working up until release 59, the last .NET5 release. In release 60 onward, after NH connects instead of authorizing the worker it states "Using version-rolling mask 1fff3eee" then closes the connection.