
An XDAG mining pool accepts RandomX work from miners and tracks rewards against an XDAG address. The main choice on XDAG.ORG is solo versus equal distribution. Both modes list the same fee, but they produce very different payout patterns.
XDAG is a mineable cryptocurrency built around a directed acyclic graph. Its roadmap records the network’s move from sha256d to RandomX.
For miners, that change determines which software and hardware path to follow. The project site publishes a CPU miner link, while the current XDAG.ORG FAQ directs manual pool users to XMRig. Older guides that describe sha256d mining refer to an earlier stage of the network.
RandomX performance still varies between processors. Cache, memory, thread settings, cooling, and background workloads can change a machine’s sustained hashrate. Benchmark the computer you plan to use instead of estimating results from its model name alone.
Current XDAG pool documentation identifies RandomX as the mining algorithm and XMRig as the manual mining option.
XDAG.ORG currently publishes four Stratum endpoints. They belong to one operator and offer two payout modes.
| Endpoint | Mode | Published fee | Minimum payout |
|---|---|---|---|
stratum.xdag.org:23655 |
Solo | 2.00% | 3 XDAG |
stratum.xdag.org:23656 |
Equal distribution | 2.00% | 3 XDAG |
stratum.xdag.org:24655 |
Solo | 2.00% | 3 XDAG |
stratum.xdag.org:24656 |
Equal distribution | 2.00% | 3 XDAG |
The published fee does not distinguish these endpoints. Select one by payout mode, then confirm its status on the live dashboard before connecting.
The dashboard also shows changing fields such as endpoint hashrate, workers, estimated block time, synchronization status, and software version. Do not copy those live values into a long-term profitability calculation.
The XDAG.ORG FAQ states that an address becomes eligible for payment after accumulating 3 XDAG. It says payment follows within the next 10 minutes. This threshold applies to XDAG.ORG; another operator may use different rules.
| Mode | Reward rule | Typical payout pattern | Variance |
|---|---|---|---|
| Equal distribution | Rewards follow contributed hashrate when the pool finds a block | Smaller credits accumulated over multiple pool blocks | Lower |
| Solo | The miner receives the full reward only after finding a block | Unpaid intervals followed by a possible full reward | Higher |
The XDAG.ORG FAQ says main blocks are found across the network every 64 seconds. That network interval does not mean an individual solo miner receives a reward every 64 seconds.
A solo miner must submit the work that finds a block. Its chance depends on its hashrate relative to competing miners. A low-hashrate worker can therefore run for a long period without receiving a reward.
Equal distribution spreads each pool reward according to contributed hashrate. A small worker receives a fraction rather than the full reward, but it does not need to find the block by itself.
Equal mode changes how the pool allocates rewards. It does not increase the RandomX work produced by the CPU.
One or two CPUs will usually provide more observable feedback on an equal-distribution endpoint. Solo mode suits miners who understand and can tolerate long unpaid intervals.
Set up an XDAG wallet before configuring the miner. The pool uses the receiving address to record shares and send payments.
Do not assume that an exchange deposit address accepts direct mining payouts. Deposit availability and address requirements can change. Check the exchange’s current XDAG deposit page before using one.
The pool account is tied to the submitted address. An incorrect address can cause subsequent rewards to be associated with a wallet you do not control.
The current XDAG.ORG FAQ links to XMRig for manual mining. The pool also offers a generated Windows package for each endpoint.
For an equal-distribution Windows setup:
XDAG_ORG_EQUAL.BAT file as directed on the setup page.stratum.xdag.org:23656 and begins submitting accepted shares.The advanced setup page identifies stratum.xdag.org:23656 as the XMRig Stratum endpoint. The dashboard publishes the corresponding ports for the other modes:
| Mode | Primary endpoint | Second endpoint |
|---|---|---|
| Equal distribution | stratum.xdag.org:23656 |
stratum.xdag.org:24656 |
| Solo | stratum.xdag.org:23655 |
stratum.xdag.org:24655 |
Use the domain name rather than copying the displayed server IP. The setup page recommends the domain so the operator can move the service without requiring miners to replace a fixed address.
Start with the miner’s default CPU settings. After it runs reliably, compare hashrate, accepted shares, temperature, and computer responsiveness under different thread settings. A higher thread count does not guarantee a higher stable hashrate.
The miner log should show accepted work rather than repeated connection or authorization errors. Search the wallet address on the pool dashboard after the worker has submitted shares. For more background, see how to find a pool’s Stratum address and port.
Network conditions help show whether solo mining is practical. Read current figures from the XDAG explorer and pool dashboard because they change over time.
Compare three measurements:
Dividing the sustained miner hashrate by the network hashrate gives a rough share of competing work. It does not predict when a solo reward will arrive. Short mining periods can differ sharply from a long-run estimate.
If network hashrate or difficulty rises while the local rate stays fixed, the miner’s relative position worsens. Recheck the calculation before switching from equal distribution to solo.
The documented 64-second network block interval describes the whole network. It should not be presented as an individual miner’s payout schedule.
A pool should expose operational data, connection details, payout rules, and recent activity. A polished homepage alone does not verify that it records shares or sends payments.
Check the endpoint’s synchronization status and recent updates on its dashboard. Then use the XDAG explorer to inspect blocks and payments associated with the pool.
Compare the published fee and payout threshold with the values shown during setup. Stop the test if the miner connects to an unexpected host or the dashboard does not recognize the submitted address.
Run a limited test before adding more machines. Wait until the dashboard records accepted work and the expected balance appears. After reaching the threshold, confirm the payment in the destination wallet.
Verify a pool through accepted shares, recorded balances, and on-chain payments rather than branding.
Frozen statistics, unexplained downtime, missing payout terms, or repeated authorization failures warrant investigation. Learn what server-side and client-side pool software does before trusting unfamiliar infrastructure.
Price, volume, market capitalization, and exchange availability change too quickly for fixed values in a mining guide. Check them on a live market page immediately before estimating revenue.
A displayed market price does not guarantee that an order can be filled at that level. Inspect the relevant order book and account for trading fees before assigning a cash value to expected mining rewards.
Confirm that the venue currently supports XDAG deposits and withdrawals. A listed trading pair does not prove that deposits are open. Historical exchange references in a project roadmap also do not confirm current support.
Estimate mining results with a measured hashrate and current network data. Then subtract electricity, the published pool fee, and any exchange costs. Treat the result as an estimate rather than a guaranteed return.
For a first test, the equal endpoint offers the clearest way to check the wallet, worker name, miner, and pool connection. Its rewards accumulate according to contributed hashrate whenever the pool finds a block.
Solo mode exposes the miner to longer unpaid intervals. Consider it only after measuring sustained hashrate and comparing that rate with current network conditions.
Before leaving a worker unattended, confirm its Stratum endpoint, synchronization status, accepted shares, wallet address, and backup. Recheck the live XDAG pool dashboard when network conditions or endpoint status changes.
Start with a limited equal-mode test and verify the first wallet payment before committing more CPU time or electricity.
Equal distribution allocates rewards in proportion to contributed hashrate whenever the pool finds a block. Solo mode pays the full reward only when that miner finds a block. Equal mode produces smaller accumulated credits, while solo mode can produce long unpaid intervals.
The XDAG roadmap records the switch from sha256d to RandomX. Current pool documentation identifies RandomX as the network’s mining algorithm, so miners should follow current RandomX setup instructions rather than older sha256d guides.
The XDAG.ORG FAQ sets the threshold at 3 XDAG and says payment follows within the next 10 minutes. Its published endpoints list a 2.00% fee. These figures should not be applied to another operator without checking that operator’s rules.
The current XDAG.ORG FAQ links to XMRig for manual mining. Its setup page can also generate a Windows mining package for a chosen endpoint and wallet address.