The DAG file is completely regenerated with entirely different contents every 30000 blocks (~100 hours). It needs to be generated (and takes time to do so) each 30,000 block cycle. DAG's can however be pre-generated, avoiding the need for the delay in generating one between each 30,000 block epoch. It seems there are a few comments/concerns related to DAG files, optimized configuration, space issues related to them, etc, So I will try to write a lengthier post explaining them, how they are used, and how to configure your environment to help clear up everyone's understanding.

eye candy 

That would be nice to know how to pre-regenerate them and relocate them to another drive to be read, especially people running ssds.

So, create a soft link on the dir?

Waiting on this looks like it could be a good coin 

so today we get test mining?

Looking forward to this, perfect launch time for us that are in AUS 

The new launch time means I miss it. Good luck i guess.

 Let's compare:

Expanse, 11,000,000 premine with 1,100,000 available immediately. Block target 1 minute and 8 EXP block reward. 4,207,680 EXP mined per year. Time to match premine = 2 years, 7 1/2 months

Ethereum, 72,000,000 premine to prerelease investors, devs, contributors, and their foundation. Block target 15 seconds and 5 Ether block reward. 10,519,200 Ether mined (and staked in future) per year. Time to match premine = 6 years 10 months

Shift, 250,000 premine. Block target 12 seconds (in theory, its first post says average blocktime is higher) and 3 SHF block reward. 7,889,400 (theoretical) mined (or staked in future) per year. Time to match premine = 12 days.

Edit: Shift target is 11 seconds, so math is slightly off, but you get the picture.

you right

at the same time "shift didn`t turn out to be a good project because of greedy dev, but this looks great"  and 12 days and more than 2 year.
someone do not like math