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

[gusknure]

TT-Miner.exe -A MTP-101 -P 32BKFGN2THJKZQ3xCkUmEfZ8khU.RIG1070:x@mtp.usa.nicehash.com:3374 -logpool

[gusknure]

06:42:04.047 <- {"id":null,"method":"mining.notify","params":["00000206b3302574","d5de1142e363afff19fe147d2f3f1873c8544323eee14d3143f821256f95a660","01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff360358750204e06dd65c08","1b324d696e6572732068747470733a2f2f326d696e6572732e636f6dffffffff07004e725300000 0001976a91455154ec4385f71c4a284731cafaf5d19406c030588ac8017b42c000000001976a914 e9d8e0514c1e74a0499018ae2dd5e64dff59eb1b88ac80f0fa02000000001976a9147d9ed014fc4 e603fca7c2e3f9097fb7d0fb487fc88ac80f0fa02000000001976a914bc7e5a5234db3ab82d74c3 96ad2b2af419b7517488ac80f0fa02000000001976a914ff71b0c9c2a90c6164a50a2fb523eb54a 8a6b55088ac80d1f008000000001976a9140654dd9b856f2ece1d56cb4ee5043cd9398d962c88ac 80f0fa02000000001976a9140b4bfb256ef4bfa360e3b9e66e53a0bd84d196bc88ac00000000",[],"00100020","d1050a1b","e06dd65c",true]}
06:42:04.282 <- {"id":3,"result":true,"error":null}
09:42:13.791 SOCKET: ErrorConnect Connection lost(0) / _NetworkInterfaceSocket::_CommunicationLoop:755
09:42:13.791 Disconnected
06:42:16.808 -> {"id":1,"method":"mining.subscribe","params":["TT-Miner/2.2.3"]}
09:42:16.808 SOCKET: Error connected(0) / _NetworkInterfaceSocket::_CommunicationLoop:615
06:42:17.240 <- {"id":1,"result":["e5ec5fec2d6294286a4a95682319abd2","0100000000005e92da"],"error":null}
06:42:17.240 -> {"id":2,"method":"mining.authorize","params":["32BKFGN2THJKCUxCkUmEfZ8khU.RIG1070","x"]}
06:42:17.458 <- {"id":2,"result":true,"error":null}
06:42:17.458 -> {"id":3,"method":"mining.extranonce.subscribe","params":[]}
06:42:17.475 <- {"id":null,"method":"mining.set_target","params":["0000000000000000000000000000000000000000000000000000f0ff0f000000"]}

[gusknure]

_NetworkInterfaceSocket::_CommunicationLoop:615
09:47:56.802 SOCKET: ErrorConnect Connection lost(0) / _NetworkInterfaceSocket::_CommunicationLoop:755
09:47:56.803 Disconnected
09:47:58.741 Subscribe failed. Protocol-Mode was = EthProxy-Stratum
06:47:58.741 -> {"id":1,"method":"eth_submitLogin","worker":"RIG1070","params":["32BKFGZQ3dHhtFCUxCkUmEfZ8khU"]}
09:47:58.741 SOCKET: ErrorConnect Cannot send data - not connected(-1) / _NetworkInterfaceSocket::SendData:131

[TrailingStop]

_NetworkInterfaceSocket::_CommunicationLoop:615
09:47:56.802 SOCKET: ErrorConnect Connection lost(0) / _NetworkInterfaceSocket::_CommunicationLoop:755
09:47:56.803 Disconnected
09:47:58.741 Subscribe failed. Protocol-Mode was = EthProxy-Stratum
06:47:58.741 -> {"id":1,"method":"eth_submitLogin","worker":"RIG1070","params":["32BKFGZQ3dHhtFCUxCkUmEfZ8khU"]}
09:47:58.741 SOCKET: ErrorConnect Cannot send data - not connected(-1) / _NetworkInterfaceSocket::SendData:131

Let me check...

[TrailingStop]

_NetworkInterfaceSocket::_CommunicationLoop:615
09:47:56.802 SOCKET: ErrorConnect Connection lost(0) / _NetworkInterfaceSocket::_CommunicationLoop:755
09:47:56.803 Disconnected
09:47:58.741 Subscribe failed. Protocol-Mode was = EthProxy-Stratum
06:47:58.741 -> {"id":1,"method":"eth_submitLogin","worker":"RIG1070","params":["32BKFGZQ3dHhtFCUxCkUmEfZ8khU"]}
09:47:58.741 SOCKET: ErrorConnect Cannot send data - not connected(-1) / _NetworkInterfaceSocket::SendData:131

Does an older version of TT work with NH? Can you try different pool - just to test please?

[gusknure]

2.2.1 and 2.2.0 don't work also

[TrailingStop]

2.2.1 don't work also

Hi, yes I tried here also some older version. They all disconnect from NH, but work on other pools. Not sure what changed? I will try to get in touch with some of the NH guys and find out if there was any change in the protocol.

[gusknure]

Other pools work smoothly

[TrailingStop]

Other pools work smoothly

Yes - just tried ETHASH on NH - works without issues.

[Divinity666]

There is smth wrong with nicehash MTP server, no TT no Cryptodredge can connect to it, "connection was closed by pool" is what I get on CD, even look at server's stats: hashrate has dropped dramatically since this started ~2 days ago.

