TT-Miner 2024.1.2 BLAKE3, KAWPOW, ETHASH, ETCHASH, EPIC, SHA512256D, SHA3D, ETI

[TrailingStop]

Version 2.1.12 is available.

  - fixes a bug that could cause rejected shares under certain conditions. If you see an unusual high number of rejected shares this version should fix this and reduce the number of rejected shares. This happened sometimes after DevFee mining.


Note for xzc mining on Nicehash: Please make sure that you do not have -RH or -rate on your command line. Nicehash doesn't not like hashrate reporting and will disconnect if this notification is sent.

Note for xzc mining on f2pool: The first job @ f2pool is '0' and for TT-Miner a Job-ID of 0 is invalid. So it will not start mining until the next job from f2pool is received - which can take a minute or two.


Download link:
https://TradeProject.de/download/Miner/TT-Miner.zip

Let me know if you have any issues or questions,
Happy mining.

can u support amd card?

Hi - at the moment I work on a new algo and a Linux release. Maybe after that I can look into AMD stuff if there is need.

[ayiphelmy]

Version 2.1.12 is available.

  - fixes a bug that could cause rejected shares under certain conditions. If you see an unusual high number of rejected shares this version should fix this and reduce the number of rejected shares. This happened sometimes after DevFee mining.


Note for xzc mining on Nicehash: Please make sure that you do not have -RH or -rate on your command line. Nicehash doesn't not like hashrate reporting and will disconnect if this notification is sent.

Note for xzc mining on f2pool: The first job @ f2pool is '0' and for TT-Miner a Job-ID of 0 is invalid. So it will not start mining until the next job from f2pool is received - which can take a minute or two.


Download link:
https://TradeProject.de/download/Miner/TT-Miner.zip

Let me know if you have any issues or questions,
Happy mining.

can u support amd card?

Hi - at the moment I work on a new algo and a Linux release. Maybe after that I can look into AMD stuff if there is need.

ok nice! Keep the good job!!

[topteam]

waiting for linux release

[theplayernkc]

Just started using this as this newer version mines MTP on NiceHash now. The current uptime at the time of this post is 4 hours 15 min, but I'm getting a lot of "share above target". I'm running it on two cards right now, a GTX 1060 and GTX 1070. The GTX 1060 is showing 8.8% and the 1070 is showing 14.1% in the miner window. I assume that the % numbers is for the "share above target" percentage. Just thought you should know what I'm getting from your miner and if I'm correct, the "share above target" % is quite high and then count in the 1% devfee.

Hi,

yes, these values seem way too high. The % number is the percentage of rejected shares in relation to all submitted shares. No matter why they have been rejected. Can you please reduce your OC and try again? How are the numbers if you use an other miner?

Hello,

There is only one other miner that I know of that is compatible with NiceHash running the MTP algo. It's Bminer and it's horrible, constantly get "GPU1: Result for XXXXXXX does not validate on CPU" all the time even with no oc on the cards. It's so bad that it's unusable.

Around 3 hours and 30 min ago miner on my GTX 1060 6GB got the following error.

Miner: Error ******** GPU[1] CudaError: 700
Miner: Error ******** GPU[1] Not enough memory to run algo. GPU disabled. (0/1)
Miner: Error ******** GPU[1] Maybe your Virtual Memory is set too low - please check.
Miner: Error ******** GPU[1] All GPUs are disabled. TT-Miner cannot continue and will exit now

However your miner just restarted and started mining on the GTX 1060 6GB like normal. I have my Virtual Memory set to 64GB.
I will lower the clock speeds and see if that helps with the "share above target" issue and report back.

Thank you.

[TrailingStop]

