What mining options are available using only my GPU?

[SolfataraEmit]

How can I mine with my GPU? How can I ensure I only mine using SHA3X?

[SolfataraEmit]

Instructions for GPU solo mining Tari

The following instructions are a simple guide to solo mining with the GPU using the Tari suite. The instructions cover solo mining with glytex (SHA3X) and graxil for pool-mining (SHA3x). LolMiner instructions are upcoming.

The contents are as follows:

• Setting up Minotari
  • Minotari Base Node
  • Minotari Console Wallet (optional)
• Solo-mining with Glytex (SHA3x)
  • Resource Utilization
  • Customisation
• Pool-mining with Graxil (SHA3x)
• Solo mining with LolMiner (Coming Soon)
• Troubleshooting
  • MacOS: "Command" Not Opened. Apple could not verify "Command"

Prerequisites

In order to run Tari, you will require the following applications, as well as your text editor of choice for editing configuration files.

• The Tari suite, which can be downloaded here. For stability, please use the latest released version and avoid the pre-releases.
• A Tari Wallet Address
• glytex, located here: https://github.com/tari-project/glytex/releases
• alternatively, graxil, located here: https://github.com/tari-project/graxil/releases

LolMiner instructions are a work in progress.

Setting up Minotari

Download the Tari suite for your operating system of choice, and unzip the contents to a folder of your choice.

Next, open your command line interface (CLI) on Windows, Terminal on MacOS/Linux) and navigate to the folder. It'll typically be something like this:

cd tari
ls

Typing ls will list all the Tari binaries we'll require. The ones we'll be using are:

• minotari_node
• minotari_console_wallet

Minotari Base Node Setup

To set up the Minotari Base Node, ensure you are still in the folder with the Tari binaries, then run the following

./minotari_node -b <nodebasefolder>

This will start the process and store the configuration files in the you provided.

Initializing logging according to "minotarinodesettings/mainnet/config/base_node/log4rs.yml"
Node config does not exist.
Would you like to mine (Y/n)?
NOTE: this will enable additional gRPC methods that could be used to monitor and submit blocks from this node

Select Y to both question

• "Would you like to mine?", and,
• "Node Identity does not exist. Would you like to create one?"

This will start the node, which will begin syncing. This will use the default settings for the base node:

• The base node's default GRPC address will be http://127.0.0.1:18142
• Wallet will connect to the base node via http://127.0.0.1:9000

Note: Make sure you are connected to the right network. By default, if you are using the main release, it will be mainnet. If you are using one of the pre-releases, it will likely be esmeralda, which is the test network. You can confirm you are on the correct network by assessing the messages being displayed in the terminal (the below as an example):

11:25 v4.9.0 mainnet State: Syncing blocks: (01dc53343af8e28b) 26937/60367 (44%) 3.28 blks/s, latency: 305.12ms Tip: 26938 (Thu, 12 Jun 2025 09:12:07 +0000) Mempool: 0tx (0g, +/- 0blks) Connections: 17|0 Banned: 0 Messages (last 60s): 99 Rpc: 0/100 ⚡️ 608.93ms

If you wish to configure the node with your own preferences, please refer to the Custom Configuration section.

minotari_node needs to be open and running for mining to work

Minotari Console Wallet (Optional)

If you do not have a Minotari wallet address, you will need to create one. This can be done either via running Tari Universe or creating a wallet through the minotari_node binary. If you already have a Minotari wallet address, you can proceed to the Minotari Merge Mining Proxy setup section.

The following instructions assume you will use the Minotari Console Wallet.

From the same folder, run the following command. Note that the should be different from the

./minotari_console_wallet -b <walletbasefolder>

Select Y to the question, "Would you like to mine (Y/n)?"

You will be then presented with a list of options, as per below. Select 1 and press ENTER

Console Wallet

1. Create a new wallet.
2. Recover wallet from seed words or hardware device.
3. Create a read-only wallet using a view key.
>> 

Enter in your desired wallet passphrase. This is required for accessing the wallet locally via minotari_console_wallet. If you enter a weak password, you will be warned that this is the case and provided recommendations to improve it.

Note: Be sure to note the passphrase as you will require it to access your wallet locally.

Select N to the question, "Would you like to use a connected hardware wallet?"

You will be presented with your seed words. These are essential if you wish to recover your wallet. You cannot recover the wallet without them. Note them down, then type confirm and press enter.

This will launch into the wallet. To confirm that you are connected to your base node (and not a fallback server), check the bottom-right corner of the interface. You'll see the "Connected Base Node ID:" and your local address. Default value will be http://127.0.0.1:9000.

