ACADEMY
MINING EDITION
MODULE 3
LESSON 3
Advanced Miner Configuration (Qubic.li Client & Alienminer)
By now, you likely have the basics of mining with the Qubic.li client (the standard miner). In this lesson, we’ll explore advanced configuration options that allow you to fine-tune how your miner runs.
Qubic.li Miner (QLI) Advanced Settings: The Qubic.li client is designed to be user-friendly, but it offers plenty of configurability under the hood . You can run it via command-line flags, environment variables, or a config file (appsettings.json). If you made a Qubic.li pool account, the easiest route is to use the Web Client Setup Configurator on the pool site, which generates a ready-made config string or token for you . This configurator lets you pick CPU vs GPU mining, number of threads, and whether to enable Monero idle mining, then provides an Access Token or config that you plug into the miner . For example, you might get a one-line command like:
This would launch the miner pointing at your Qubic address with N CPU threads . Alternatively, you can save these settings in appsettings.json in the same folder as the miner. An example config for a 10-thread CPU miner might look like:
This file approach is convenient for persistent rigs – just double-click the client and it will read the JSON. The Qubic.li client also supports Docker and even a systemd service on Linux for running in the background (ideal for headless servers). Advanced users can set up the miner to auto-start at boot using these methods, ensuring you’re always online.
Config Flags to Know
Some useful QLI config flags include CpuThreads (how many CPU threads to use) , gpu and gpuVersion (to enable GPU mining and specify CUDA vs AMD) , Alias (a custom name for your worker, shows on the pool dashboard) , and pps (true/false for Pay-Per-Share vs solo mode in the pool) . Pay-Per-Share (PPS+) means you get steady income based on work contributed, smoothing out luck . Solo means you only get reward if your miner actually finds a valid solution, which is higher variance but potentially higher payout if you’re powerful. Most beginners stick to PPS, but advanced miners might go solo if they have a lot of hashpower.
Idle Mining (XMR) Settings
By default, the Qubic.li client’s Monero mining module is enabled and will kick in during idle periods . Advanced users can choose to disable this if, for example, you prefer your own method of using idle time or want to reduce power usage when no Qubic tasks are available. In the config, the xmrSettings block has a flag disable (set it to true to turn off XMR mining) . You can also point the XMR miner to different pool endpoints if needed – Qubic.li provides regional XMR stratum addresses for optimal latency (EU, US, HK, SG, etc.), but typically you won’t need to touch this. Note that currently GPU mining for XMR is not supported in the client (it’s CPU only for the idle mining). The XMR module uses a variant of XMRig under the hood, and you could pass custom parameters to it (e.g., limit it to 1 thread) via the customParameters field . However, it’s generally recommended not to modify the XMR settings unless you really know what you’re doing – the defaults are optimized to convert idle time into extra QUBIC smoothly.
Clarification: This fallback is integrated; external switch scripts are discouraged.
Apool
Apool is another major community-developed option for Qubic mining. It provides its own miner and dashboard, supporting both solo and pooled setups. Apool’s client is known for high stability, strong hashrate performance, and active development updates. Many miners use it as an alternative or companion to Qli, depending on preferred interface and reward structure.
Benchmarking & Logging
How do you know if your tweaks are helping? Qubic.li typically displays performance info in the console (e.g., iterations per second, shares found, etc.). If you have a pool account, the pool dashboard also shows your current hash rate (though in Qubic’s case it might show as “training performance” rather than a hash hash rate) and your contribution relative to others. A good practice is to change one setting at a time and let the miner run for a while (several minutes at least) to gauge the steady-state performance.
For instance, try CpuThreads=16 vs CpuThreads=32 and compare the output. The logging in Qubic.li client is fairly minimal by default (mostly status updates and any warnings/errors). If something goes wrong, the client will drop error logs in the log/ folder with timestamps .
Advanced users can increase verbosity by running the client in a console to see all messages, or by enabling debug flags if available (check Qubic’s GitHub for any debug build instructions). The legacy Computor software had function keys to toggle detailed logging (F7, F8, F9) , but in the current pool miner those aren’t used. Instead, rely on the log files for troubleshooting (we’ll cover common issues in Lesson 5).
If you’re running Apool, be prepared for a more bare-bones output – you might need to manually update config files or even recompile for new epochs. Always document your changes and results so you can roll back if a “tweak” makes things worse.