EVERY NIGHT AT MIDNIGHT ET, EACH UNIT SEALS ITS DAY WITH A FINGERPRINT THAT NOBODY CAN KNOW AHEAD OF TIME OR CHANGE AFTERWARD. WE READ A DIE FROM EACH ONE: TWO DICE A NIGHT, THE SAME FOR EVERYONE, AND YOU CAN CHECK EVERY ROLL YOURSELF.
STAY UP FOR THE MIDNIGHT ROLL.
Each unit seals its own file, so every night rolls two dice. Every character in a fingerprint is equally likely, so every face is too.
—
IN POWERSHELL: PRESS START, TYPE POWERSHELL, OPEN IT, PASTE THE COMMAND AND PRESS ENTER.
HOW THE SEAL WORKS ›EACH NIGHT: APEX1 · APEX2. PICK A NIGHT TO SEE IT IN THE ROLL ABOVE. THE FIRST ROLL IS OCT 31, THE FIRST SEALED DAY.
Twenty-four stars, twelve from each unit's seal: five characters of a fingerprint place each star, two for how far across, two for how high, one for how bright. Each unit's brightest star glows (the first, if two tie), and its twelve are joined by the shortest lines that link them all. Everyone sees the same sky, and at midnight it changes.
CLICK THE BRIGHTEST STARS OVER THE FARM ON THE CONTACT PAGE ›We write the code that builds each night's file. In principle we could try version after version until one rolled what we wanted, and nobody could prove we didn't. We don't, but you shouldn't have to take our word for it. For anything that matters, use the Midnight Beacon: the same two seals mixed with a public value from drand that only comes out after them, so nobody can steer it, us included.
The fingerprints are public at /data/days_apex1.json and /data/days_apex2.json, so your own code can read the same roll. Each sealed day file is at /days/apex1-YYYY-MM-DD.json and /days/apex2-YYYY-MM-DD.json, for hashing yourself. If your code needs a number nobody could pick, use the Midnight Beacon instead.