Skip to main content
8 events
when toggle format what by license comment
Mar 12, 2017 at 21:02 comment added vutran @RichardHorrocks, from source code of ethash, I believe that you dont have to restart geth to have it regenerated :D
Mar 12, 2017 at 20:48 comment added Richard Horrocks Ah, the pre-generation - you're right. I'd forgotten about that :-) @JCor1 - as vutran says, you'll need to keep the 2 DAGs with the most recent timestamps, just to be safe. (If you've already removed all but the most recent one, and that's actually a future DAG, then the current DAG should be regenerated when you restart Geth.)
Mar 12, 2017 at 20:44 comment added vutran @RichardHorrocks, often the most recent timestamp is used, not always. There is a case that ethash generate new DAG file to do smooth transition even though it's not gonna be used right away.
Mar 12, 2017 at 19:55 comment added Richard Horrocks No problem - glad to be of help.
Mar 12, 2017 at 19:47 comment added JCor1 Richard, thanks a bunch for the explanation. Sounds like I need to adjust my cron job to remove all but the latest file for maintenance.
Mar 12, 2017 at 19:36 comment added Richard Horrocks They're all DAG files, though only the one with the most recent timestamp is used. The DAG changes every epoch, which is currently 30,000 blocks (~100 hours). You can safely remove the older ones.
Mar 12, 2017 at 19:22 comment added JCor1 Thanks! I've been running the miner for a while and noticed that .ethash directory keeps filling up with other full-R23-* files. If the DAG is the all '000' file, what are the others? I see that every 4-5 days or so, there's a new full-R23-* file that gets generated at 1.9G in size.
Mar 12, 2017 at 18:39 history answered Richard Horrocks CC BY-SA 3.0