Just started using this as this newer version mines MTP on NiceHash now. The current uptime at the time of this post is 4 hours 15 min, but I'm getting a lot of "share above target". I'm running it on two cards right now, a GTX 1060 and GTX 1070. The GTX 1060 is showing 8.8% and the 1070 is showing 14.1% in the miner window. I assume that the % numbers is for the "share above target" percentage. Just thought you should know what I'm getting from your miner and if I'm correct, the "share above target" % is quite high and then count in the 1% devfee.

Hi,

yes, these values seem way too high. The % number is the percentage of rejected shares in relation to all submitted shares. No matter why they have been rejected. Can you please reduce your OC and try again? How are the numbers if you use an other miner?

Hello,

There is only one other miner that I know of that is compatible with NiceHash running the MTP algo. It's Bminer and it's horrible, constantly get "GPU1: Result for XXXXXXX does not validate on CPU" all the time even with no oc on the cards. It's so bad that it's unusable.

Around 3 hours and 30 min ago miner on my GTX 1060 6GB got the following error.

Miner: Error ******** GPU[1] CudaError: 700
Miner: Error ******** GPU[1] Not enough memory to run algo. GPU disabled. (0/1)
Miner: Error ******** GPU[1] Maybe your Virtual Memory is set too low - please check.
Miner: Error ******** GPU[1] All GPUs are disabled. TT-Miner cannot continue and will exit now

However your miner just restarted and started mining on the GTX 1060 6GB like normal. I have my Virtual Memory set to 64GB.
I will lower the clock speeds and see if that helps with the "share above target" issue and report back.

Thank you.

OK. You can roughly say that you need 4.5 GB virtual memory per gpu. The error message (700) indicated that the algo accesses an invalid memory address. Memorysize is OK. Reducing clock speed is a good appoarch to identify the problem. I would set all OC setting to 0. If that works stable I would OC. You will see that not all settings have impact to MTP.

Thanks for keeping me updated.

[chrysophylax]

Any chance of a Linux based miner soon? ...

Debian and Fedora functional one? We are willing to do a deal for one just to test these Algos out.

#crysx

[TrailingStop]

Any chance of a Linux based miner soon? ...

Debian and Fedora functional one? We are willing to do a deal for one just to test these Algos out.

#crysx

Will take some days from now - working hard on it. I develop using Ubuntu, hope that is still OK for you?

[rednoW]

There is only one other miner that I know of that is compatible with NiceHash running the MTP algo. It's Bminer and it's horrible, constantly get "GPU1: Result for XXXXXXX does not validate on CPU" all the time even with no oc on the cards. It's so bad that it's unusable.

I don't see mtp in list of bminer supported algos. Why? ))

[theplayernkc]

There is only one other miner that I know of that is compatible with NiceHash running the MTP algo. It's Bminer and it's horrible, constantly get "GPU1: Result for XXXXXXX does not validate on CPU" all the time even with no oc on the cards. It's so bad that it's unusable.

I don't see mtp in list of bminer supported algos. Why? ))

My bad, it's ccminer by djm34.

[chrysophylax]

Any chance of a Linux based miner soon? ...

Debian and Fedora functional one? We are willing to do a deal for one just to test these Algos out.

#crysx

Will take some days from now - working hard on it. I develop using Ubuntu, hope that is still OK for you?

If it is a static compile ...

That should be OK, as it will work similar to TRex and GMiner do, where the dependencies are actually contained IN the binary itself. Otherwise there will be dependency issues, version issues or both.

If it can't be done, then we will have to find another that can, or we could do a deal for an internal miner. Either way, it would be good if it just 'worked' and optimization always comes later anyway. Especially when working on the NiceHash stratums.

#crysx

[theplayernkc]

Hello,

There is only one other miner that I know of that is compatible with NiceHash running the MTP algo. It's Bminer and it's horrible, constantly get "GPU1: Result for XXXXXXX does not validate on CPU" all the time even with no oc on the cards. It's so bad that it's unusable.

Around 3 hours and 30 min ago miner on my GTX 1060 6GB got the following error.

