Download DagCore Miner

Download

Both kits are published on GitHub, on the repository's Releases page: the newest release is at the top, and its files are listed under Assets, one archive for Linux and one for Windows, named after the version. The current version is 1.3.1. Older versions and every release's notes are on the same page.

Each archive unpacks to one folder with the archive's own name. The Linux one, dagcore-miner-<version>-linux-x64, holds dagcore-miner (graphics card and processor), dagcore-miner-cpu (processor only), the GPU kernel dagcore_gpu.cl, the dashboard folder, config.env.example, LICENSE, SHA256SUMS and README.md, a getting-started guide written for the terminal (less README.md): making config.env, starting the miner directly or in the background and stopping it, the dashboard and its control token, several cards, and what to do when something goes wrong.

The Windows one, dagcore-miner-<version>-windows-x64, holds dagcore-miner.exe (graphics card and processor), dagcore-miner-cpu.exe (processor only), the GPU kernel dagcore_gpu.cl, the dashboard folder, config.env.example, start.bat, readme.html, a getting-started page that opens offline with a double-click, LICENSE, and SHA256SUMS, the list of checksums used below.

Keep dagcore_gpu.cl in the same folder as the miner. The GPU build loads it from there when it starts.

The source code is in the same repository, github.com/dagcore/dagcore-miner, with what changed in each version in its CHANGELOG.md.

Requirements

• A BDAG wallet address on chain 1404: 0x followed by 40 hexadecimal characters. Rewards are paid to it, so copy it exactly.
• A 64-bit x86 computer. ARM machines, including Apple Silicon and Raspberry Pi, are not supported.
• Linux: glibc 2.34 or newer, which means Ubuntu 22.04, Debian 12, or a later release of either.
• Windows: 64-bit Windows 10, version 1803 or later. Nothing else to install for the processor build; the .exe brings no DLLs of its own.
• For graphics-card mining, the card maker's driver with OpenCL. NVIDIA's driver includes it on both systems. On Windows, AMD's Adrenalin and Intel's graphics drivers include it too. On Linux, AMD needs ROCm or another OpenCL driver for your card, and Intel needs the Intel compute runtime (intel-opencl-icd on Debian and Ubuntu). The Linux GPU build also needs the OpenCL loader, libOpenCL.so.1 (package ocl-icd-libopencl1).
• For the power and clock controls in the dashboard, an NVIDIA card. Mining itself does not need them.

On Linux, clinfo lists every OpenCL device the system can see. If your card is not in its output, the miner will not see it either, and the fix is the driver, not the miner.

Check the files

Every release carries SHA256SUMS: one line per file, with the file's SHA256 sum and its name. It is inside each archive, next to the files it lists. A SHA256 sum is a fingerprint: change a single byte of a file and its sum comes out completely different. Checking the files against that list tells you each one arrived whole and is the file that was built for the release. Do it before the first start.

On Linux

