The data job files each difficulty retarget
From this entry’s day the Gazette’s data job files a fourth thing by itself: each difficulty retarget, once its block is six deep. Each is an entry in this log under the desk Difficulty, with the job’s mark. The job reads block headers alone, under the rule printed on the method page, and writes the period file only at a retarget. On Mining the mark stands under the difficulty of each period the job filed, and under the days since the all-time high when the job filed either of the two periods the count is read from: the one that set the high, or the newest. The chart on the difficulty claim’s page carries the mark under the same count, on the same days. The lines of both charts, the list of stretches on the claim’s page and the node check under Reproduce this page carry none. The difficulty download gains one field, filed_by, on each period’s row: data-job, person, or nothing where the log does not say. Its JSON file and its CSV file change, and so do their checksums. The retarget at block 969,696 was read and filed by a person, in the entry under this one.