Miner: Error ******** GPU[1] CudaError: 700
Miner: Error ******** GPU[1] Not enough memory to run algo. GPU disabled. (0/1)
Miner: Error ******** GPU[1] Maybe your Virtual Memory is set too low - please check.
Miner: Error ******** GPU[1] All GPUs are disabled. TT-Miner cannot continue and will exit now

However your miner just restarted and started mining on the GTX 1060 6GB like normal. I have my Virtual Memory set to 64GB.
I will lower the clock speeds and see if that helps with the "share above target" issue and report back.

Thank you.

OK. You can roughly say that you need 4.5 GB virtual memory per gpu. The error message (700) indicated that the algo accesses an invalid memory address. Memorysize is OK. Reducing clock speed is a good appoarch to identify the problem. I would set all OC setting to 0. If that works stable I would OC. You will see that not all settings have impact to MTP.

Thanks for keeping me updated.

Here are the results of 4 hours and 15 min like my previous post. The cards are running at stock clock speeds. The GTX 1060 is getting 5.5% "share above target" and the GTX 1070 is getting 4.4% "share above target".

https://i.postimg.cc/65ShMhG3/gtx1060a.jpg
https://i.postimg.cc/yxxFPJ1c/gtx1070.jpg

[TrailingStop]

Hello,

There is only one other miner that I know of that is compatible with NiceHash running the MTP algo. It's Bminer and it's horrible, constantly get "GPU1: Result for XXXXXXX does not validate on CPU" all the time even with no oc on the cards. It's so bad that it's unusable.

Around 3 hours and 30 min ago miner on my GTX 1060 6GB got the following error.

Miner: Error ******** GPU[1] CudaError: 700
Miner: Error ******** GPU[1] Not enough memory to run algo. GPU disabled. (0/1)
Miner: Error ******** GPU[1] Maybe your Virtual Memory is set too low - please check.
Miner: Error ******** GPU[1] All GPUs are disabled. TT-Miner cannot continue and will exit now

However your miner just restarted and started mining on the GTX 1060 6GB like normal. I have my Virtual Memory set to 64GB.
I will lower the clock speeds and see if that helps with the "share above target" issue and report back.

Thank you.

OK. You can roughly say that you need 4.5 GB virtual memory per gpu. The error message (700) indicated that the algo accesses an invalid memory address. Memorysize is OK. Reducing clock speed is a good appoarch to identify the problem. I would set all OC setting to 0. If that works stable I would OC. You will see that not all settings have impact to MTP.

Thanks for keeping me updated.

Here are the results of 4 hours and 15 min like my previous post. The cards are running at stock clock speeds. The GTX 1060 is getting 5.5% "share above target" and the GTX 1070 is getting 4.4% "share above target".

Hi,

thanks for your feedback. I try to avoid more rejections, but at the moment your rejected rate is within expectation.

Please let me know if you nocetice some other bug or have any suggestions.

Thanks for reporting.

[theplayernkc]

Hi,

thanks for your feedback. I try to avoid more rejections, but at the moment your rejected rate is within expectation.

Please let me know if you nocetice some other bug or have any suggestions.

Thanks for reporting.

Appreciate you looking at my results. I'll check back to see if you come out with a new version that will lower the "share above target" issue.

Right now I'm getting a better return on Grin and Beam versus the high "share above target" percentage I'm currently getting with your miner.

Thank you.

[TrailingStop]

Hi,

thanks for your feedback. I try to avoid more rejections, but at the moment your rejected rate is within expectation.

Please let me know if you nocetice some other bug or have any suggestions.

Thanks for reporting.

Appreciate you looking at my results. I'll check back to see if you come out with a new version that will lower the "share above target" issue.

Right now I'm getting a better return on Grin and Beam versus the high "share above target" percentage I'm currently getting with your miner.

Thank you.

You're welcome - and thanks again for posting your findings.

[birdjan]

can you add support for yescrypt-koto coin?

