CryptoDredge 0.26.0 — NVIDIA GPU Miner

[JayDDee]

       Also have this error on ver 23 mtp-tcr.

Stale shares can't be complety avoided, there will alway be a window where a submitted share or 2 can overlap with a
new job. High network latency and low hashrate algos (longer time/thread to calculate 1 hash) make stales more likely.
In this case it looks like it may be related to the fee switch (something I have no experience with).

[1618590381]

1618590381

[1618590381]

1618590381

[1618590381]

1618590381

[1618590381]

1618590381

[JayDDee]

I've had a chance to run this over my rig and it'll work on all old and modern Nvidia cards except for the 1650 Super.  It only gives a GPU Critical Error message and restarts the miner.  Works fine on all other cards ranging from a 750 ti, 1050ti, 1660ti, 1070 and RTX 2080.  Just the 1650 Super fails. 

Since this GPU is still relatively new, has it not been coded for yet?  I am currently running the latest version 23.0

Update driver?

[tbearhere]

       Also have this error on ver 23 mtp-tcr.

Stale shares can't be complety avoided, there will alway be a window where a submitted share or 2 can overlap with a
new job. High network latency and low hashrate algos (longer time/thread to calculate 1 hash) make stales more likely.
In this case it looks like it may be related to the fee switch (something I have no experience with).

It seems it is related to the fee switch. Never happens with older versions.

Also if we update drivers the cpu will run at 100% load.

[mstrozier]

I've had a chance to run this over my rig and it'll work on all old and modern Nvidia cards except for the 1650 Super.  It only gives a GPU Critical Error message and restarts the miner.  Works fine on all other cards ranging from a 750 ti, 1050ti, 1660ti, 1070 and RTX 2080.  Just the 1650 Super fails. 

Since this GPU is still relatively new, has it not been coded for yet?  I am currently running the latest version 23.0

Update driver?

I was at 441 on the nvidia driver.  Updated to 442.74  and same issue.  Does not hash and states critical issue and restarts the miner.   I can use this card on any other mining software, claymore 15 on coins that'll allow due to dag size (callisto, Ether-1 as examples) without any problem.  I can use T-Rex on Ravencoin again no problem.  Card works great.  However if I use Cryptodredge it'll bomb out every time.  So now with everything updated just leads me to thinking something in the mining software.  Since the 1650 Super is fairly new and not many people using the card.

[JayDDee]

I was at 441 on the nvidia driver.  Updated to 442.74  and same issue.  Does not hash and states critical issue and restarts the miner.   I can use this card on any other mining software, claymore 15 on coins that'll allow due to dag size (callisto, Ether-1 as examples) without any problem.  I can use T-Rex on Ravencoin again no problem.  Card works great.  However if I use Cryptodredge it'll bomb out every time.  So now with everything updated just leads me to thinking something in the mining software.  Since the 1650 Super is fairly new and not many people using the card.

Could be a tuning issue. Does Cryptodredge have an intensity option like ccminer? Try lowering it until the SW is updated to
properly tune for that card.

[mstrozier]

I was at 441 on the nvidia driver.  Updated to 442.74  and same issue.  Does not hash and states critical issue and restarts the miner.   I can use this card on any other mining software, claymore 15 on coins that'll allow due to dag size (callisto, Ether-1 as examples) without any problem.  I can use T-Rex on Ravencoin again no problem.  Card works great.  However if I use Cryptodredge it'll bomb out every time.  So now with everything updated just leads me to thinking something in the mining software.  Since the 1650 Super is fairly new and not many people using the card.

Could be a tuning issue. Does Cryptodredge have an intensity option like ccminer? Try lowering it until the SW is updated to
properly tune for that card.

Thanks, didn't think about the tuning.  That did the trick.  It fails on 6 however 5 and below it works great.   Appreciate it.

[Eketubol]

Is there any reason why MTP is still at 2% fee? I would probably use CryptoDredge if the miner outperforms its competitors but at the moment T-rex Miner works better on MTP for less fee. Can you please update the fee to reflect the current mining climate.

[ZeeeN]

Is there any reason why MTP is still at 2% fee? I would probably use CryptoDredge if the miner outperforms its competitors but at the moment T-rex Miner works better on MTP for less fee. Can you please update the fee to reflect the current mining climate.

