ENSign in

Verification · what can actually be checked

Verification

Verifying a commitment yourself

Take the revealed pick text, append the revealed salt exactly as published, run SHA-256 on the result, and compare the output to the hash that was posted before the event.

The whole value of the mechanism is that it requires no trust. If verification depends on the publisher's own tool, the publisher is still the authority, and nothing has actually been removed from the chain of trust.

Doing it without any special software Any command line has a sha256sum utility, and every operating system ships one. Paste the string, run it, compare sixty-four characters. It takes about ten seconds and needs no account anywhere.

The exact format of the string matters — spacing, ordering, whether the salt goes before or after. A scheme that does not state the format precisely cannot be verified even in principle.

Which is where it goes wrong. A publisher who provides only a verify button has rebuilt the thing they claimed to remove, and it looks more convincing than a plain instruction would.

What to do with it. Verify one pick manually, once. If it matches, the mechanism is real; if it cannot be done at all, treat the scheme as unverified.

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