T-Rex 0.20.4 NVIDIA GPU miner (Ethash, Octopus, Kawpow, MTP)

[trexminer]

Dev will you release miner version for new x16r algo soon?there are other x16r coins that will fork before rvn

It's already released as 0.14.1 beta version and available to download from our Discord server (#download-links channel) https://discord.gg/gj7jcYf

I think he is talking about x16rv2 algo.

Yeah, I guessed the question was about x16rv2. t-rex 0.14.1 beta supports x16rv2

[1624427050]

1624427050

[1624427050]

1624427050

[1624427050]

1624427050

[1624427050]

1624427050

[1624427050]

1624427050

[tbearhere]

Dev will you release miner version for new x16r algo soon?there are other x16r coins that will fork before rvn

It's already released as 0.14.1 beta version and available to download from our Discord server (#download-links channel) https://discord.gg/gj7jcYf

I think he is talking about x16rv2 algo.

Yeah, I guessed the question was about x16rv2. t-rex 0.14.1 beta supports x16rv2

Ok thx. 

[cel1697i845]

X16RV2 Test Beta T-Rex 0.14.2 (Example PEXA)
https://youtu.be/AJlZH1E-XJg

[trexminer]

Version 0.14.4 released.

Change log:
* Add x16rv2 algorithm (upcoming RVN fork)
* Add ability to auto-switch mining algorithm using new --fork-at parameter:
    RVN fork: --fork-at x16rv2=2019-10-01T16:00:00
    See the help file for more details

Bug fixes:
* (Linux) Miner wouldn't start in watchdog mode via symlink

NOTE (RVN hardfork): In order for the miner to automatically switch to mining x16rv2 at the time of RVN fork, please make sure
1) T-Rex is launched in watchdog mode (--no-watchdog parameter should NOT be set in your bat file)
2) Your system clock is synchronised with a time server (The miner uses your system clock to check if it's time to switch)
3) Add --fork-at x16rv2=2019-10-01T16:00:00 parameter to the miner start cmd line. If your pool changes ports for the new algo, make it --fork-at x16rv2:3637=2019-10-01T16:00:00 where 3637 is the new port the miner should switch to (replace it with the actual port number)

If the miner is started in watchdog mode and you've set the fork time correctly, you will see a message
Fork has been requested at Tue Oct  1 16:00:00 2019 UTC. Algo will be changed to x16rv2.

[Vispilio]

Version 0.14.4 released.

Change log:
* Add x16rv2 algorithm (upcoming RVN fork)
* Add ability to auto-switch mining algorithm using new --fork-at parameter:
    RVN fork: --fork-at x16rv2=2019-10-01T16:00:00
    See the help file for more details

Bug fixes:
* (Linux) Miner wouldn't start in watchdog mode via symlink

NOTE (RVN hardfork): In order for the miner to automatically switch to mining x16rv2 at the time of RVN fork, please make sure
1) T-Rex is launched in watchdog mode (--no-watchdog parameter should NOT be set in your bat file)
2) Your system clock is synchronised with a time server (The miner uses your system clock to check if it's time to switch)
3) Add --fork-at x16rv2=2019-10-01T16:00:00 parameter to the miner start cmd line. If your pool changes ports for the new algo, make it --fork-at x16rv2:3637=2019-10-01T16:00:00 where 3637 is the new port the miner should switch to (replace it with the actual port number)

If the miner is started in watchdog mode and you've set the fork time correctly, you will see a message
Fork has been requested at Tue Oct  1 16:00:00 2019 UTC. Algo will be changed to x16rv2.

can you talk a bit more about your mining projections after the RVN hard fork, will it resume its spot among the top contenders as the most

profitable coin to mine with GPU's, or would you decisively recommend to mine something else particularly for 1080 TI's at the moment ?..

[borox]

can you talk a bit more about your mining projections after the RVN hard fork, will it resume its spot among the top contenders as the most

profitable coin to mine with GPU's, or would you decisively recommend to mine something else particularly for 1080 TI's at the moment ?..

I could hand over my magic crystal ball. 

[Kodaman]

Will there be an improvement on the X25X algo?

[luka1002]

I am having problem with one of miners. It is W10 1903, 2x1070 Nvidia with latest drivers. Cpu usage is locked on 100% on miner I downloaded today latest miner for rvn fork ..

https://i.imgur.com/9urmdk3.png

[joseph32]

I am having problem with one of miners. It is W10 1903, 2x1070 Nvidia with latest drivers. Cpu usage is locked on 100% on miner I downloaded today latest miner for rvn fork ..

If you also have updated your drivers, go back to an older version (430.x or 431.x). Its a bug in the newest driver, which will result in most systems in a 100% CPU usage.