Confirm that you are on the right network. Mainnet will be displayed at the lower-right of the application.

Press right arrow button twice to access the Send tab, and note the one-sided address. Be sure that your CLI is maximized; if the terminal window is too small, it may cut off a portion of the address..

Once this has been noted, you can close the wallet. It is not necessary for the wallet to be active for you to mine to the wallet. Wallet can be relaunched when required to confirm deposit of mining rewards.

If you wish to configure the node with your own preferences, please refer to the Custom Configuration section.

Solo-mining with glytex (sha3x)

Download the latest release here

Be sure to select the version that is appropriate for the network you want to mine for. In most cases, you'll want mainnet

Unzip, then run the following command:

• If you're running the miner on the same local machine where the MinoTari node is: ./glytex --tari-address <address> --engine OpenCL --http-server-port <desired_glytex_http_port>. This should automatically locate the MinoTari node if using default settings.
• If the MinoTari node has a different address or is located remotely: ./glytex --tari-address <address> --engine OpenCL --tari-node-url <ipaddress>:<port> --http-server-port <desired_glytex_http_port>

These should start the miner. By default, glytex uses all compatible GPUs and automatically optimizes mining parameters for about one second per cycle, with minimal CPU and memory usage.

Sample Output

./glytex --tari-address f2BcXXm8wrezYAvqH4KcXAEKP6srsiGLjjBVAYyUAEiBFFPU9BKYzqSaupz44ZA9vTiYZbAebjhKMernkzhj6kvS1nF --engine OpenCL --http-server-port 9696
Device: Apple M1 is available: true is excluded false
Device indexes to use: 1 from the total number of devices: 1
Device index: 0
Starting thread for device index: 0
Connecting to http://127.0.0.1:18142
Connecting to http://127.0.0.1:18142
Starting HTTP server at http://127.0.0.1:9696
Starting HTTP listener address Ok(127.0.0.1:9696)
Current height: 69659, P2Pool height: 0 time: 1s
Refreshing block template
Getting block template
Block template refreshed
Current height: 69659, P2Pool height: 0 time: 1s
Current height: 69659, P2Pool height: 0 time: 2s
[Thread:0] total 55,050,240 grid: 1024 max_diff: 14,852,555, target: 820,914,370 hashes/sec: 27,525,120
Current height: 69659, P2Pool height: 0 time: 3s
Current height: 69659, P2Pool height: 0 time: 4s
[Thread:0] total 110,100,480 grid: 1024 max_diff: 23,439,791, target: 820,914,370 hashes/sec: 27,525,120
Current height: 69659, P2Pool height: 0 time: 5s
Current height: 69659, P2Pool height: 0 time: 6s
[Thread:0] total 165,150,720 grid: 1024 max_diff: 23,439,791, target: 820,914,370 hashes/sec: 27,525,120
Current height: 69659, P2Pool height: 0 time: 7s
Current height: 69659, P2Pool height: 0 time: 8s
[Thread:0] total 221,118,464 grid: 1024 max_diff: 23,439,791, target: 820,914,370 hashes/sec: 27,639,808
Current height: 69659, P2Pool height: 0 time: 9s
Current height: 69659, P2Pool height: 0 time: 10s
[Thread:0] total 277,086,208 grid: 1024 max_diff: 23,439,791, target: 820,914,370 hashes/sec: 27,708,620
Current height: 69659, P2Pool height: 0 time: 11s
Current height: 69659, P2Pool height: 0 time: 12s
[Thread:0] total 332,136,448 grid: 1024 max_diff: 23,439,791, target: 820,914,370 hashes/sec: 27,678,037
Current height: 69659, P2Pool height: 0 time: 13s
Current height: 69659, P2Pool height: 0 time: 14s
[Thread:0] total 387,186,688 grid: 1024 max_diff: 23,439,791, target: 820,914,370 hashes/sec: 27,656,192
Current height: 69659, P2Pool height: 0 time: 15s
Current height: 69659, P2Pool height: 0 time: 16s
output and diff 424168480 70623
Block submitted
Current height: 69660, P2Pool height: 0 time: 17s
Refreshing block template
Getting block template
Block template refreshed
Current height: 69660, P2Pool height: 0 time: 1s

Congratulations, you're now mining with glytex. You can use the minotari_console_wallet to confirm your rewards.

How to Customise glytex Resource Utilization

You can customize resource utilization with additional command line options or configuration file entries. Key options:

Command-Line Flags

