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

[Damiber]

HI Thanks for helping

It looks like i might have had a faulty video card. Just testing and will get back to you .

[TrailingStop]

sure - np. happy to help.

[Damiber]

Okay just mining with one card to the local qt wallet.

it starts mining with the correct wattage at +-89w and then this drops to +-4w . Is it actually mining at this wattage.

15:58:42.924 GPU[00-RVN]:   9.044 MH/s [A0:R0:S0 0.0%]  CClk:139.0 MHz-0%  MClk:405.0 MHz-0%  35°C  64%  4 W  2.261 MH/s/W  1.069 GB left  last: -
15:58:42.924 All[RVN]:      9.044 MH/s [A0:R0:S0 0.0%]  4 W  2.261 MH/s/W  uptime: 0 00:24:28  last: -
15:58:42.924 Luck[RVN]:     555.3 TH @ 9.044 MH/s -> avg. time/shr: 17054:14:33   passed 24:27   this shr: 0%   session: 0%
15:58:57.915 GPU[00-RVN]:   9.044 MH/s [A0:R0:S0 0.0%]  CClk:139.0 MHz-0%  MClk:405.0 MHz-0%  35°C  64%  4 W  2.261 MH/s/W  1.069 GB left  last: -
15:58:57.915 All[RVN]:      9.044 MH/s [A0:R0:S0 0.0%]  4 W  2.261 MH/s/W  uptime: 0 00:24:43  last: -
15:58:57.915 Luck[RVN]:     555.3 TH @ 9.044 MH/s -> avg. time/shr: 17054:14:33   passed 24:42   this shr: 0%   session: 0%
15:58:58.055 Pool[RVN-0]:   Difficulty changed from 555.3 TH to 554.4 TH
15:58:58.055 Pool[RVN-0]:   Received new job#: 13862e432f195d79f62b323e2fd4c7aa8603f08f558e5900117cc8ab00b16188
15:58:58.055 Pool[RVN-0]:   Working on Block#: 2682326, BlkTime: ~59 sec. - Blocks until epoch change: 2674, time left: ~1 19:49
15:58:04.694 Pool[RVN-0]:   Difficulty changed from 554.4 TH to 554.2 TH
15:58:04.694 Pool[RVN-0]:   Received new job#: 16706c99792d4b2d0003171a79fc68269c8451b55244a560b34b807d01fdd65d
15:58:04.694 Pool[RVN-0]:   Working on Block#: 2682327, BlkTime: ~57 sec. - Blocks until epoch change: 2673, time left: ~1 18:19
15:58:04.694 Coin[RVN]:     Modify algo for block: 2682327, ProgPoW period: 894109
15:59:12.916 GPU[00-RVN]:   9.044 MH/s [A0:R0:S0 0.0%]  CClk:139.0 MHz-0%  MClk:405.0 MHz-0%  35°C  64%  4 W  2.261 MH/s/W  1.069 GB left  last: -
15:59:12.916 All[RVN]:      9.044 MH/s [A0:R0:S0 0.0%]  4 W  2.261 MH/s/W  uptime: 0 00:24:58  last: -
15:59:12.916 Luck[RVN]:     554.2 TH @ 9.044 MH/s -> avg. time/shr: 17020:56:26   passed 24:57   this shr: 0%   session: 0%
15:59:27.916 GPU[00-RVN]:   9.044 MH/s [A0:R0:S0 0.0%]  CClk:139.0 MHz-0%  MClk:405.0 MHz-0%  35°C  64%  4 W  2.261 MH/s/W  1.069 GB left  last: -
15:59:27.916 All[RVN]:      9.044 MH/s [A0:R0:S0 0.0%]  4 W  2.261 MH/s/W  uptime: 0 00:25:13  last: -
15:59:27.916 Luck[RVN]:     554.2 TH @ 9.044 MH/s -> avg. time/shr: 17020:56:26   passed 25:12   this shr: 0%

Pool info

