T-Rex Miner

What you should know about us and our
T-Rex Miner:

Here’s what you should know about T-Rex Miner:

  • T-Rex miner is a powerful and efficient software program for mining various cryptocurrencies
  • Utilizes your computer’s GPU(s) for complex mathematical calculations to solve blocks and earn rewards
  • Available for Windows, Linux and MacOS
  • Considered one of the most efficient and powerful mining software in the market
  • Allows for adjustments and configurations such as hash rate, power consumption, and temperature control for optimal performance
  • Utilizes natural language processing techniques for efficient mining
  • Versatile solution and easy to set up and use
  • A must-have tool for maximizing your hardware’s potential in crypto mining.

Key Features:

Here are some key features of the T-Rex miner:

  • High Hash Rate: T-Rex miner boasts a high hash rate of up to 110 TH/s, making it one of the most efficient miners on the market.
  • Algorithm Support: It is designed to work with the algorithms used by coins such as Bitcoin, Litecoin, and other similar coins.
  • Operating System Support: T-Rex miner is compatible with Windows, Linux and MacOS operating systems, making it a versatile solution for crypto miners.
  • Customizable settings: The software allows users to configure and adjust settings such as the hash rate, power consumption, and temperature control to optimize their mining performance.
  • Easy to use: The software is user-friendly and easy to set up and use.
  • NLP technique: T-Rex miner uses natural language processing (NLP) techniques to mine efficiently.
  • Optimize Hardware: It’s a powerful tool that helps you to get the most out of your hardware in crypto mining.
  • Advanced features: T-Rex Miner also allows for advanced features such as overclocking, fans control and API for remote monitoring.
  • Stability: T-Rex miner is well known for its stability and low rejection rate.
  • Security: T-Rex miner uses the latest security measures to protect your mining operation from hacking attempts.

What coins can t-rex miner mine ?

Some of the tokens that T-Rex miner can mine include, but are not limited to:

  • Bitcoin (BTC)
  • Bitcoin Cash (BCH)
  • Bitcoin Gold (BTG)
  • Dash (DASH)
  • Litecoin (LTC)
  • Ethereum Classic (ETC)
  • Zcash (ZEC)
  • Ravencoin (RVN)
  • Grin (GRIN)
  • Beam (BEAM)
  • ZelCash (ZEL)
  • Aion (AION)
  • Binance Coin (BNB)
  • Vertcoin (VTC)
  • Monero (XMR)

You can download miner by clicking the link below:

Latest release T-Rex v0.26.8

  • Add support for NVIDIA 40xx GPUs
  • Handle v520+ LHR-free video drivers correctly

Quick installation guide:

Here is a quick guide on how to install T-Rex miner:

  1. Download the T-Rex miner.
  2. Extract the files to a folder on your computer.
  3. Open the folder and run the T-Rex.exe file.
  4. Select the coin you want to mine and the mining pool you want to use.
  5. Configure the settings to your liking, such as the hash rate, power consumption, and temperature control.
  6. Click the “Start” button to begin mining.
  7. You can monitor your mining progress by checking the statistics displayed in the T-Rex miner software.

Please note that the above installation guide is general, the instructions may vary depending on the version of the T-Rex miner or your operating system. You can find more detailed instructions below.

To learn more about how to set up T-Rex Miner, you can follow the link by clicking on this text.

Algorithms and DevFee:

T-Rex Miner supports the algorithms listed below. The program commission is displayed for each algorithm. This commission, which is usually only a few percent, is used by us to maintain and improve the miner’s work, as well as to add new functions. Since the program transfers money to our wallet every hour for a short period of time, the commission is collected (usually no more than a minute).

Cryptonight (v7, v8, v9, R, R2, RX, WOW, etc)1%
CuckooCycle (Grin29, Grin31, Aeternity)2%

Please note that the dev fee is subject to change and may vary depending on the version of the T-Rex miner.

Command Line Arguments


-i, --intensity Intensity of operation of video cards 8-25 (default value: auto).

