XMRig remains the standard miner for Monero because it is open-source, stable, and supports both command-line configuration and config.json files. If you want to connect a home CPU, a rented server, or a machine that only runs part of the day, XMRig is usually the most direct way to do it. Monero uses RandomX, an algorithm built for modern CPUs rather than dominant ASICs, so the quality of your configuration matters almost as much as the raw power of the hardware.

Download from the right source

Start by downloading XMRig from its official site or public repository and, if you can, verify the binary you receive. The official repository is github.com/xmrig/xmrig. Plenty of websites redistribute miners with hidden changes, extra fees, or outright malware. That precaution is especially important on machines that will mine to the same address for days or weeks. Once it is installed, keep three things ready: the Monero address that should receive the reward, the required worker name, and the pool endpoint. For OwnBlock, the basic format is stratum+tcp://xmr.eu.ownblock.io:4242 with username YOUR_XMR_ADDRESS.WORKER_NAME.

The minimum configuration you need

If you prefer the command line, the basic setup is simple. Set the host, the username containing your address and worker name, and the coin:

bash 
./xmrig -o xmr.eu.ownblock.io:4242 -u YOUR_XMR_ADDRESS.WORKER_NAME --coin XMR

If you prefer config.json, this example is valid JSON and can be copied as-is. The worker name comes after the address with a dot and is required:

json 
{
  "autosave": true,
  "cpu": true,
  "donate-level": 1,
  "pools": [
    {
      "coin": "XMR",
      "url": "xmr.eu.ownblock.io:4242",
      "user": "YOUR_XMR_ADDRESS.WORKER_NAME",
      "pass": "x"
    }
  ]
}

Tune CPU and memory carefully

RandomX needs fast memory and benefits noticeably from huge pages when your operating system allows them. On Linux you can enable them with:

bash 
sudo sysctl -w vm.nr_hugepages=1280

It also helps to set thread count carefully instead of blindly enabling every logical thread. On many systems, using every thread hurts efficiency because of heat, cache pressure, or normal system activity. Start with a reasonable value, monitor power use, temperature, and stable hashrate, and then adjust.

Common connection mistakes and the tweaks that matter

The common mistakes are simple: using an exchange address, forgetting the worker name, confusing the port, or assuming more threads always mean more performance. On OwnBlock, the correct XMRig port is 4242. If you see frequent reconnects, rejected shares, or an unstable hashrate, do not start by changing dozens of flags: check wallet, worker, port, huge pages, and temperature first.

Verify before you leave it running

Before you consider the setup finished, make sure XMRig shows a stable connection, accepted shares, and a reasonably consistent hashrate after the first few minutes. A clean startup matters more than a screenshot showing brief spikes. It also helps to confirm on the pool that the worker appears as expected and that the address is correct. Once that is in place, you have a solid setup to keep refining. If you want to try it on a live pool, you can do that directly at xmr.ownblock.io.

If you want to use this setup in a real environment, open xmr.ownblock.io and verify the wallet, worker, huge pages, and accepted shares before you spend time on fine-tuning.