CryptoDredge 0.27.0 — CUDA Miner

[CinErik]

next version with algo X16RT???   Crypto project Veil  

It's already out... CryptoDredge 0.15.2  

Hi;

Is it?



Kind regards

[1714968670]

1714968670

[1714968670]

1714968670

[1714968670]

1714968670

[1714968670]

1714968670

[1714968670]

1714968670

[1714968670]

1714968670

[joseph32]

You need the beta 

[tbearhere]

next version with algo X16RT???   Crypto project Veil  

It's already out... CryptoDredge 0.15.2  

Hi;

Is is?



Kind regards

No... I thought it was for X16RT. But not. I get the same thing as you. X16RT algo not supported.
I can't find the beta either on discord.

[CinErik]

You need the beta 

Hi;

I think so but beta version was not in the github or bitcointalk.

Kind regards

[cost82el]

https://nemosminer.com/data/optional/0.16.0-beta.7z

[cryptodredge]

v0.16.0 released

• Add X16RT algorithm
• Add Lyra2zz (LAPO) algorithm
• Stabilize MTP algorithm
• Other minor fixes

Download
Mirror

Happy mining!
The CryptoDredge Team 👾

[duboisi]

Is the HMQ1725 problem fixed?

[Xazax310]

@ CryptoDredge team. Will you be doing/supporting ProgPOW mining?

[topteam]

back to beta, more stable on x16rt (linux version)

[rottongg]

Hi! MTP algo, xzc.2miners.com,  I got problem with high amount of rejected shares, from 15% rejecrts , up to 50% rejects sometime.

https://i.ibb.co/RywqhRG/sharerr.jpg


tested with standard gpu clocks, same sh1t

ping is okay

C:\Users\start>ping xzc.2miners.com
Pinging xzc.2miners.com [54.36.109.3] with 32 bytes of data:
Reply from 54.36.109.3: bytes=32 time=83ms TTL=47
Reply from 54.36.109.3: bytes=32 time=79ms TTL=47
Reply from 54.36.109.3: bytes=32 time=87ms TTL=47
Reply from 54.36.109.3: bytes=32 time=78ms TTL=47
Ping statistics for 54.36.109.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 78ms, Maximum = 87ms, Average = 81ms

please help.

[gusknure]

Version 1.16.0 6x1080ti miner still unstable.
It's crashed after hour or so.

[topteam]

Hi! MTP algo, xzc.2miners.com,  I got problem with high amount of rejected shares, from 15% rejecrts , up to 50% rejects sometime.

https://i.ibb.co/RywqhRG/sharerr.jpg


tested with standard gpu clocks, same sh1t

ping is okay

C:\Users\start>ping xzc.2miners.com
Pinging xzc.2miners.com [54.36.109.3] with 32 bytes of data:
Reply from 54.36.109.3: bytes=32 time=83ms TTL=47
Reply from 54.36.109.3: bytes=32 time=79ms TTL=47
Reply from 54.36.109.3: bytes=32 time=87ms TTL=47
Reply from 54.36.109.3: bytes=32 time=78ms TTL=47
Ping statistics for 54.36.109.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 78ms, Maximum = 87ms, Average = 81ms

please help.

try mintpond, with d=1000
the is no reject

[rottongg]

just right now

