CryptoDredge 0.8.0 — NVIDIA GPU Miner [obsolete]

[sabercrypto]

i cant make it work with nicehash. nonce too small

[cryptodredge]

Someone already tested these algorithms with a GTX 1080 Ti?

Here are results for GTX 1080Ti:

Code:

----------------------------------------------------------------------------------------------
          |       phi1612      |       neoscrypt     |       lyra2v2     |       skunk   
----------------------------------------------------------------------------------------------
Overclock | 0/0    | +130/-400 | 0/0      | 130/500  | 0/0      | 130/0  | 0/0      | 130/-400
----------------------------------------------------------------------------------------------
Hashrate  | 36MH/s | 38.6MH/s  | 1740KH/s | 1835Kh/s | 74.5MH/s | 78MH/s | 51.5MH/s | 54.5MH/s
----------------------------------------------------------------------------------------------

[infPICO]

Support in near future in Lyra2Z for 1060/1070/1080?

[MoNTE48]

Please, make linux build!

[cryptodredge]

Support in near future in Lyra2Z for 1060/1070/1080?

Yes, we'll add support for Lyra2Z in near future. Probably this will be added in version 0.5.

[cryptodredge]

Please, make linux build!

We completely understand how it is important to support Linux and this is a high priority task.

[cryptodredge]

v0.2.0 released

• New Allium algorithm
• Add watchdog
• Improve NeoScrypt for low-end graphics cards
• Other minor fixes

[preda]

im using this miner its simply the best!!!!

looking forward for lyra2z 1060!!!!!

[HashAuger]

Thank you for your hard work in releasing this new miner. As others have already said, it is a good start and has a lot of potential. Unfortunately, I may have found a small issue when using the --device parameter.  In version 0.2,  it is not possible to specify the first GPU using --device=0 or -d 0.  An error "bad lexical cast: type value could not be interpreted as target" is displayed and the executable quits.  However, this error does not occur if  --device=1 or -d 1 is used instead.

[sonkub]

Does this support API and --benchmark command?
Thanks!

[cryptodredge]

Thank you for your hard work in releasing this new miner. As others have already said, it is a good start and has a lot of potential. Unfortunately, I may have found a small issue when using the --device parameter.  In version 0.2,  it is not possible to specify the first GPU using --device=0.  An error "bad lexical cast: type value could not be interpreted as target" is displayed and the executable quits.  However, this error does not occur if -d 0 is used instead.  --device=1 will also work without an error, so the only problem appears to be when 0 is used with  --device.  It is a small issue, but one I thought you would like to be aware of.

It will be fixed in the next release

[cryptodredge]

Does this support API and --benchmark command?
Thanks!

--benchmark command will be available in the next release. API coming soon.

[HashAuger]

Thank you for your hard work in releasing this new miner. As others have already said, it is a good start and has a lot of potential. Unfortunately, I may have found a small issue when using the --device parameter.  In version 0.2,  it is not possible to specify the first GPU using --device=0.  An error "bad lexical cast: type value could not be interpreted as target" is displayed and the executable quits.  However, this error does not occur if -d 0 is used instead.  --device=1 will also work without an error, so the only problem appears to be when 0 is used with  --device.  It is a small issue, but one I thought you would like to be aware of.

It will be fixed in the next release

Thank you for the prompt reply.  After using your miner for a while, I do have a couple of feature requests. First, I noticed that it is not currently possible to redirect the screen output of your miner.  For example, if I try to redirect the standard console output to a log file, only your logo is written to the file but not the rest of the output. Would it be possible for you to either change how the screen output is handled so that it can be redirected or could you instead add a command line parameter that would write a file containing the screen output to disk?  Also, since color codes can make it more difficult to parse such log files, would you also consider adding a "no color" parameter to display the text in monochrome? 

[cryptodredge]

Thank you for the prompt reply.  After using your miner for a while, I do have a couple of feature requests. First, I noticed that it is not currently possible to redirect the screen output of your miner.  For example, if I try to redirect the standard console output to a log file, only your logo is written to the file but not the rest of the output. Would it be possible for you to either change how the screen output is handled so that it can be redirected or could you instead add a command line parameter that would write a file containing the screen output to disk?  Also, since color codes can make it more difficult to parse such log files, would you also consider adding a "no color" parameter to display the text in monochrome? 

Thank you for feedback.

Redirecting the console output to a file does not work as expected, this is a known issue. An additional command line arguments for redirecting log and suppressing color will be added in the next update.

[sonkub]

Does this support API and --benchmark command?
Thanks!

--benchmark command will be available in the next release. API coming soon.

Oh Thanks.

Last question.
Does --device can use more than 10? ^_^

[cryptodredge]

Does this support API and --benchmark command?
Thanks!

--benchmark command will be available in the next release. API coming soon.

Oh Thanks.

Last question.
Does --device can use more than 10? ^_^

Yes, it can. There is no limit for the number of devices.

[preda]

Does this support API and --benchmark command?
Thanks!

--benchmark command will be available in the next release. API coming soon.

Oh Thanks.

Last question.
Does --device can use more than 10? ^_^

Yes, it can. There is no limit for the number of devices.

compliments this miner is very fast!! i comparated to all ccminers out there this win against all

[eosdev]

https://www.virustotal.com/ru/file/701b580a7f07b6aaa52408fd3fba86ec079b399dfecf94a7278844cb73234789/analysis/1527967093/

[ghostlander]

I have tested your miner on neoscrypt algorithm with NVIDIA GTX1050TI 4GB with my default OC settings. Your miner looks like more stable and a little bit faster. I didnt checked the pool side. This informations are based on the miner reports.

I hope you will release Linux version. There is no any competitor for neoscrypt on Linux.

426.4 kh/s - CryptoDredge
422.7 kh/s - hsrminer fork of Just_a_miner - High process priority version

CUDAminer is still faster. Maybe except for 1080.

[cryptodredge]

v0.2.1 released

• Fix bug with NiceHash pool
• Improve Lyra2REv2

Download/Mirror