–cpu-priority Program process priority (default value: 2). 0 – inactive, 2 – normal, 5 – highest.

Settings for ProgPOW:

--coin Specify the name of the coin for the ProgPOW algorithm variant.

--nonce-start Specify the number of nonce to search for a solution (for SOLO mining).

--nonce-range-size Specify the size of the Nonce range to search. The range will be shared between all devices (for SOLO mining).

Disable or select video card:

-d, --devices Specify Nvidia devices. You can choose to mine only certain cards using a comma. For example -d 0,2,5 will mine only the first, third and sixth map. Device IDs start at 0.

--ab-indexing View device sorting by bus ID. The first device starts with 1)


--exit-on-cuda-error Causes the miner to exit immediately on CUDA error.

--exit-on-connection-lost Causes the miner to exit immediately when the connection is lost.

--no-watchdog Disable watchdog (not recommended).

Power consumption, temperatures and overclocking:

--temperature-start GPU temperature to turn on the card after turning it off. (default value: 0 – disabled)

Working with the Remote Control API:

-b, --api-bind-telnet IP:port for miner API via telnet (default value: Specify 0 to disable.

--api-bind-http IP:port for miner API via HTTP (default value: Specify 0 to disable.

-J --json-response The telnet API server will make json responses.

Other settings:

--autoupdate Perform an automatic update whenever a newer version of the miner is available.

-B, --benchmark Run a benchmark (testing and debugging).

-c, --config Load and use a configuration file in JSON format.

-version Display help.

-h, --help Display program version.

Pool connection parameters:

-a, --algo Specify the hash algorithm to use. The list of supported algorithms is listed at the beginning of the article.

-o, --url Mining server URL.

-u, --user Username for the mining server.

-p, --pass Password for the mining server.

-r, --retries The number of connection attempts if the network fails.

-R, --retry-pause Pauses in seconds between connection attempts.

-T, --timeout Network timeout, in seconds (default: 180)

--time-limit Network timeout, in seconds. (default value: 0 – disabled)

--back-to-main-pool-sec Forces the miner to switch back to the main pool in case of working with the backup pool. The parameter is set in seconds. (default: 600)

--reconnect-on-fail-shares Causes the miner to immediately reconnect to the pool on N consecutive failed shares (default: 10).

--fork-at Ability to automatically switch the algorithm using this option.

Example RVN fork: --fork-at KAWPOW=2020-05-06T16:00:00

Event log and program interface:

-P, --protocol-dump User protocol log.

-l, --log-path The full path of the log file.

--no-color Disable color output in the console.

--temperature-color Set temperature color for GPUs. Example: 55.65 – this means that the temperature above 55 will be yellow, above 65 – red. (default: 67.77)

-N, --hashrate-avr Sample value in seconds used to calculate average speed (default: 60).

--sharerate-avr Sample value in seconds used to calculate share share (default: 600).

--gpu-report-interval frequency of reporting GPU statistics. (default: 5, i.e. every fifth ball)

-q, --quiet Quiet mode. No GPU statistics will be shown.

--hide-date Hide the date in the console.

--no-nvml Disable GPU NVML statistics.


Profitability of T-Rex miner depends on several factors:

  • Hash rate: The higher the hash rate of the miner, the more chances to mine and earn rewards.
  • Coin price: The value of the coin you are mining will affect the profitability. The higher the value, the more profitable it will be to mine.
  • Difficulty: The difficulty of mining a certain coin will affect the profitability. The higher the difficulty, the less profitable it will be to mine.
  • Electricity cost: The cost of electricity is a significant factor in determining profitability. The higher the electricity cost, the less profitable it will be to mine.
  • Dev fee: Some mining software, like T-Rex miner, takes a percentage of the mined coins as a developer fee.
  • Algorithm: Some algorithms are more profitable than others.

TIP! Change the MTP algorithm to Ethash to configure mining of coins that utilize less of the video card core (the stream processors in it consume the most energy).

24 hour profit ETH mining, t-rex miner info and hiveos. rtx 3080 and rtx 3060ti:

T-Rex Miner vs PhoenixMiner

T-Rex Miner and PhoenixMiner are both software programs used for mining various cryptocurrencies. Both are designed to work with the algorithms used by coins such as Bitcoin, Litecoin, and other similar coins. Both utilize the computer’s hardware, specifically the GPU(s) to perform complex mathematical calculations in order to solve blocks and earn rewards for the miner.

Here are a few key differences between T-Rex Miner and PhoenixMiner:

  • Hash rate: T-Rex Miner boasts a higher hash rate of up to 110 TH/s, while PhoenixMiner’s hash rate is lower.
  • Algorithm support: T-Rex Miner supports a wide range of algorithms, while PhoenixMiner’s algorithm support is more limited.
  • Operating System Support: T-Rex miner support Windows, Linux and MacOS, PhoenixMiner only support Windows.
  • Dev fee: T-Rex Miner has a dev fee of 1% for most algorithms, while PhoenixMiner’s dev fee ranges from 0.65% to 1%.
  • Advanced features: PhoenixMiner has more advanced features such as dual mining and remote management.
  • Stability: T-Rex miner is well known for its stability and low rejection rate, PhoenixMiner is also considered as a stable miner.

Ultimately, the choice between T-Rex Miner and PhoenixMiner will depend on your specific needs and preferences. Both programs are powerful and efficient mining software, but T-Rex Miner is considered more versatile and has a higher hash rate, while PhoenixMiner is more advanced with more features.

Is T-Rex Miner better than Phoenix miner for gtx 1660 super mining ethereum? 31.8mh/s vs 31.7mh/s:

Antivirus alerts:

The binaries are packed using third-party software that mutilates the original machine code to shield the miner from reverse engineering assaults. As a result, some anti-virus engines can detect signatures in the executable file that are identical to those of real viruses that are protected by the same packer. In any event, bitcoin miners should not be used on computers that store sensitive information (wallets, passwords, etc.).


T-Rex 0.26.8

  • Add support for NVIDIA 40xx GPUs
  • Handle v520+ LHR-free video drivers correctly

T-Rex 0.26.6

  • Add ETC+ALPH dual mining support
  • (progpow-veil) Support upcoming Veil fork

Bug fixes:

  • (autolykos2Invalid extranonce2 size error when mining to Nicehash

T-Rex 0.26.4

  • LHR unlock of 3080 12GB and 3050 (~90%)

Bug fixes:

  • Miner sometimes takes too long to shut down on multi-GPU rigs

T-Rex 0.26.1

  • (ethashautolykos2) LHR 100% unlock (except 3080 12GB and 3050)
    LHR unlocker requires 512.xx version of the driver on Windows, and 510.xx on Linux

T-Rex 0.25.15

  • (LHR) Extend the new LHR unlock functionality to ETH+ALPH dual mining, and ERGO single mode.
    LHR tune values aren’t accurate, but once you’ve found a value that’s stable for your GPU, you can set it manually with --lhr-tune and get consistent results across miner restarts.
  • (LHR) Allow setting “up” and “down” auto-tune intervals separately, e.g. --lhr-autotune-interval 5:120, meaning that in --lhr-autotune-mode full mode the miner will be increasing LHR tune value every 5 minutes, and decreasing it as soon as it starts tripping LHR more frequently than once every two hours.
  • (LHR) Change --lhr-autotune-step-size default value to 0.1 (previously 0.5)
  • (LHR) Low power mode can now be set for GPUs individually, e.g. --lhr-low-power 0,1,1,0 – the second and third GPUs will be working in low power mode.
    If you previously had --lhr-low-power in your config, the equivalent would be --lhr-low-power 1 (or "lhr-low-power": "1" in HiveOS).

Bug fixes:

  • LHR unlocker is more stable compared to 0.25.12, infinite LHR lock loops should be solved now
  • (ethashblake3) “Duplicate share” issue

IMPORTANT: LHR unlocker requires 512.xx version of the driver on Windows, and 510.xx on Linux. It will not work properly with older drivers.

T-Rex 0.25.12 

  • (ethash) Improve LHR unlock functionality (dual modes and autolykos2 LHR performance is unchanged)
    Expect about 78-79% in normal mode, and 75% in low power mode (see --lhr-low-power)
  • Change default value of --lhr-autotune-mode parameter to down (used to be full)

Bug fixes:

  • (Linux) Memory temperature is not displayed on some GDDR6X cards

Make sure you remove any --lhr-tune settings you may have in your existing configuration. The miner will calibrate the unlocker and the hashrate should go up to its normal level in about a minute after the miner displays calibration finished message.

Recommended drivers:
Linux – 470.xx or newer
Windows – 512.xx (although 472.xx works fine too)

A few tips if you experience frequent LHR locks:

  1. Make sure you don’t have monitors connected to your LHR cards, or at least turn them off during miner start up to let it calibrate correctly. Avoid using RDP if it puts load on your LHR cards.
  2. Do not delay applying overclock – this will mess up calibration results and the miner will display unrealistically high LHR tune values.
  3. Try reducing memory overclock of the GPU that frequently trips LHR.

T-Rex 0.25.9

  • Allow setting “LHR dual ratio” parameter for ETH+ALPH dual mining,
    e.g. --dual-algo-mode a12:r10:lr12 (dual ratio 10, LHR dual ratio 12)
  • (Linux) Display memory temperature for GPUs with GDDR6X memory type (requires administrative privileges)

Bug fixes:

  • (progpow) Miner frequently disconnects from the pool when mining SERO

T-Rex 0.25.8

  • Improve ETH+ALPH dual mining performance for LHR cards (high power limit / core clock is important to get high ALPH hashrate).
    In order for the miner to re-tune your cards, remove LHR tune values from your config if you previously set them.
  • --lhr-algo parameter is deprecated and is now an alias for --dual-algo

Bug fixes:

  • Miner uses incorrect worker name for the secondary algorithm if --worker2 is set
  • (WebUI) Various fixes around dual mining configuration setup

T-Rex 0.25.6

  • Add ETH+ALPH dual mining support for non-LHR cards.
  • (WebUI) Add an optional “Lock Count” column to track the number of times the GPU hit an LHR lock

Bug fixes:

  • (WebUI) Login sessions are preserved between miner restarts if the watchdog is enabled

T-Rex 0.25.2

  • Add blake3 algorithm (Alephium coin)
  • Add ETH+ALPH dual mining mode for LHR cards (ETH 68% / ALPH 32% by default)

NOTE: solo mining to Alephium nodes isn’t supported

T-Rex 0.24.8

  • Add DNS-over-HTTPS support when resolving mining pool domain names (see --dns-https-server for details)
  • Add an option not to set mining pool domain name in SNI header for SSL connections (see --no-sni)
  • Resolve domain names through SOCKS5 proxy if --proxy is set
  • Display mining pool IP address in console
  • (WebUI) Make the monitoring page layout more compact on mobile phones

Bug fixes:

  • Miner is not creating a log file when --log-path is specified
  • GPU does not get turned off when overheated while mining in dual mode
  • (WebUI) Charts are not scaled correctly when zooming in

T-Rex 0.24.7

Bug fixes:

  • Some command line arguments don’t take precedence over the values set in a config file (e.g. --lhr-autotune-step-size)
  • (WebUI) Performance degradation introduced in 0.24.6
  • (WebUI) Monitoring page shows a blank page if you had 15M or 2H graph views selected while using an older version of T-Rex
  • (WebUI) Impossible to set LHR tune values with decimal point

HiveOS users: many of you complained that your hashrate on LHR cards is fluctuating too much compared to the Windows version. The reason is HiveOS sets "hashrate-avr": 30 for T-Rex causing it to report 30-seconds average hashrate as opposed to 1-minute average (default).
A temporary solution would be to edit your flight sheet and manually add "hashrate-avr": 60 to the “Extra config arguments” field. Otherwise, we’ve been told there will be a HiveOS release that fixes it permanently.