excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a]

[dropky]

We released new version of excavator: https://github.com/nicehash/excavator/releases/tag/v1.5.0a

Changelog:

• bug fixes & improvements
• changed stratum protocol to NiceHash Miner Protocol
• API version bumped to 0.1.0
• added algorithm CryptoNightV7 (XMR)
• speed improvements for CryptoNight
• added support for Tesla P100

Additional notes:

• From version 1.5.0a further excavator supports only NiceHash stratum servers. Stratum servers are available at:
  nhmp.LOCATION.nicehash.com (LOCATION: eu, usa, hk, jp, in, br).
• Excavator API has changed!
• This version of Excavator is not compatible with NiceHash Miner (yet).

Config file example:

Code:

[
	{"time":0,"commands":[
		{"id":1,"method":"subscribe","params":["nhmp.usa.nicehash.com:3200","34HKWdzLxWBduUfJE9JxaFhoXnfC6gmePG.testrig"]}
	]},
	{"time":2,"commands":[
                {"id":1,"method":"algorithm.add","params":["equihash"]}
        ]},
	{"time":3,"commands":[
		{"id":1,"method":"worker.add","params":["equihash","0"]}
	]},
	{"time":10,"loop":10,"commands":[
		{"id":1,"method":"worker.print.speed","params":["0"]},
		{"id":1,"method":"algorithm.print.speeds","params":[]}
	]}
]

[nitrobg]

From version 1.5.0a further excavator supports only NiceHash stratum servers.

Why?

[dropky]

From version 1.5.0a further excavator supports only NiceHash stratum servers.

Why?

We implemented our own stratum protocol (nhmp) to reduce the network traffic.   

[EvgeniyKorepov]

We released new version of excavator: https://github.com/nicehash/excavator/releases/tag/v1.5.0a

Changelog:

• bug fixes & improvements
• changed stratum protocol to NiceHash Miner Protocol
• API version bumped to 0.1.0
• added algorithm CryptoNightV7 (XMR)
• speed improvements for CryptoNight
• added support for Tesla P100

Additional notes:

• From version 1.5.0a further excavator supports only NiceHash stratum servers. Stratum servers are available at:
  nhmp.LOCATION.nicehash.com (LOCATION: eu, usa, hk, jp, in, br).
• Excavator API has changed!
• This version of Excavator is not compatible with NiceHash Miner (yet).

Config file example:

Code:

[
	{"time":0,"commands":[
		{"id":1,"method":"subscribe","params":["nhmp.usa.nicehash.com:3200","34HKWdzLxWBduUfJE9JxaFhoXnfC6gmePG.testrig"]}
	]},
	{"time":2,"commands":[
                {"id":1,"method":"algorithm.add","params":["equihash"]}
        ]},
	{"time":3,"commands":[
		{"id":1,"method":"worker.add","params":["equihash","0"]}
	]},
	{"time":10,"loop":10,"commands":[
		{"id":1,"method":"worker.print.speed","params":["0"]},
		{"id":1,"method":"algorithm.print.speeds","params":[]}
	]}
]

Config:
[
   {"time":1,"commands":[
      {"id":1,"method":"subscribe","params":["nhmp.eu.nicehash.com:3200","3DQ9fRMVfxHaTkxt2y8BBDnVb1eAad94NP.home"]}
   ]},
   {"time":2,"commands":[
      {"id":1,"method":"algorithm.add","params":["cryptonightV7"]}
  ]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["cryptonightV7","0"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"worker.print.speed","params":["0"]},
      {"id":1,"method":"algorithm.print.speeds","params":[]}
   ]}
]

Result:
[13:41:37][0x00003b58][info] Log started
[13:41:37][0x00003b58][info] core | Found CUDA device: GeForce GTX 960
[13:41:37][0x00003b58][info] api | Listening on 0.0.0.0:33333
[13:41:37][0x00003b58][info] http | Listening on 0.0.0.0:38080
[13:41:37][0x00003b58][info] core | Initialized!
[13:41:38][0x00003b58][info] Connected to nhmp.eu.nicehash.com:3200
[13:41:38][0x00000ab8][info] nhmp | Subscribed
[13:41:39][0x00003b58][info] nhmp | cryptonightV7 | add failure
[13:41:39][0x00003b58][info] nhmp | Reason: Internal server error (-1)
[13:41:40][0x00001224][info] wrkr0-0 | Algorithm: CUDA-cryptonightV7 parameters: B=14,TPB=32
[13:41:43][0x00003b58][info] nhmp | Disconnected
[13:41:43][0x00003b58][warning] nhmp | read: WebSocket connection closed normally

[dropky]

@EvgeniyKorepov I answered you on GitHub

[apiontek]

I see no linux version, will there still be linux builds forthcoming?

Not that I'll be upgrading without standard stratum support (Not that Nicehash has any reason to care about that ).

But sometimes I choose to mine at Nicehash, and it'd be nice to use the latest version for that on linux.

(What would really get me to commit to Nicehash would be implementing lyra2z algorithm, but I realize that's not in the hands of excavator developers, and I've already given Nicehash Support my two cents on that.)

[dropky]

I see no linux version, will there still be linux builds forthcoming?

Not that I'll be upgrading without standard stratum support (Not that Nicehash has any reason to care about that ).

But sometimes I choose to mine at Nicehash, and it'd be nice to use the latest version for that on linux.

(What would really get me to commit to Nicehash would be implementing lyra2z algorithm, but I realize that's not in the hands of excavator developers, and I've already given Nicehash Support my two cents on that.)