15:44:27.912 All[RVN]:      9.322 MH/s [A0:R0:S0 0.0%]  88 W  105.9 kH/s/W  uptime: 0 00:10:13  last: -
15:44:27.912 Luck[RVN]:     578.8 TH @ 9.322 MH/s -> avg. time/shr: 17247:39:40   passed 10:12   this shr: 0%   session: 0%
15:44:42.924 GPU[00-RVN]:   9.306 MH/s [A0:R0:S0 0.0%]  CClk:1.582 GHz-100%  MClk:4.644 GHz-89%  64øC  64%  89 W  104.6 kH/s/W  1.069 GB left  last: -
15:44:42.924 All[RVN]:      9.306 MH/s [A0:R0:S0 0.0%]  89 W  104.6 kH/s/W  uptime: 0 00:10:28  last: -
15:44:42.924 Luck[RVN]:     578.8 TH @ 9.306 MH/s -> avg. time/shr: 17278:01:36   passed 10:27   this shr: 0%   session: 0%
15:44:43.335 Pool[RVN-0]:   Difficulty changed from 578.8 TH to 578.1 TH
15:44:43.335 Pool[RVN-0]:   Received new job#: 2202ee5b67f714c4aa17f8a0fe1ba905842a7d75e1da329d8dfe6bedcd09f3c2
15:44:43.335 Pool[RVN-0]:   Working on Block#: 2682313, BlkTime: ~52 sec. - Blocks until epoch change: 2687, time left: ~1 14:48
15:44:46.533 Pool[RVN-0]:   Difficulty changed from 578.1 TH to 579.4 TH
15:44:46.533 Pool[RVN-0]:   Received new job#: 20e6a6ad569e289f77cc634f7ca678c06d7f17563d60a505522fe113d0f66139
15:44:46.533 Pool[RVN-0]:   Working on Block#: 2682314, BlkTime: ~48 sec. - Blocks until epoch change: 2686, time left: ~1 11:48
15:44:56.498 Pool[RVN-0]:   Difficulty changed from 579.4 TH to 583.6 TH
15:44:56.498 Pool[RVN-0]:   Received new job#: debfbbfaeb8b5a06a333d38ff5cf82069ab3f9af4cc71100e1244a1305ab97e5
15:44:56.498 Pool[RVN-0]:   Working on Block#: 2682315, BlkTime: ~45 sec. - Blocks until epoch change: 2685, time left: ~1 09:33
15:44:56.498 Coin[RVN]:     Modify algo for block: 2682315, ProgPoW period: 894105
15:44:56.498 Krnl[00-RVN]:  Reuse Kernel (A048#2BA85-61) for NVIDIA P106-100 - wait for completion.
15:44:57.882 Krnl[00-RVN]:  Kernel (A048#2BA85-61) loaded
15:44:57.899 GPU[00-RVN]:   9.044 MH/s [A0:R0:S0 0.0%]  CClk:1.582 GHz-0%  MClk:4.644 GHz-0%  61øC  65%  28 W  323.0 kH/s/W  1.069 GB left  last: -
15:44:57.899 All[RVN]:      9.044 MH/s [A0:R0:S0 0.0%]  28 W  323.0 kH/s/W  uptime: 0 00:10:42  last: -
15:44:57.899 Luck[RVN]:     583.6 TH @ 9.044 MH/s -> avg. time/shr: 17923:56:58   passed 10:42   this shr: 0%   session: 0%
15:45:12.917 GPU[00-RVN]:   9.044 MH/s [A0:R0:S0 0.0%]  CClk:1.506 GHz-0%  MClk:4.644 GHz-0%  56øC  64%  27 W  335.0 kH/s/W  1.069 GB left  last: -
15:45:12.917 All[RVN]:      9.044 MH/s [A0:R0:S0 0.0%]  27 W  335.0 kH/s/W  uptime: 0 00:10:58  last: -
15:45:12.917 Luck[RVN]:     583.6 TH @ 9.044 MH/s -> avg. time/shr: 17923:56:58   passed 10:57   this shr: 0%   session: 0%
15:45:27.915 GPU[00-RVN]:   9.044 MH/s [A0:R0:S0 0.0%]  CClk:189.0 MHz-0%  MClk:405.0 MHz-0%  51øC  64%  5 W  1.809 MH/s/W  1.069 GB left  last: -
15:45:27.915 All[RVN]:      9.044 MH/s [A0:R0:S0 0.0%]  5 W  1.809 MH/s/W  uptime: 0 00:11:13  last: -
15:45:27.915 Luck[RVN]:     583.6 TH @ 9.044 MH/s -> avg. time/shr: 17923:56:58   passed 11:12   this shr: 0%   session: 0%
15:45:40.023 Pool[RVN-0]:   Difficulty changed from 583.6 TH to 585.4 TH
15:45:40.023 Pool[RVN-0]:   Received new job#: 48aca0d6f797690661fd40da12ad72f97463f9a77a296ee075e748bc9322a27f
15:45:40.023 Pool[RVN-0]:   Working on Block#: 2682316, BlkTime: ~45 sec. - Blocks until epoch change: 2684, time left: ~1 09:33

[TrailingStop]

let me check this. Do you use the latest version?

Did you notice that it will take some time for you to find a block?
15:59:27.916 Luck[RVN]:     554.2 TH @ 9.044 MH/s -> avg. time/shr: 17020:56:26   passed 25:12   this shr: 0%

more than 17020 hours.... ;-(

[Damiber]

Yes but i am just testing this to see if it works against a wallet , then i will put my other 100 cards into operation.

[TrailingStop]

Got it. latest version? 2023.1.7? If so can you run it with logs? add:
-log -logpool
to your commandline. Please DM me the files you will find in the Logs folder.

[Damiber]

Have sent you DM request

Does the api not auto refresh itself

[TrailingStop]

Have sent you DM request

Does the api not auto refresh itself

Yes - already replied.

refresh: https://github.com/TrailingStop/TT-Miner-release/releases/tag/2023.1.6

[crsminer]

Hi TT,

Can you please implement NEXA?
Way more profitable than all others.

Thx.

[CryptoSperm]

I'm getting the error "Block does not solve the boundary - Function" while Solo mining on a kawpow test fork.  It happens after block 7499 is mined.  If I restart the chain it will again error at block 7499 or 7500.  Could it be related to #define ETHASH_EPOCH_LENGTH 7500?  Any Ideas?

[TrailingStop]

I'm getting the error "Block does not solve the boundary - Function" while Solo mining on a kawpow test fork.  It happens after block 7499 is mined.  If I restart the chain it will again error at block 7499 or 7500.  Could it be related to #define ETHASH_EPOCH_LENGTH 7500?  Any Ideas?

Can you please share more information? The commandline you use and the OS would be very helpful to help.

[CryptoSperm]

In the RVN fork code src/crypto/ethash/include/ethash/ethash.h for testing purpose I changed the epoch length "#define ETHASH_EPOCH_LENGTH 7500" to "#define ETHASH_EPOCH_LENGTH 56" and it confirmed to be the configuration issue with TT-Miner erroring after mining block 55 instead of 7499. 

The ERROR: GPU[00-KAW]:   Rejected #2175, RT in 71 ms. [Block does not solve the boundary - Function: 16779391(-22)][10.10.0.191:4456]

So it looks like the miner errors when the epoch changes on the node.

The miner is on windows with command line:
 TT-Miner.exe -coin KAW -P http://my_username:my_password@10.10.0.191:4456

The QT node it is mining to is Ubuntu with config:
 server=1
 miningaddress=correctwalletaddress
 rpcuser=my_username
 rpcpassword=my_password
 rpcallowip=127.0.0.1
 rcpallowip=10.10.0.101
 rcpallowip=10.10.0.191
 rpcport=4006
 

[TrailingStop]

So you change the epoch length of the node and mine with TT to that node? What do you expect to happened other than the fail you see?

[crsminer]

@TT

Hi! Can you add Clore and/or Kaspa?

Thx!

[TrailingStop]

@TT

Hi! Can you add Clore and/or Kaspa?

Thx!

Hi - Kaspa is on the list for the new release, Clore is already supported with kawpow algo (no -coin option):

TT-Miner -a KawPoW -P ......

Let me know if that works for you or if you have any issues.

[crsminer]

Wow.. did not know that.. you should write in the description that Clore is supported .

It works! I tried with -algoalt KawPoW.
Only small issue is that coin name is not printed in miner output, it is ---  Pool[DEF-0].

Now we wait for KAS in next release... any ETA?

[TrailingStop]

Wow.. did not know that.. you should write in the description that Clore is supported .

It works! I tried with -algoalt KawPoW.
Only small issue is that coin name is not printed in miner output, it is ---  Pool[DEF-0].

Now we wait for KAS in next release... any ETA?

hope to get it out very soon. Will not be the fastest under the sun - but it is a first start.

[CryptoSperm]

So you change the epoch length of the node and mine with TT to that node? What do you expect to happened other than the fail you see?

I changed the length to reproduce the error with different epoch configuration which it did.  I noticed on the miner it is still looking at epoch 0 even though the chain moved to the next epoch.  The CPU mining was able to continue the chain.  I'm just trying to figure out why the miner isn't moving to the new epoch regardless of epoch length. 

[grendel25]

Thank you for supporting Epic Cash!

[bubers]

Hello, I have a problem with TT Miner when I mine EPIC with another coin whenever the miner creates the DAG file and sets the kernels of the cards it works sometimes then it runs for a certain time and at some point suddenly the whole rig switches completely from what can it be