--block-size <value>
Sets the number of threads per block for GPU mining.
--grid-size <value>
Sets the grid size for GPU mining (number of blocks).
--iterations-per-cycle <value>
Controls how many iterations the miner does in each mining cycle.
--engine <OpenCL|Metal>
Select GPU engine (OpenCL for most GPUs, Metal for Apple devices).
--gpu-status-file <path>
Specify a custom GPU status file to control which GPUs are used.
--detect
Forces device detection and status file creation.
--find-optimal
Runs a benchmark to find the optimal grid size for your device.
--benchmark
Runs a performance benchmark instead of mining.

Custom Configuration

Most of Tari's applications allow you to define custom values, such as choosing your desired base node address and port, or running on a particular network.

This can be done in two ways. When running the binaries, the tools create a folder with the config.toml file. Users can edit these to allow for custom configurations

When reviewing the config.toml, settings related to the specific section fall under their appropriate [block]. As an example, the base node settings will fall under the [base_node] block, with sub-settings falling under [base_node.subsetting]

Alternatively, users can pass the variables via the command line using the -p argument. Below is an example of minotari_node being launched with custom configuration values. Note that these override the specific values in the config.toml, not the entire configuration file:

./minotari_node \
  -p base_node.http_wallet_query_service.port=9000 \
  -p base_node.http_wallet_query_service.external_address=http://127.0.0.1:9000 \
  -p base_node.mining_enabled=true \
  -p base_node.second_layer_grpc_enabled=false \
  -p base_node.grpc_enabled=true \
  -p base_node.grpc_address=/ip4/127.0.0.1/tcp/18142

Pool-mining using graxil (sha3x), either in pool mode or solo mode

We recommend using graxil for pool-mining via the GPU. You can download graxil here: https://github.com/tari-project/graxil

Unzip or build the release (if building, be sure to set the correct feature flag for GPU usage) and then run graxil using the following command:

You have two options here. If you use the solo: prefix with prefix with your wallet address, you are mining in "solo" mode via the pool and only get paid when you personally find a block. Without the solo: prefix, you are mining in regular pool mode and earn smaller, more frequent payouts based on your share of the pool's total work.

The example we will use is using the solo mode.

Run the following command:

./graxil -u solo:<your_walletaddress> --worker <your_identifier> -g --algo sha3x --pool <probably_some_luckypool_address>

By default, graxil uses some pre-defined default values for the GPU settings. You can adjust these by passing the relevant arguments when you run it (e.g. --gpu-intensity: number between 0-100)

If you are running it successfully, you should see something along the lines of the following:

