Quote from: stevej on February 13, 2018, 08:49:21 AM

Quote from: dropky on February 13, 2018, 08:34:43 AM

Quote from: stevej on February 12, 2018, 07:00:58 PM

Quote from: dropky on February 12, 2018, 07:42:21 AM

As mentioned before we dropped the daggerhashimoto for 3gb cards because there were a lot of issues/crashes with it among NHM users (especially on primary cards). We could remove the 3gb condition in excavator though, and you can run it without NHM then..

Ok, then I could use it for external mining ?

What do you mean by external mining? You could mine to NH pool just not by using NHM. I'll keep you updated on this.

Yes, thats what I meant, external mining to nicehash without NMH

I took a look at daggerhashimoto and excavator already supports it on 3GB cards (we've never put the 3GB condition to excavator, it was only added to NHM).

Here is an example of config file for running dagger on one card:

Code:

[
{"time":0,"commands":[
{"id":1,"method":"algorithm.add","params":["daggerhashimoto","daggerhashimoto.eu.nicehash.com:3353","your_btc"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","0"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"algorithm.print.speeds","params":[]}
]}
]

To run it on 2 cards you just have to add another worker.add method, like this:

Code:

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

First parameter represents the algorithm id, the second one is device id - 0, 1...
Take a look here: https://github.com/nicehash/excavator/tree/master/api#worker-add

You have to run excavator with -c config.json parameter.