[birdjan]

for koto at the moment there is only ccminerKlaust-mod,for nvidia_gtx1070 9 kh on 50%tdp. for amd - sgminer koto, but very slow- 600h.can you improve this hashrates with your versions? thanks

[TrailingStop]

New version 2.1.13

  - added support for cuda 10.1
  - fixes a bug in ETHASH that might come up after several epoch switches
  - miner will now check and inform about a new version once a day on program-start

In this version the miner support cuda 9.2, 10.0 and 10.1.If you want to make sure that TT-Miner uses a certain cuda version please append one of these values. If you do not append any of them, the miner will always use the algo for the latest cuda version:

   -92      for cuda 9.20   (ETHASH-92, UBQHASH-92)
   -100      for cuda 10.00   (ETHASH-100, PROGPOW-100)
   -101      for cuda 10.10   (ETHASH-101, MTP-101)

Please note these requirements for the different cuda toolkit releases:
Cuda-Toolkit      Windows      Linux
CUDA 10.1.105      >= 418.39      >= 418.96
CUDA 10.0.130      >= 410.48      >= 411.31
CUDA 9.2.148      >= 396.37      >= 398.26

Please report any issues.
Thanks.

[BrucoMining]

New version 2.1.13

  - added support for cuda 10.1
  - fixes a bug in ETHASH that might come up after several epoch switches
  - miner will now check and inform about a new version once a day on program-start

In this version the miner support cuda 9.2, 10.0 and 10.1.If you want to make sure that TT-Miner uses a certain cuda version please append one of these values. If you do not append any of them, the miner will always use the algo for the latest cuda version:

   -92      for cuda 9.20   (ETHASH-92, UBQHASH-92)
   -100      for cuda 10.00   (ETHASH-100, PROGPOW-100)
   -101      for cuda 10.10   (ETHASH-101, MTP-101)

Please note these requirements for the different cuda toolkit releases:
Cuda-Toolkit      Windows      Linux
CUDA 10.1.105      >= 418.39      >= 418.96
CUDA 10.0.130      >= 410.48      >= 411.31
CUDA 9.2.148      >= 396.37      >= 398.26

Please report any issues.
Thanks.

Hi,
with 2.1.13 all my shares are being rejected on NiceHash, this is the error:
POOL: Error - Invalid job id size

[TrailingStop]

New version 2.1.13

  - added support for cuda 10.1
  - fixes a bug in ETHASH that might come up after several epoch switches
  - miner will now check and inform about a new version once a day on program-start

In this version the miner support cuda 9.2, 10.0 and 10.1.If you want to make sure that TT-Miner uses a certain cuda version please append one of these values. If you do not append any of them, the miner will always use the algo for the latest cuda version:

   -92      for cuda 9.20   (ETHASH-92, UBQHASH-92)
   -100      for cuda 10.00   (ETHASH-100, PROGPOW-100)
   -101      for cuda 10.10   (ETHASH-101, MTP-101)

Please note these requirements for the different cuda toolkit releases:
Cuda-Toolkit      Windows      Linux
CUDA 10.1.105      >= 418.39      >= 418.96
CUDA 10.0.130      >= 410.48      >= 411.31
CUDA 9.2.148      >= 396.37      >= 398.26

Please report any issues.
Thanks.

Hi,
with 2.1.13 all my shares are being rejected on NiceHash, this is the error:
POOL: Error - Invalid job id size

Hi,

please reload the miner. I made a mistake with the very first upload of the 2.1.13 - sorry. Please let me know if you still get the rejection.

Thanks.

[TrailingStop]

Released new version 2.1.14

   - added Lyra2Rev3 algo (Vertcoin)
   - added support for Nicehash / Lyra2Rev3
   - added support for non-numberic job-ids (f2pool.com)
   - works now with job-id = 0 (first job at f2pool.com)

Please report bugs and issues.

Thanks - and happy mining.