ENSign in

Verification · what can actually be checked

Verification

Why publishing a hash before kick-off matters

A cryptographic hash is a fingerprint of a piece of text. Publishing the fingerprint of a selection before the event fixes that selection without revealing it, and publishing the text afterwards lets anybody confirm the two match.

It removes the one thing that cannot otherwise be checked. Every published record depends on the publisher not having changed anything after the fact, and normally there is no way to verify that from outside.

What it establishes Hash published at 13:00. Game at 20:00. Pick and salt published at 23:00. Anybody can run SHA-256 on the revealed text and compare it to the number posted ten hours earlier. Either it matches or it does not.

It says nothing about quality. A commitment scheme proves a pick was not altered; it does not make the pick good, and a service that implies otherwise is overselling its own mechanism.

The problem arrives next. It is easy to describe and easy to fake in appearance. A hash published without the reveal, or with a reveal that nobody can recompute, looks identical and establishes nothing.

What to do with it. Check that the reveal includes the salt, and recompute one hash yourself before believing any of the others.

Today's free pick (not the main pick)

Today's free pick, for your email

Team, bet, price and the hash it was sealed under, on this page the moment you send. Lose or win, it stays public.

Unlock today's pick in Telegram →Telegram channel: sealed picks and the record, 21+ →

or by email

Public record of the main pick, losses included: 115 won, 44 lost. See every pick

One free pick a day by email until you unsubscribe, in one click. 21+.

More Verification