for MTP you can use ccminer with same speed

[igotek]

2020-07-20Announce Haven hardfork succeeded successfully.
We now have two different payment systems. XHV and xUSD.
You can set minimum payment amounts here.
Please do not forget to update miners and wallet.
2020-07-15AnnounceHaven launching xUSD on July 20th.
Miner algo stays the same cn-heavy/xhv but need to update will be required.
Please do not forget to update miners and wallet.
You can find all working miners here.


Any update for XHV ?

[cryptoyes]

Haven already forked. Any updated version to support it?

[coinminery]

https://prnt.sc/tqfgvq
https://prnt.sc/tqfgvq

[cryptodredge]

v0.24.0 released

• Improve Nimiq algorithm
• Add -q, --recompute option to set memory reduction factor (1 - 32) (Nimiq only). For example: -q N[,N] (default: 23)
• Fix high CPU usage on MTP-like, Argon2-like and CryptoNight-like algorithms
• Slightly improve Chukwa (Argon2-512) and Ninja (Argon2-256) algorithms
• MTP: Fix memory leaks
• New CryptoNightTLO algorithm
• Fix CryptoNightHaven issue related to 'Unsupported blob size'
• New Sha256csm algorithm
• Add --sni option to enable SNI (Server Name Indication) for the pool connection
• Other minor fixes

Download: https://github.com/technobyl/CryptoDredge/releases/tag/v0.24.0

Example:

Code:

CryptoDredge -a argon2d-nim -o wss://nimiq.icemining.ca:2053 -u "NQ68 XM08 9BE8 57DE QMT6 PAT5 PJGQ TEBX FSBU" -p "My Miner" -q 21

Happy mining!

[tbearhere]

Intensity settings aren't working or should I say - i 0 still isn't low enough to mine and use my computer too. This also happens in v0.23.0 release too. Windows 8.1

[mirny]

v0.24.0 released

• Improve Nimiq algorithm
• Add -q, --recompute option to set memory reduction factor (1 - 32) (Nimiq only). For example: -q N[,N] (default: 23)
• Fix high CPU usage on MTP-like, Argon2-like and CryptoNight-like algorithms
• Slightly improve Chukwa (Argon2-512) and Ninja (Argon2-256) algorithms
• MTP: Fix memory leaks
• New CryptoNightTLO algorithm
• Fix CryptoNightHaven issue related to 'Unsupported blob size'
• New Sha256csm algorithm
• Add --sni option to enable SNI (Server Name Indication) for the pool connection
• Other minor fixes

Download: https://github.com/technobyl/CryptoDredge/releases/tag/v0.24.0

Example:

Code:

CryptoDredge -a argon2d-nim -o wss://nimiq.icemining.ca:2053 -u "NQ68 XM08 9BE8 57DE QMT6 PAT5 PJGQ TEBX FSBU" -p "My Miner" -q 21

Happy mining!

Hi, could you please compile binary for cuda 9.1(linux)?
cheers

[arielbit]

MTP latest nvidia drivers.

windows 7 ~3MH
windows10 ~4MH

[cryptodredge]

v0.25.1 released

• Fix high CPU usage on MTP when 'Received new job'

v0.25.0 released

• Improve MTP algorithm
• Improve Argon2d (NIM) algorithm
• Add optimizer (Argon2d (NIM) only). Check Readme for more information
• Allow floating-point intensity (e.g. -i 6.5)
• Fix CryptoNight issue related to 'the launch timed out and was terminated'
• Remove --recompute option
• Remove obsolete algorithms
• Other minor fixes

Download: https://github.com/technobyl/CryptoDredge/releases/tag/v0.25.1

Happy mining!

[alucard20724]

v0.25.1 released

• Remove obsolete algorithms

Which algorithms were removed that are considered obsolete?

[UselessGuru]

v0.25.1 released

• Remove obsolete algorithms

Which algorithms were removed that are considered obsolete?

I'd like to know too

[tbearhere]

v0.25.1 released

• Remove obsolete algorithms

Which algorithms were removed that are considered obsolete?

I'd like to know too

      I'd like to know too.  

[tbearhere]

    -i 0 is still to intensive ...... bogging down my personal computer. On my rig it's ok.