./graxil -u solo:12A3JmWWhfyV3nBDh4bt6PXTR4tWenfydHC4Qr3xWDasNkPEzH3ob79huPGSrbnL34riEq2fNC1nBjHHQ4RZ7oEBGxQ --worker workeridentifiermagic -g --algo sha3x --pool ca.luckypool.io:6118
Initializing logging according to "/Users/Definitelyarealuserforsure/Tari Versions/tari5.0.1esme/graxil/logs/graxil/log4rs_config.yml"
12:03 INFO  🚀 Starting SHA3x Miner - GPU-ONLY Mode
12:03 INFO  📍 Pool: ca.luckypool.io:6118
12:03 INFO  💳 Wallet: solo:12A3JmWWhfyV3nBDh4bt6PXTR4tWenfydHC4Qr3xWDasNkPEzH3ob79huPGSrbnL34riEq2fNC1nBjHHQ4RZ7oEBGxQ
12:03 INFO  👷 Worker: workeridentifiermagic
12:03 INFO  🎮 Mode: GPU-only mining (385+ MH/s beast mode!)
12:03 INFO  🎮 GPU Settings - Intensity: 100%, Batch: None, Power: None%, Temp: None°C
12:03 INFO  Creating GPU manager with settings: intensity=100%, batch=None
12:03 INFO  🎮 Creating GPU miner with settings: intensity=100%, batch=None
12:03 INFO  Setting GPU manager settings: intensity=100%, batch=None, power=None%, temp=None°C
12:03 INFO  🎮 Initializing GPU mining...
12:03 INFO  🎮 GPU Settings: intensity=100%, batch=None, power=None%, temp=None°C
12:03 INFO  Found 1 OpenCL platform(s)
12:03 INFO  Detected OpenCL device 0: Apple M1 (Platform: Apple)
12:03 INFO  Successfully detected 1 OpenCL GPU device(s)
12:03 INFO  ✅ Found suitable GPU: Apple M1 (CU: 8, WG: 256, MEM: 5.3 GB, Type: Integrated)
12:03 INFO  Initializing OpenCL engine for Apple M1 with GPU settings
12:03 INFO  🎮 GPU Settings: Intensity=100%, Batch=None, Power=None%, Temp=None°C
12:03 INFO  OpenCL program built successfully for Apple M1
12:03 INFO  ✅ OpenCL engine initialized for Apple M1 (CU: 8, WG: 256)
12:03 INFO  🚀 GPU Apple M1 ready - estimated 96.0 MH/s with 100% intensity
12:03 INFO  ✅ GPU mining initialized with 1 device(s)
12:03 INFO  🎯 Total estimated GPU hashrate: 96.0 MH/s (100% intensity)
12:03 INFO  🔢 GPU thread IDs: 0 to 0
12:03 INFO  🎮 GPU miner created with 1 device(s) and 100% intensity
12:03 INFO  ✅ GPU Settings Applied: intensity=100%, batch=None
12:03 INFO  🔗 WebSocket endpoint: ws://localhost:8080/ws
12:03 INFO  🚀 Starting GPU mining with 100% intensity - unleashing the beast!
12:03 INFO  🌐 Starting GPU web dashboard server...
12:03 INFO  💡 Add --web flag to enable real-time web dashboard
12:03 INFO  🔗 WebSocket endpoint: ws://localhost:8080/ws
12:03 INFO  ✅ GPU miner connected to SHA3x pool
12:03 INFO  📤 Sent GPU miner login request (100% intensity)
12:03 INFO  🎮 GPU miner login request sent
12:03 INFO  🎮 Starting GPU mining with settings: 1 GPU(s) | 96.0 MH/s | 100% intensity | batch: auto
12:03 INFO  🎮 Starting 1 GPU mining thread(s) with 100% intensity
12:03 INFO  🎮 Launching GPU mining thread 0 for Apple M1 (~96.0 MH/s, 100% intensity)
12:03 INFO  🚀 GPU mining threads started with 100% intensity!
12:03 INFO  🚀 GPU miner fully operational - delivering 385+ MH/s with 100% intensity!
12:03 INFO  📊 GPU MINING DASHBOARD - cc2ad48d98e00a06
12:03 INFO  🎮 GPU mining thread 0 starting for Apple M1 with 100% intensity
12:03 INFO  📊 MINER DASHBOARD - cc2ad48d98e00a06
12:03 INFO  ├─ Algorithm: Sha3x
12:03 INFO  ├─ Current Hashrate: 0.00 H/s
12:03 INFO  ├─ Session Avg: 0.00 H/s
12:03 INFO  ├─ Total Work: 0
12:03 INFO  ├─ Top 5 Shares: None
12:03 INFO  ├─ Shares: 0/0 (0.0% accepted)
12:03 INFO  ├─ Rejected Shares: 0
12:03 INFO  ├─ Work Efficiency: 0.0%
12:03 INFO  ├─ Average Luck: 0.00x
12:03 INFO  ├─ Share Rate: 0.00 shares/min
12:03 INFO  ├─ Time Since Last Share: 0s
12:03 INFO  ├─ Average Share Time: 0s
12:03 INFO  ├─ Session Time: 0s
12:03 INFO  ├─ Active Threads: 0/1
12:03 INFO  ├─ Current Difficulty: 0
12:03 INFO  └─ GPU Status: No GPU detected
12:03 INFO  Initializing OpenCL engine for Apple M1 with GPU settings
12:03 INFO  🎮 GPU Settings: Intensity=100%, Batch=None, Power=None%, Temp=None°C
12:03 INFO  OpenCL program built successfully for Apple M1
12:03 INFO  ✅ OpenCL engine initialized for Apple M1 (CU: 8, WG: 256)
12:03 INFO  🎮 GPU thread 0 initialized - starting CONTINUOUS mining with batch size 100 (100% intens

Congratulations, you are now pool-mining using SHA3X via graxil.

Solo Mining with LolMiner

This is a relatively new addition and instructions will be updated once the correct instructions are confirmed.

Troubleshooting

MacOS: "Binary" Not Opened. Apple could not verify "Binary"

Occasionally, MacOS will indicate that it is unable to verify the application when you attempt to run it. To remove this, you can use two commands

# Make it executable
chmod +x ./binary_name

# Remove quarantine attribute (if it was downloaded from the web)
xattr -d com.apple.quarantine ./binary_name

This should allow you to run the binary.

Note: Before you do this, you should ensure that the application you have downloaded is correct and from the official source.