Skip to main content
← Return to Miner Tool Encyclopedia DAG Size Vernacular Guide

Think of DAG as a work manual that the miner spreads out every day

The manual must be completely put into the memory before the miner can start calculations. The manual is larger than the desktop. Even if the chip can calculate this algorithm, it will not work properly.

miner available memory6 GiB
DAG4.24 GiB
Firmware and ProgrammingReserve 0.5 GiB

4.24 + 0.5 = 4.74 GiB, which leaves room for 6 GiB.

Just count it once

Take ETC block 24,938,270 as an example

This height translates into effective epoch 415, and the DAG is approximately 4.24 GiB. Then, instead of just taking the ratio of 4.24 to the machine's marked capacity, we also need to leave a space for firmware and mining programs.

Sample height verification date: 2026-07-17. The blocks will continue to increase. For actual use, please enter the calculator to fill in the latest height.
Data ontology4.24 GiB
+
Recommended to reserve0.50 GiB
=
At least required4.74 GiB
4 GBCan't let go

The DAG itself has exceeded capacity.

5 GBVery close to the upper limit

It's feasible on paper, but the actual machine is easily affected by firmware usage.

6 GBMore room to spare

Still need to confirm firmware and mining pool support.

Just ask three questions before starting the phone

The algorithm is the same, but it does not mean that it can be mined.

  1. 01

    Will the chip count?

    First make sure the device lists Ethash or Etchash. Algorithms with similar names are not directly interchangeable.

  2. 02

    Can DAG be let go?

    Calculate the DAG using the latest block height, plus at least 0.5 GiB of program reserve space.

  3. 03

    Can the firmware and mining pool be connected?

    After you have enough memory, you also need to check the firmware version, Stratum port, wallet and actual connection.

Don’t mix ETC and ETHW

Same-origin algorithm, DAG growth rhythm is different

ETC / Etchash

After ECIP-1099 is enabled at block 11,700,000, every 60,000 blocks enter an effective epoch, and the time speed of DAG growth is approximately halved.

Example: epoch 415 approximately 4.24 GiB

ETHW / Ethash

Following the Ethash rhythm of one epoch every 30,000 blocks, DAG is usually larger than ETC on the same date.

Example: epoch 822 approximately 7.42 GiB
It's your device's turn

Enter the block height, memory and reserved space to see if it can be put down.

Start calculating
Next Steps

After the capacity is passed, look at the equipment revenue

The DAG, firmware and mining pool can all work normally, so the hashrate, power consumption, electricity cost and downtime assumptions are put into the revenue model.

  1. 01Research
  2. 02Run the Numbers
  3. 03Review Deployment