XDAG is mined by ordinary CPUs — this pool is where their work gets paid
XDAG is a block-DAG: a new main block lands roughly every 64 seconds and the chain is a graph, not a line. The proof of work is RandomX — the same memory-hard algorithm Monero uses — so the hardware that mines it well is the server or desktop CPU you already have. Point XMRig at this pool with your XDAG address as the login; there is no account to create and no form to fill.
Live from /xdag/stats — the same endpoint the dashboard renders. Numbers here are measured, not typed in.
Connect
You need two things: XMRig (the miner) and a base58 XDAG address (where the pool will pay
you). Addresses come from the official wallets linked on xdag.io —
they look like 5nnL…, 26 to 33 characters of an alphabet that also contains
+ and /.
Windows — one line in cmd or PowerShell
xmrig.exe -o stratum+tcp://pool.ion.cool:33347 -u <YOUR_ADDRESS>.<RIG> -p x -a rx/0Grab XMRig from its GitHub releases
(the regular Windows zip — no XDAG-specific fork needed), unpack it anywhere, and run the line
above from that folder. -a rx/0 is plain RandomX: this pool announces exactly that
algorithm in its jobs, and the whole path — connect, share, accept — was verified end-to-end
with stock XMRig before this page was written.
Linux and macOS
./xmrig -o stratum+tcp://pool.ion.cool:33347 -u <YOUR_ADDRESS>.<RIG> -p x -a rx/0Same binary name, same flags; on macOS take the build from the same releases page. First
start takes a minute or two while RandomX builds its dataset — that pause is normal, and after
it the console starts printing accepted lines. Those are real, credited shares.
ADDRESS.rig1, ADDRESS.office — everything after the dot only
names the machine in the statistics. Every rig should get its own suffix, otherwise several
computers pile into one row. Payouts always go to the address itself, never to a rig name.
RandomX was designed so that caches and memory bandwidth, not raw ALUs, decide the speed — GPUs lose their usual advantage here, and mining XDAG on a video card is typically a step backwards per watt. Threads: start with the physical cores, drop one or two if the machine also does other work.
Every share is worth the same target, so a slow CPU simply submits less often than a fast one; nothing is wrong if a small rig goes a few minutes between accepted shares. What does hurt is a rig that restarts constantly: dataset init time is work the pool never sees.
There is no registration and no email — the address you type IS your account. A share credited to a typo is a share paid to an address nobody controls. Copy-paste it; do not retype it.
Miners: what was tested against this pool
XMRig, stock releaserx/0 |
Works — tested. Two minutes on 12 October 2026 produced 8 accepted
lines in the miner's log with no rejections, from the unmodified Windows build you can
grab from the releases page linked above — no fork, no patch, no flag beyond the address |
Any other RandomX minerrx/0 |
Expected to work, not measured. The pool announces plain RandomX and validates the share rather than the binary behind it — we simply publish figures for what we have actually run |
Its share counter is a placeholder that stays at zero, so do not read it as a rejection.
An XDAG share shows up in two places instead: the miner's own accepted line, and
the payment records. This is a known gap in this dashboard — for every other pool on this site
the tables above are read from the pool's counter.
How it pays
| Scheme | Proportional (equal mode) — every payout window splits what the pool earned by each miner's share of the work in that window |
| Payout | From the pool's hot wallet, batched about every ten minutes. The pool signs the transactions itself and submits them to the network — you do nothing, there is no withdrawal button to press |
| Minimum | 3 XDAG — below that the balance carries over to the next window until it clears |
| Fee | 1% — the only cut; it comes off the pool's earnings, not out of your balance afterwards |
| Block pace | A main block about every 64 seconds; the current emission stage pays 64 XDAG per main block, and that reward is the pot the whole window is split from |
| Stratum | pool.ion.cool:33347 — plain TCP, no TLS port |
| Address | base58 only (5nnL…, 26–33 chars). The legacy 32-hex XDAG addresses cannot receive pool payouts — mine to a fresh base58 address |
The pool's own payout address is 5nnLNvpkRPxYAFhPfbcgSLDbAiknqBs8x — you can
watch it on any XDAG explorer to see the payout batches leave.
Things worth knowing before you start
- A pool smooths luck, it does not mint extra coins. XDAG blocks are frequent but their value is staged, and solo mining swings between droughts and windfalls. Pool mining trades a slice of the average (the 1%) for a balance that moves in steps you can plan around.
- The pool holds your coins for minutes, not days. Rewards land on the pool address and are forwarded to you in the next batch once you clear the minimum. That is the trade of hot-wallet payouts: convenience on both sides, so keeping your own large balances in your own wallet stays the right habit.
- The DAG swallows orphaned work differently than a chain does. Shares are recorded the moment they arrive; the accounting already assumes some blocks will not make it into the main DAG — you are paid for accepted shares, not for the pool's optimism.
- One pool is a centralization risk on any young network. The dashboard shows this pool's hashrate against the network's, measured rather than claimed — and a second XDAG pool run by someone else would be good for everyone.
- Your address is your identity here. The lookup on the dashboard answers only for the address you paste, and nothing about your rigs leaves the pool except the counters you see.