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

[TrailingStop]

Thanks for the information. I will release a newer version later today or tomorrow. That comes with an automatic optimization that will find the best cuda settings for each GPU and the applied coin/pool configuration. This process might take almost an hour because the miner have to wait for stable hash rates befor it continues to test the next settings-combination (and there are really a lot of them). Once the optimal settings are found the Miner stores them. This profile contains information about the Graphic interface and the pool/coin configuration so that it can be reused whenever this combination is mining again - no matter in which rig the interface is. Today I optimized the cuda settings for the interface I have available, but they are certain not oiptimal for others.

[TrailingStop]

New release is available.

new in build 17:
- new information window in the MinerControl - open it with a doubleclick on a GPU

- you can now configure how the nonces will be generated, your options are:

    - start with zero and continue to count up

    - reset the nonce to zero on every new job

    - use a random nonce for each iteration

    - create a random nonce and count up on each new job

    - create a random nonce on a new job and if the miner do not find a solution within the timeout. You can setup the timeout in 10th of a second.

[Metroid]

DevFee
The DevFee is 1 minute for 1-hour mining - that is about 1.7%

Your devfee is extremely high, have you ever heard of competition? This is not a good way of getting people to try your miner.

PhoenixMiner has a developer fee of 0.65%, if you want people to try it out then your devfee should be much lower than PhoenixMiner.

[TrailingStop]

fair point. I will reduce it in one of the next releases. Anyway the miner wait until it collects 3 minutes for the dev (me) - so you have no risk to pay me in the first 3 hours.

On the other hand I do not think that it is much of a difference if I get 1.7 or 1% - looking at the variance of the hashrate at the pool. Also I see some hashrates improvements here on my rigs (for ProgPoW and Ethash). If the miner isn't faster than others people will not use it anyway.


But your point is OK and fair. Next release will have 1% only.

[TrailingStop]

Done. New version is available with 1% dev fee only
Enjoy - any happy mining!

[TrailingStop]

TradeTec-Miner 18.10.40.18 released.

New reduced DevFee of 1 %.
Fixed an issue when adding a new pool/coin configuration
Performance improvement for Ethash

[TrailingStop]

TradeTec-Miner 18.10.40.20 released.


- fixes a bug when you quickly change the pools a GPU should mine to. Miner became unresponsive for some seconds.
- Improvements to ProgPoW - hope they will show on 2080 as well

[TrailingStop]

Hi ol92,

if you're around could you please run a quick test with the latest miner and let me know if the hashrates for the 2080 are better than the rates you got with the last miner?

Thx!

[TrailingStop]

I noticed that I do get good hashrates @ bci.coinblockers.com for BCI ProgPoW with this settings for the hashrate generation. The miner will create a new random nonce when a new job comes in, or the timeout expires. I get good results with a timeout of 7.5 sec on the pools I use.

[ol92]

Hi ol92,

if you're around could you please run a quick test with the latest miner and let me know if the hashrates for the 2080 are better than the rates you got with the last miner?

Thx!

Hello,

tested yesterday : the new miner has almost the same performance as the first one: around 23 Mh/s at 85% powerlimit. The first one was a little bit better (around 23.5). Others were worse (21-22).
I will test more this afternoon.

[TrailingStop]

Thanks a lot. Please keep in mind that it might take up to 20 minutes until a stable hashrate is available.

Thanks!!

[dragonmike]

Nice features... but out of the box the miner is a little slower than the original ProgPow miner provided by the BCI devs (approx 3.5%) on my rig of 1080's.

Also, no idea how to tweak the timeout values... What should I be looking at?

[TrailingStop]

Hi dragonmike,

Unfortunately I do not have a 1080 available for development, but I'm working on improvement for the 1080 with some miner. I have just released a new version that should address this issue. Maybe you want to give the new release a try and see if that works better on your rig. I release the TTminer as CUDA 9.20 and as CUDA 10.0 version. Please try the one you haven't. I have better results on my 1070 rigs with the CUDA 9.20 release - but that my differ from system to system. Cuda 10 required driver 411 or later.

Do you use the UI or the command line version? If you use command line please try the same options you use for the ProgPoWminer.

If you run the miner you can see in which frequency it finds and submits shares. I noticed that there are sometime 'areas' in the nonce that shows more shares than others. Also there are  areas where the miner do not find any share at all. If you think that the miner should change the area where it tries to find share after 10 seconds of searching without success then you should use 100 for timeout. You can think of this options as you are searching for gold. If you do not find any gold at one place you try a different location after some time. That is the same idea. You enter the timeout in tenth of a second. So 10 is one second, 100 is 10 seconds.

Let me know if the new release brings any improvement for you.

Thanks.

[dragonmike]

Hah, ok will have to look into it a bit further then.

I'm using the gui version (as you described in the original post). I'm on latest driver and Cuda10.
Also I'd like to report that the miner crashed overnight (and/or closed itself). Was using same clocks/voltages/PL than with the original ProgPow miner.

Keep us posted on any updates.

PS: can I add any parameters if I use the gui version anywhere?

[TrailingStop]

Hi Dragonmike,

will do. Until the end of this week I have only access to a limited development environment without GPU. So I cannot test. I will look into the crash as soon as I'm back. Until then you can wrap the call to the miner into a batch loop like this:

:loop
TradeTec-Miner.exe
goto loop


This should make sure that the miner is restarted after a crash (even if that shouldn't happened at all!). I will add the settings for the cuda grid and block size into the next release of the UI version next week. So long you can use the commandline miner if you like, this allows you to verify the CUDA 9.20 version as well since it brings better results on my system. The commandline version also supports the cuda grid/block size settings already.

Thanks - and happy mining.

[nickeltabs]

Hi I can't get the GUI miner for Windows OS and Nvidia GPU working, but I am using the bat file to run the miner and it is faster than the
_progpowminer-cuda-windows-0.16_final_ with the same setting that I had was 64.4 MHs and now it is 67.36 MHs using the  --cuda-block-size 320   added to the line

[TrailingStop]

Hi nickeltabs,

do you have more details for my why you cannot run the GUI version? Do you see a error message? Di you see the windows for the miner and the control?

Yes, I see improvements of that size on my rigs. You might also want to try the CUDA 9 release, it gives me a little bit more hashrate than the CUDA 10 release - but that might be very system dependent.

[nickeltabs]

I have everything entered then I am stuck at this Part:::
Add your rigs
Next stop is to add your rigs. Go to ‘Edit’->’Add new rig…’. Now the dialog to add an IP/port pair shows up. Enter the information to allow the control software to connect with the miner-rig. If you run the Miner and the MinerControl on the same box you can use the loopback address (127.0.0.1) and the default port 8010 if that is OK for you. Otherwise, enter the IP of the rig.

[TrailingStop]

Do you have the GUI-Miner (TradeTec-Miner.exe) running? Please make sure that is is running an that you enable the connection to the Control-App by clicking on 'Listen'. Then if you add the rig click in the add-rig dialog just on 'Add Rig'. 127.0.0.1 is OK if miner and control run on the same PC.

[TrailingStop]

Hi nickeltabs,

any update for me? You have still issues with the GUI release?