Yes, we'll release linux version shortly.

I'll see what I can do regarding the lyra2z.   

[apiontek]

I see no linux version, will there still be linux builds forthcoming?

Not that I'll be upgrading without standard stratum support (Not that Nicehash has any reason to care about that ).

But sometimes I choose to mine at Nicehash, and it'd be nice to use the latest version for that on linux.

(What would really get me to commit to Nicehash would be implementing lyra2z algorithm, but I realize that's not in the hands of excavator developers, and I've already given Nicehash Support my two cents on that.)

Yes, we'll release linux version shortly.

I'll see what I can do regarding the lyra2z.   

Excellent, re: Linux versions.

For lyra2z I won't hold my breath, but it'd be sweet to be able to mine it at Nicehash. It's an excellent CPU algorithm so far, and frequently one of the highest earners at MiningPoolHub and a couple other pools, for both GPU and CPU. Better CPU earner than cryptonight, really.

[akuci]

So what about equihash? Any plan to catch DSTM?

[dropky]

So what about equihash? Any plan to catch DSTM?

Yes, we're working on it.

[dropky]

Pushed out a new version today (linux version as well):
https://github.com/nicehash/excavator/releases/tag/v1.5.1a

Changelog:

• API bug fixes
• Added devices.get method to API
• CryptoNight and CryptoNightV7 bug fixes
• Speed improvements for lyra2rev2 on Titan V

[nitrobg]

From version 1.5.0a further excavator supports only NiceHash stratum servers.

Why?

We implemented our own stratum protocol (nhmp) to reduce the network traffic.   

No way to maintain backwards compatibility? Your miner is the best for neoscrypt and possibly other algos as well.

[dropky]

From version 1.5.0a further excavator supports only NiceHash stratum servers.

Why?

We implemented our own stratum protocol (nhmp) to reduce the network traffic.   

No way to maintain backwards compatibility? Your miner is the best for neoscrypt and possibly other algos as well.

Unfortunately no. You can still use old versions that are supporting the standard stratum protocol.

[remauto1187ma]

My 2 rigs (running nicehash) have gone full retard starting yesterday.  Numerous crashes.  Rig 1 popping up with Nvidia Driver update warning.  I have the latest and it still pops up with it now and then since yesterday (i see this warning because of the numerous crashes and needed reboots).  Rig 2 running without driver warning even though it has the same Nvidia driver updates AND has all GPU's (11) that are Nvidia GTX 10 series. It has crashed less than Rig 1 though.  As if the lower payouts arent enough now ive gotta deal with instability and loss of profit from all the crashes.  Changes are coming soon....at my house.

[apiontek]

To everyone worrying - you can still use 1.4.4a for legacy stratum protocol pools. So far I haven't noticed that 1.5.x is significantly faster. It seems a teensy tiny bit faster in equihash, but it's a wash for neoscrypt and lyra2v2. So just keep using 1.4.4a if you don't want to mine at nicehash.

Also, if you already have mining scripts that use multiple miners, it shouldn't be too hard to add in the new excavator as a totally new miner. Say, call the old one "excavator-classic" or call the new one "excavator-nhmp" or something. That's what I did.

To the excavator devs:

question: is there any chance of the new nicehash mining protocol being documented or open-sourced in some way so other software devs could implement support for it in their miners? Setting aside dstm -- which it sounds like you're working on overtaking anyway -- ethminer, claymore, xmrig and xmrig-nvidia for example are all still significantly faster than excavator, and if they could support nhmp I bet it'd be a net positive for Nicehash.

[tadeus1]

https://github.com/nicehash/Specifications
although not updated recently.

As far as I know most popular other miners already have support for it already - i.e. Claymore, dtsm, etc.  unless I am missing something here, what new mining protocol?

[dropky]

My 2 rigs (running nicehash) have gone full retard starting yesterday.  Numerous crashes.  Rig 1 popping up with Nvidia Driver update warning.  I have the latest and it still pops up with it now and then since yesterday (i see this warning because of the numerous crashes and needed reboots).  Rig 2 running without driver warning even though it has the same Nvidia driver updates AND has all GPU's (11) that are Nvidia GTX 10 series. It has crashed less than Rig 1 though.  As if the lower payouts arent enough now ive gotta deal with instability and loss of profit from all the crashes.  Changes are coming soon....at my house.

Since your rigs worked fine before you should check for any potential changes in your system (windows update, driver update, etc). Also recheck your PSU connectors and risers if everything is connected ok.

[dropky]

@apiontek Currently there is no plan to open-source the new protocol.

@tadeus1 We implemented a new mining protocol (NHMP - NiceHash Miner Protocol) that is used between our stratum servers and excavator.

[tadeus1]

Ooh the new version of excavator. Makes sense.
Thank you dropky.

[modus]

"If no parameters are provided, device specific defaults are used (M=1). We suggest using two workers per device when running equihash with mode 0*, otherwise use one worker per device.

* To manage intensity of this algorithm, we suggest you to run only one worker to reach low intensity and multiple (suggest 2) workers per device to reach optimal speed."

1 GTX 1080 GPU is the setup

from what i know p-0 is enabled by default , do i edit the  "default_command_file.json" and put 2 exactly like this

{"id":1,"method":"worker.add","params":["0","0"]},
{"id":1,"method":"worker.add","params":["0","0"]}

Does this command give the low intensity and the optimal speed?

Thank-you