XDAG mining supports a ledger built as a directed acyclic graph rather than a simple line of blocks. Transactions and blocks are linked inside that graph, while a main chain selected by accumulated difficulty gives the network an ordered history.
The original XDagger repository says mainnet launched on 5 January 2018 and new rewards were created every 64 seconds. That repository was archived on 4 June 2025, so current software provenance and community maintenance are now part of the mining decision.
Estimated reading time: 7 minutes
TL;DR
- XDAG uses a directed acyclic graph with a maximum-difficulty main chain.
- The original repository describes mineable rewards on 64-second main-block intervals.
- The original repository is read-only since June 2025, so verify a maintained implementation, live peers and pool payments.
What This Means in Simple English
XDAG lets many small blocks point to earlier blocks like branches in a family tree. The network then follows the strongest ordered path through that graph. Miners add work that helps decide this main path.
Simple Example
Imagine many pupils pinning notes to a board and drawing arrows to notes they have checked. Several notes can appear at once. A marked route through the strongest linked notes becomes the class record.
Key Terms in Plain English
| DAG: | A directed acyclic graph in which blocks can link to several earlier blocks. |
|---|---|
| Main chain: | The ordered path selected from the graph using accumulated difficulty. |
| Main block: | A block on the selected main chain that can carry a mining reward. |
| Epoch: | A 64-second time interval used by the original protocol. |
| Archived repository: | A source repository made read-only, which is not evidence of current maintenance. |
How the XDAG Ledger Differs
The original protocol gives each fixed-size block links to other blocks. A block can represent an address, transaction or mining candidate. The graph grows with more than one branch instead of forcing every new object directly behind one tip.
A distinct main chain provides ordering. Its difficulty is built from selected main blocks. This means the word DAG does not remove proof of work or the need to settle on one accepted transaction order.
What Miners Contribute
Mining searches for block hashes that add difficulty to the graph and its main chain. The original documentation describes a reward schedule that changes across block ranges and creates a main block in each 64-second interval.
An interval is a network rule, not a personal payment clock. A small miner may wait much longer for a pool credit. Pool method, total work and variance decide the individual result.
Hardware and Algorithm Checks
XDAG implementations have changed mining code over time, including GPU-oriented work and later RandomX material in the original repository. Do not assume one old benchmark describes the current community network.
Identify the maintained client, active fork if any, network height and algorithm before choosing hardware. The correct answer must come from code and peers that agree with the live chain, not from the asset table's broad DAG label.
What Repository Archival Means
GitHub marks the original XDagger repository as archived and read-only from 4 June 2025. The old source remains useful historical evidence, but issues and security fixes cannot be merged there.
A community may continue through another maintained repository. Verify maintainers, signed releases, recent commits, compatible peers and current explorer height. Never hide the archive status from a beginner.
Pool and Node Evidence
Check recent XDAG main blocks, connected peers, pool work and the exact client version. A miner can appear busy while following stale peers or submitting to an abandoned endpoint.
Test one worker and one small payment. Record whether the pool pays directly, uses a minimum or converts rewards. A dashboard number is not a controlled wallet balance.
Calculate XDAG Mining Income
Use pool-side accepted work and the live network state. Subtract whole-system power, pool fees, downtime, cooling and the cost of moving or selling XDAG. Allow for long payout variance.
Model a software interruption and weak market depth as well as ordinary price changes. Archived upstream code increases operational risk even if a community build remains functional.
A Cautious Test Plan
Use a dedicated machine and wallet, verify the current community release and compare its chain height with more than one source. Start at safe clocks and record temperature, power and accepted work.
Complete a wallet backup and small payout before scaling. Stop if maintainers, peers, pool blocks or exchange deposits cannot be independently confirmed. Technical curiosity is a valid reason to test; it is not a promise of profit.
What the Current Data Can and Cannot Tell You
The supplied snapshot labels XDAG as mineable, but that field is only a discovery clue. The current community proof-of-work implementation rule, current node release, recent blocks and usable pool support must all agree before a machine is treated as productive.
Keep the XDAG network name beside every address, worker and payment. A copied address format can look plausible on another chain. A small receipt and a tested backup provide better evidence than a screenshot from a pool dashboard.
The correct status for this guide is historically mineable, with current maintenance and network status requiring verification. Record the date and source behind that status because a fork, migration, repository archive or new release can change the answer without changing an old market-data row.
A market price is not the same as money a miner can realise. Check the amount available at the intended sale size, spread, deposit status and withdrawal fee. Keep unsold coins separate from cash already received in the profit record.
Measure the complete computer or miner at the wall for several days. Compare that power with pool-side accepted work over the same period. Startup time, rejected shares and one lucky block can make a short test look much better or worse than normal.
Save the software version, pool terms, wallet backup result and calculation inputs. Change one setting at a time. This makes the result repeatable and gives the operator a clear stop point when power, stability, support or liquidity deteriorates.
Decision Table
| Claim | Required evidence |
|---|---|
| Network is live | Current peers, matching height and recent main blocks |
| Software is maintained | Active repository, recent release and named maintainers |
| Mining works | Accepted shares and a completed pool payment |
| Income is usable | Wall cost and executable sale depth |
A table is a starting point, not a promise. Verify every live input before spending money on XDAG mining hardware, software or hosting.
Frequently Asked Questions
Is XDAG a Normal Blockchain?
No. Its blocks form a directed acyclic graph, with a main chain selected for ordering.
When Did XDAG Mainnet Launch?
The official original repository records 5 January 2018 at 22:45 GMT.
Is the Original XDAG Repository Maintained?
No. GitHub shows it as archived and read-only since 4 June 2025.
Does an Archived Repository Mean the Network Is Dead?
Not automatically, but a current maintained implementation, peers, pools and payments must be proved separately.
Can XDAG Mining Guarantee a 64-Second Payment?
No. Sixty-four seconds describes a protocol interval, not an individual miner's payout schedule.
Conclusion
Xdag mining deserves a measured trial, not a promise of easy money. Confirm the live network rules, use compatible hardware and official software, protect the wallet, and calculate profit from accepted work and wall power. Keep dated records because rewards, difficulty, prices and pool terms change.
Sources and Further Reading
For wider planning, see our mining profitability guides and GPU and alternative algorithm mining articles.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.