[Shaddyr]

v.2.2.3
single 1070Ti didn't like the version - screen attached. With the same settings v2.2.2 works fine. But 3x1066 agreied to work with no errors.

Hi,

I change the mining code to get some more hashes. It could be that OC settings that works with older version doesn't work now. I see that you have some accepted and some rejected shares. You have no rejected shares with 1660?

106x - rejects like before, no more no less
>>
About nicehash - had same problems with other miners. Looks like some NH servers was bad - at list EU zone. Now its Ok.

[korinee]

Refresh of the version 2.2.3.

Added the cuda 10.0 and cuda 9.2 version of ProgPoWZ for Zano and a small fix for fairpool.

Let me know if you have any issues.

Happy mining.

wow! what a wonderful miner

could you add a tethashv1 algoritm?

This is also anti asic algoritm forked from ethash

https://github.com/tao-foundation/tethashv1
https://github.com/tao-foundation/FNV-Analysis
https://github.com/tao-foundation


pool info
https://miningpoolstats.stream/trusteth

[joseph32]

2.2.1 don't work also

Hi, yes I tried here also some older version. They all disconnect from NH, but work on other pools. Not sure what changed? I will try to get in touch with some of the NH guys and find out if there was any change in the protocol.

It is since 2..3 days. Mining MTP @ Nicehash will just disconnect the miner. Buy the way, its the same picture with CD. So its clearly something with Nicehash. Maybe buggy, maybe they changed something.

[dkmontague]

Been getting a lot of rejected shares with 2.2.3 version... any tips?  Im running at 14 intensity on MTP and still getting like 3-5% rejects

[jelome198959]

Is this the best miner for MTP? What hashrates should I get with a 2080 Ti at 75-80% power limit?

[korinee]

Refresh of the version 2.2.3.

Added the cuda 10.0 and cuda 9.2 version of ProgPoWZ for Zano and a small fix for fairpool.

Let me know if you have any issues.

Happy mining.

wow! what a wonderful miner

could you add a tethashv1 algoritm?

This is also anti asic algoritm forked from ethash

https://github.com/tao-foundation/tethashv1
https://github.com/tao-foundation/FNV-Analysis
https://github.com/tao-foundation


pool info
https://miningpoolstats.stream/trusteth

Thanks TT-Miner!!

TT-Miner is best miner for ProgPow(z), MTP, LYRA2V3, UBQHASH, and tethashv1!!!

[2h4u]

@TrailingStop

Looks like some of the command-line arguments are fixed position arguments. I wasted over an hour and figured out that "tt-miner.exe -P pool -A algo" doesn't work. But "tt-miner.exe -A algo -P pool" does.
Refreshingly new programming practice, I say.

[TrailingStop]

@TrailingStop

Looks like some of the command-line arguments are fixed position arguments. I wasted over an hour and figured out that "tt-miner.exe -P pool -A algo" doesn't work. But "tt-miner.exe -A algo -P pool" does.
Refreshingly new programming practice, I say.

Hi,

I'm sorry for the problem, but it is almost impossible to test all possible configurations. I could verify this bug and fixed it for the next release. Please report any issues early so that I can check that - no need for you to wast your time on that.

Thanks for reporting.

[Shivoreun]

Commandline for the miner is:
tt-miner -a mtp -A MTP-100 -P stratum+tcp://<address>.nvidia01:x@zcoin-eu.mintpond.com:3000 --api-bind 127.0.0.1:4035

The rig is on Win10, has local IP 192.168.128.21, firewall is disabled for all networks, WinDefender disabled via registry. IPv6 is disabled.

The telnet localhost 4035 - miner answering.
The telnet 127.0.0.1 4035 - miner answering.

Trying from another rig, in the same network (192.168.128.20)
telnet 192.168.128.21 4035 - connection denied.

No wonders as you have bound API to 127.0.0.1 which is localhost. It is not accessible from LAN.
Technically you should modify the command line to utilize --api-bing 0.0.0.0:4035

0.0.0.0 means ALL of the computer IP addresses present, so it should include 127.0.0.1 and 192.168.128.21 which I assume is your LAN IP address.

However, looking at what TrailingStop wrote above "0.0.0.0 will be translated to localhost (127.0.0.1)." I doubt this will work until TT fixes this behavior.

OR

Just use --api-bind 192.168.128.21:4035 and API will be accessible from LAN, but you may have issues with your miner (awesomeminer or NHML or smth else) if any.

Hi,

This is 100% correct. I bound 127.0.0.1 to localhost. I was not aware that it should bound to all. Will fix that in next release.
Thanks for pointing to this issue.

Dear developer, when we can expect for fixing this issue? 
BTW, thanks for this miner. It's the best now for MTP

[dkmontague]

Trying to setup backup pool... keeps saying "no backup pool defined" at startup.  Can you advise what is wrong with my command line?

TT-Miner.exe -A MTP-101 -d 0 -PP 5 -pool zcoin-us.mintpond.com:3000 -user aCH5X9vpX5kvtH4RXkJLcdcNHnarmRpa27 -pass qZodTD -worker MyRigGPU0 -pool2 xzc.2miners.com:8080 -wal2 aCH5X9vpX5kvtH4RXkJLcdcNHnarmRpa27 -pass2 x -worker2 MyRigGPU0