XMRig on GitHub
What lives in the official XMRig repository, how to read its releases and issue tracker, and how to tell the genuine project apart from the many copies and repackages that borrow its name.
What you will find there
| Section | Contents |
|---|---|
| Code | Full C++ source of the miner, build scripts and CMake configuration. |
| Releases | Version history with compiled archives for Windows, Linux, macOS and FreeBSD, plus checksums. |
| Documentation | Project documentation covering configuration keys, build instructions and algorithm support. |
| Issues | Bug reports and questions from users, and the maintainers' answers. |
| Pull requests | Proposed changes, including ones that were declined and why. |
| Related repositories | The stratum proxy and supporting projects under the same organisation. |
Using the release page well
Releases are ordered newest first. Each entry carries a changelog, the attached archives and their checksums. Read the changelog before updating: algorithm changes, backend fixes and configuration-format notes all appear there, and they explain most "it worked yesterday" reports. Pre-releases are labelled as such and are meant for testing.
Using the issue tracker well
Search closed issues first — most Windows questions, from large-page failures to driver problems, have been answered already. If you do open one, include your version, Windows build, CPU, the relevant part of config.json with the wallet removed, and the first thirty lines of the startup log. A report without the log is a guess.
Telling the official project from imitations
- The organisation name is
xmrig; forks live under other accounts even when the repository name matches. - Official Windows releases are plain archives. There is no official installer, no setup wizard and no "pro" edition.
- Every archive has a published checksum. Verify it — see the download guide.
- Download links that route through a file-sharing host, a shortened URL or an advertising interstitial are not the project's.
- A fork is not automatically malicious, but it is maintained by someone else and carries someone else's changes. Treat it accordingly.
Source code, for those who want it
Cloning the repository and building locally is the strongest guarantee you can give yourself about what you are running. It also lets you change build-time options, including the developer fee, which the project documents openly. A C++17 compiler, CMake and the listed dependencies are all it takes on Windows.
Repository questions
Where is the official XMRig GitHub repository?
At github.com/xmrig/xmrig. The proxy has its own repository in the same organisation.
Is this site connected to that repository?
No. This is an independent informational site; we link to the project rather than mirror it.
Which version should I use?
The latest stable release, unless a changelog entry gives you a reason to stay on an older one.