Keep the call private. Keep the record honest.

1. Write it once

When you seal a call, Concerning saves the wording, what counts as a hit, and the deadline. Your account and the time are attached. There is no edit or delete option after that.

2. Publish a fingerprint, not the call

We use SHA-256 to turn the sealed record into a 64-character fingerprint. The same record always produces the same fingerprint, while even a one-character change produces a different result.

The fingerprint, author, topic, sealed time, and deadline go public immediately. The call remains private until reveal. We include a secret random value, called a nonce, before hashing so no one can test likely guesses against the public fingerprint.

3. Open it and check

The call opens when it is marked hit or miss, or when its deadline arrives. The original record and its secret random value are revealed together. Anyone can run them through SHA-256 again. A matching fingerprint shows that these are the same words that were sealed earlier. An edited version will not match.

What permanent means here

Authors have no edit or delete path after sealing. If a moderator has to hide the words for safety or legal reasons, the fingerprint and dates remain on the record. Someone with database access could see a sealed call, but they could not quietly replace its wording and keep the same fingerprint.

This does not make the website indestructible. A fingerprint copied or shared elsewhere is the useful backup. It can still be compared with the revealed record even if Concerning changes later.

Hit and miss are a separate question

The fingerprint proves what was written and when. It does not decide whether the call came true. During the beta, authors mark their own hits and misses. Readers can see the revealed wording and any evidence, then judge the result for themselves.