[luka1002]

I am having problem with one of miners. It is W10 1903, 2x1070 Nvidia with latest drivers. Cpu usage is locked on 100% on miner I downloaded today latest miner for rvn fork ..

https://i.imgur.com/9urmdk3.png

If you also have updated your drivers, go back to an older version (430.x or 431.x). Its a bug in the newest driver, which will result in most systems in a 100% CPU usage.

Thank you, bingo. Reverted to 419.23 and then to 431 and working ok (both).

https://b.imge.to/2019/10/01/vqXehC.png

[frequencydip]

Has anyone else had an issue with version 0.11.1 and above having the miner shutdown after around 3 minutes with the error "T-Rex instance wasn't validated", "Messy shutdown"?

I'm mining MTP and have 2 RTX 2080's running in Windows 7 on the latest 430.86 nvidia drivers.

If I revert back to 0.11.0 I don't have any issues.

I'm having the same issue;
TREX: T-Rex instance wasn't validated

trying to upgrade to support the RVN hard fork but the new version keeps shutting down, on Linux. v11. use to work flawlessly
Driver Version: 430.50       CUDA Version: 10.1

I don't have any firewalls that should be blocking this machine, on spectrum internet.

[frequencydip]

TREX: T-Rex instance wasn't validated

trying to upgrade to support the RVN hard fork but the new version keeps shutting down, on Linux. v11. use to work flawlessly
Driver Version: 430.50       CUDA Version: 10.1

I don't have any firewalls that should be blocking this machine, on spectrum internet.

Checking if my rig can get to the dev fees and i get this:

localhost:~$ wget https://trex-miner.com --no-check-certificate
--2019-09-30 18:17:07--  https://trex-miner.com/
Resolving trex-miner.com (trex-miner.com)... 45.77.35.138
Connecting to trex-miner.com (trex-miner.com)|45.77.35.138|:443... connected.
WARNING: cannot verify trex-miner.com's certificate, issued by ‘/O=T-Rex/CN=*.trex-miner.com’:
  Self-signed certificate encountered.
    WARNING: certificate common name ‘*.trex-miner.com’ doesn't match requested host name ‘trex-miner.com’.
HTTP request sent, awaiting response... 400 Bad Request
2019-09-30 18:17:08 ERROR 400: Bad Request.

Is this part of the issue?

[ivakar]

can you talk a bit more about your mining projections after the RVN hard fork, will it resume its spot among the top contenders as the most

profitable coin to mine with GPU's, or would you decisively recommend to mine something else particularly for 1080 TI's at the moment ?..

unfortunately, due the situation on the global cryptomarket, low profits on 1080ti we have now not depend on the miner
of course it is good to squish extra 2-5 precents of margin because of miner's optimizations, but due to the fact, that new, optimized version of the miner will spread over miners and global hashrate would grow and profit will be same as before miner's updates .

[hustleman]

With the new algo for Raven... whats the best intensity for 1070s, 20 or 21?

[jebidia]

Does the updated miner work better with 2080 cards?  My 1080 ti machines are fine but I crash with the previous version.

[tg88]

I am having problem with one of miners. It is W10 1903, 2x1070 Nvidia with latest drivers. Cpu usage is locked on 100% on miner I downloaded today latest miner for rvn fork ..

For comparison of cpu usage, Driver 436.02 vs Driver 430.64 took a few days to identify that new drivers were overloading cpu.

Driver 436.02


Driver 430.64

[Vispilio]

so looks like profitability is back for RVN after the fork, just to confirm does the new algo on 0.14.4 work as smoothly as before,

what are your newest results if anyone can make a comparison with the past versions pre fork ?..

[ivakar]

For comparison of cpu usage, Driver 436.02 vs Driver 430.64 took a few days to identify that new drivers were overloading cpu.

this is really strange, but on my pc there is no difference in cpu load for both versions. no idea why it is so? might be the reason I'm using 1080ti not the new version of nvidia cards with this modern tensor cores?
also I have to mention that performance change is very low, so basically no need to upgrade imo, better save time and stay with current version.

[nambu]

Any benchmark on 1660ti ?

[tg88]

this is really strange, but on my pc there is no difference in cpu load for both versions. no idea why it is so? might be the reason I'm using 1080ti not the new version of nvidia cards with this modern tensor cores?
also I have to mention that performance change is very low, so basically no need to upgrade imo, better save time and stay with current version.

I updated the driver after the security alert made by nvidia ... In my case it affected the cpu overload, maybe for other gpus models this doesn't really happen.
https://www.techradar.com/news/nvidia-graphics-cards-vulnerable-to-security-flaw