Set V to the version you downloaded (1.3.1 is the newest as this is written; use the number in the archive's name if the Releases page shows a newer one), then unpack the archive and go into the folder it creates:

V=1.3.1
tar -xzf dagcore-miner-$V-linux-x64.tar.gz
cd dagcore-miner-$V-linux-x64
sha256sum -c SHA256SUMS

Every line must end in OK. FAILED means that file is damaged or not the one released.

On Windows

Open PowerShell in the unpacked folder, the one that holds dagcore-miner.exe and SHA256SUMS (in File Explorer, Shift + right-click inside the folder, then Open PowerShell window here, or Open in Terminal). To check a single file, work out its sum:

Get-FileHash .\dagcore-miner.exe -Algorithm SHA256

and compare the Hash column with that file's line in SHA256SUMS, which opens in Notepad. PowerShell prints the sum in capitals; that makes no difference. To check every file in the list at once:

Get-Content .\SHA256SUMS | Where-Object { $_.Trim() } | ForEach-Object {
    $sum, $name = $_.Trim() -split '\s+\*?', 2
    $hash = (Get-FileHash -LiteralPath $name -Algorithm SHA256 -ErrorAction SilentlyContinue).Hash
    if ($hash -eq $sum) { "OK      $name" } else { "FAILED  $name" }
}

Every line must start with OK.

If something fails

Do not run it. Delete what you downloaded, and the unpacked folder, download it again and check again; a download that was cut short is the usual cause. If a fresh download still fails, tell us on Telegram or through the contact form.

What this check proves, and what it does not: SHA256SUMS comes from the same release as the files it describes, so it catches a damaged or incomplete file, not a deliberately altered release, which would carry altered sums too. It is not a digital signature. The release page on GitHub also shows a sha256 next to each asset; comparing the archive you downloaded against it, with sha256sum on Linux or Get-FileHash on Windows, checks the download itself before you unpack it.

Set it up on Linux

Unpack the Linux archive and check it as above; the commands there leave you in its folder, dagcore-miner-$V-linux-x64. The kit's README.md covers everything below in more detail, including running the miner in the background with config.env.

With an NVIDIA card: the installer

The installer checks the machine, asks for your wallet address, takes the DagCore pool as the default, builds the miner, sets it up as a service that starts at boot, and tells you where the dashboard is. It runs from the repository:

git clone https://github.com/dagcore/dagcore-miner.git
cd dagcore-miner
sudo ./install.sh

To see what it would do without changing anything, run ./install.sh --dry-run first. The installer looks for an NVIDIA card and stops if it does not find one; on other hardware, start the miner from the archive by hand, as below.

With an AMD or Intel card: by hand

In that folder, give the miner your wallet address; everything else defaults to the DagCore pool. --dashboard-dir serves the dashboard from the folder that came in the archive, and the two variables keep the dashboard's control token and saved tuning in the same folder, which a normal user can write; without them it mines just the same, but the dashboard can only show, not change anything:

DAGCORE_TOKEN_FILE=$PWD/api-token \
DAGCORE_OVERRIDES_FILE=$PWD/overrides.env \
    ./dagcore-miner --wallet 0xYOURADDRESS --dashboard-dir "$PWD/dashboard"

Replace 0xYOURADDRESS with your own address. On start it prints the card it picked, in a line that begins [DagCore GPU] GPU 0:. A machine with more than one OpenCL driver, such as Intel graphics next to a separate card, has more than one platform; if it picked the wrong one, add --gpu-platform 1. With more than one card, see below. The dashboard is then at http://localhost:8881.

Processor only

DAGCORE_TOKEN_FILE=$PWD/api-token \
DAGCORE_OVERRIDES_FILE=$PWD/overrides.env \
    ./dagcore-miner-cpu --wallet 0xYOURADDRESS --threads -1 --dashboard-dir "$PWD/dashboard"

--threads -1 uses half of the processor's logical cores; a number sets them exactly. Stop the miner with Ctrl+C.

Set it up on Windows

1. Unpack the zip (right-click it, Extract All). Extract All proposes a folder named after the zip, and the zip already holds one of that name, so the kit ends up one level down, in dagcore-miner-<version>-windows-x64\dagcore-miner-<version>-windows-x64: the inner folder, the one with dagcore-miner.exe in it, is the kit. Put it somewhere you can write to, renamed if you like: for example C:\DAGCore, not Program Files. The miner keeps its settings in its own folder, next to the .exe.

2. Add your wallet. Rename config.env.example to config.env, open it in Notepad, and put your address after WALLET=:

WALLET=0xYOURADDRESS

The pool, stratum.dagcore.net on port 3334, is already the default. For the processor-only dagcore-miner-cpu.exe, also set THREADS=-1 (half the cores). Leave the rest as it is.

3. Start it. Double-click dagcore-miner.exe to mine on the graphics card, or dagcore-miner-cpu.exe for the processor only. Or run it from PowerShell or a Command Prompt, with the wallet on the command line instead of in the file:

C:\DAGCore\dagcore-miner.exe --wallet 0xYOURADDRESS

For the processor build, add --threads -1 for half the logical cores, or a number for exactly that many. On a machine with Intel graphics next to a separate card, --gpu-platform 1 picks the other OpenCL platform if the first line the miner prints names the wrong device.

4. Let it through. The program is not code-signed, so Windows SmartScreen may say it protected your PC; choose More info, then Run anyway. Do this only after the check above has passed. The first time it starts, Windows may also ask whether to allow it network access; it needs that to reach the pool.

5. Open the dashboard at http://localhost:8881. Stop the miner with Ctrl+C or by closing its window; either way it shuts down cleanly.

Tuning an NVIDIA card on Windows

The power limit and clock locks work from the dashboard only when the miner runs as administrator: start it with start.bat, which asks Windows for that, instead of double-clicking the .exe. Without it the miner mines the same; only those controls are unavailable. Clock offsets cannot be set from the miner on Windows, because the driver refuses them: tune the memory with MSI Afterburner on NVIDIA, or AMD Software: Adrenalin Edition on AMD, and the miner shows the clocks that result.

There is no installer and no Windows service: the miner runs while its window is open. readme.html in the folder walks through the same steps, and more, without needing the internet.

More than one graphics card

By default the miner uses only the first card. Hashrate adds up across cards, so on a rig with several, use all of them:

./dagcore-miner --wallet 0xYOURADDRESS --gpu-device all

or choose them by number, here the first two:

./dagcore-miner --wallet 0xYOURADDRESS --gpu-device 0,1

On Windows it is the same option after dagcore-miner.exe. To keep the choice, set GPU_DEVICE=all or GPU_DEVICE=0,1 in config.env instead. On Linux, add --dashboard-dir "$PWD/dashboard" as in the setup above.

The numbers are the order in which the miner names the cards when it starts: GPU 0: …, GPU 1: …. GPU_INTENSITY takes one value for every card or one per card in the same order, for example GPU_INTENSITY=80,60. The cards counted are those of one OpenCL platform, and every maker's driver is a platform of its own; --gpu-platform picks another.

With more than one card, the dashboard's power and clock controls are off, and it says why: the miner cannot yet tell which card the driver means by each number, and a power limit on the wrong card is worse than none. Mining on all of them is unaffected.

Licence and attribution

DagCore Miner is free and open source under the MIT licence. You may use, copy, change and pass it on, including commercially, as long as the copyright notice and the licence travel with it. It comes with no warranty.

It is derived from DagTech Miner by Dawie Nel / DagTech Ltd, who remain the copyright holders of the original work: the scrypt engine, the OpenCL kernel and the Stratum client are theirs. DagCore added the Linux and Windows packaging, the dashboard and its control API, and a series of fixes.

Copyright (c) 2024-2026 DagTech Ltd / Dawie Nel
Portions Copyright (c) 2026 DagCore Community

MIT License

Copyright (c) 2024-2026 DagTech Ltd / Dawie Nel
Portions Copyright (c) 2026 DagCore Community

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

The same text is the LICENSE file in each download and in the repository. The dashboard uses the IBM Plex Mono typeface, © IBM Corp., under the SIL Open Font License 1.1.

DagCore Miner is a community project. It is not made or endorsed by BlockDAG Network.