00:39:13] INFO  - Block height 125221 : Network difficulty 3967.44
[00:39:13] INFO  - Received new job #caae0372
[00:39:14] INFO  - GPU1: scratchpad is generated. 1.33318 sec
[00:39:14] INFO  - GPU2: scratchpad is generated. 1.335 sec
[00:39:15] INFO  - GPU0: scratchpad is generated. 1.34264 sec
[00:39:15] INFO  - GPU3: scratchpad is generated. 1.36243 sec
[00:39:19] INFO  - 43/5 Rejected : diff=0.139618
[00:39:26] INFO  - 43/6 Rejected : diff=0.109136
[00:39:38] INFO  - 43/7 Rejected : diff=0.126251
[00:39:39] INFO  - 43/8 Rejected : diff=0.205534
[00:39:41] INFO  - 43/9 Rejected : diff=0.0855291
[00:39:43] INFO  - 43/10 Rejected : diff=0.0868552
[00:39:45] INFO  - 43/11 Rejected : diff=2.439
[00:39:47] INFO  - 43/12 Rejected : diff=0.144709
[00:39:51] INFO  - 43/13 Rejected : diff=0.0819594
[00:39:54] INFO  - 43/14 Rejected : diff=0.248867
[00:39:56] INFO  - 43/15 Rejected : diff=0.082801
[00:39:59] INFO  - 43/16 Rejected : diff=0.0797819
[00:40:01] INFO  - 44/16 Accepted : diff=0.11192 : 13.16MH/s
[00:40:06] INFO  - 45/16 Accepted : diff=0.160867 : 13.16MH/s
[00:40:27] INFO  - 46/16 Accepted : diff=0.0907441 : 13.17MH/s
[00:40:32] INFO  - GPU0 Gigabyte GTX 1080 Ti : 3445KH/s (Avr 3276KH/s) : 14.71KH/W : T=50C Fan=100%
[00:40:32] INFO  - GPU1 Gigabyte GTX 1080 Ti : 3458KH/s (Avr 3276KH/s) : 14.76KH/W : T=52C Fan=100%
[00:40:32] INFO  - GPU2 Gigabyte GTX 1080 Ti : 3515KH/s (Avr 3335KH/s) : 15.02KH/W : T=47C Fan=79%
[00:40:32] INFO  - GPU3 Colorful GTX 1080 Ti : 3459KH/s (Avr 3283KH/s) : 14.15KH/W : T=54C Fan=100%

[gusknure]

GPU2 Gigabyte GTX 1080 Ti : 3515KH/s

How you get this hashrate?
What clock are you using?

[CarlOrff]

GPU2 Gigabyte GTX 1080 Ti : 3515KH/s

How you get this hashrate?
What clock are you using?

He said : no overclock.
It is standard values for standards clocks with 108OTi.

In my side the new version is working fine sine the avaibility of the software : no crashe, but no hashrate increase (just one 1080Ti).

[Juniormkl]

CryptoDredge 0.16.0 (Windows/Linux) added to https://www.minermonitoring.com/



Join our discord https://discord.gg/aGGaeqq



also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark

[Kompik]

Thanks for adding lapo, been waiting for some good miner for this coin

[gusknure]

Version 1.16.0 freezing PC, need to reboot manually by power.

[stzcze]

I have the same experience.

[rottongg]

ALGO MTP

GPU2 Gigabyte GTX 1080 Ti : 3515KH/s

How you get this hashrate?
What clock are you using?

In this case it was overclocked +167 mhz for gpu. memory not overclocked.
power = 90%

BUT also I made tests with no overclocking, there is no relations between gpu clock and rejects -TESTED

I think that it is only problem of communicating between miner Cryptodredge and server xzc.2miners.com
 ( by the way - Cryptodredge is fast and cool - no reboots for 15 hours for now and no bugs )

[15:02:38] INFO  - GPU2 Gigabyte GTX 1080 Ti : 3525KH/s (Avr 3401KH/s) : 15.41KH/W : T=47C Fan=79%

but i think that I get this hashrate only because of low temperature  T=47C I think it is extremely low )

here what water block do
[15:00:04] INFO  - GPU1 Gigabyte GTX 1080 Ti : 3681KH/s (Avr 3585KH/s) : 14.50KH/W : T=27C  (gpu +185 mhz, mem 0, power =100%)

when temperature goes up hash rate goes down. (tested)

When summer was, and +30C behind the window, I had to go to low power 50-60 % to keep temperature 60-65C, hash rate was very lack

(by the way, just tested with no overclocking , gpu 0 mem 0 power 90% [16:04:38] INFO  - GPU2 Gigabyte GTX 1080 Ti : 3471KH/s (Avr 3399KH/s) : 15.39KH/W : T=47C Fan=79% )