Here's the API for 1.4.4a and below, from the github history. See the 3rd paramenter to "algorithm.add" where it says "Username and password (split with "


Where does the Nicehash excavator team take donations? I don't think it's a donation-based miner. They're a proprietary, closed-playground project. Their funding is from Nicehash. If you want to pay them for their miner, just mine at Nicehash. In which case, you'd use the more recent 1.5+ versions. If you want to use 1.4.4a, they've clearly abandoned it and don't support it connecting to other pools, so I wouldn't worry about paying them for that lack of support.

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.

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.

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.)

I know nothing about it yet but I just had to tell Google that, yes, I did indeed mean "wavi coin" and it gave me the top result:

https://bitcointalk.org/index.php?topic=3146751.0

The error you're getting says the excavator api is unable to use port 3456 on your computer.

If you don't need to use the api, you can disable it with command line parameters as per https://github.com/nicehash/excavator#cmdline

So for example:


For me it works, and I use the api in my mining scripts. Controlling excavator works differently from other mining software but it's great once you understand it.

Again, if you don't need the api and it's a roadblock for you, just disable it. If you want to use it, try setting a different port. Maybe port 3456 is already in use on your machine, or you don't have permission to use it.

https://miningpoolhubstats.com/ does that. For non-MPH pools it just shows balance info, not worker status, but still.

I have my own software that does indeed monitor the miners and their connections and report accordingly. So, yes, I know what I'm talking about. Maybe don't presume when it comes to others' reported experiences.

I'm not experiencing this.

Somebody reports stratum problems on port 3636 only, other ports fine .... which is interesting since that's the new x16r algorithm which is itself new and unstable. I tried mining it here and there and it's pretty unstable even with no OC and reduced PL.

Maybe the stratum is also having instability for some reason?

Otherwise, no stratum issues at zergpool myself for the past few days.

You're not alone, several people have reported the same problem on their Windows computer, myself included.

Silence from dev. I wouldn't bother with bminer, dstm is more trustworthy and plenty fast.

New 5.3.0 still won't work on my two Windows 10 machines with GTX 1070s. No output, regardless of option provided or no option provided. And the lack of debugging info, advice, attention by the dev speaks volumes.

I don't really care anymore. It reports higher hashrates on my Linux machines, but given other people's experiences, I'm suspicious, so I won't use it there.

Amusingly, it does run on Win10 on an old laptop I have that's powering a GTX 970 via external expresscard adapter. But it reports a lower hashrate than dstm so.... there's no point there.

Agreed. My problem is different -- dies with no output on Windows -- but my experience & impression of the program author is the same. No useful troubleshooting questions asked, no useful troubleshooting information offered... just open source it and provide compile instructions, people can help you make your program better.

No output. When I run bminer.exe in cmd window, it just pauses, then goes back to the prompt. When I double-click it, an empty console window briefly appears, then disappears.

I do some very basic, minimal compiling on these machines, such as compiling xmrig & xmr-stak. So I have the CUDA SDK, and some .NET/VB libraries. Can you suggest specifics on which ones I might be missing?

Yes, I had tried disabling Windows Defender, despite it showing no indication that it cared about bminer.exe. Disabling Windows Defender had no effect.

If I double-click bminer.exe a cmd-style window appears for a couple seconds, then closes. It has no contents. There are no error messages or other outputs.

EDIT: same result with new 5.2.0 version.

Just tried again for fun -- still doesn't start for me on Windows 10. Not from batch file, nor on its own with any command arguments.

And that's with two different Windows 10 machines, one AMD Ryzen 7 1700, one intel i7 3770. Both with a GTX 1070.

Any way to debug this? I don't have anything strange running at the same time, as far as I can tell.

Trying out for the first time, using latest 5.1.0.

Runs on linux.

On Windows 10 amd64 there is no output for a couple seconds, then it ends. No error messages, nothing. Just a pause and a return to the command prompt. CPU is AMD Ryzen 7 1700, GPU is evga nvidia GTX 1070. I usually oc the GPU but I tried without any OC and it still just hangs for a couple seconds and quits with no output.

Very strange.

Seconded.

And/or, if you could make sure the output is unbuffered. I run my miners in a python script with subprocess.popen() and pipe stdout, which helps me watch for disconnects. This works with cli apps that don't buffer their output, and on linux, it works with everything since I can prepend "stdbuf -o0" to force unbuffered stdout ... but on Windows, the process just hangs until enough connection errors mount up to fill the buffer. Then I can catch the error and kill the program, but if it just had a control for # of retries, and/or didn't buffer stdout, I could use it.