What goes into verifying an outcome?
The seed, the frozen rules and the receipt. Here is what a result check can tell you.
A commitment comes before the result
A server seed commitment is a hash recorded before the outcome is revealed. After the seed is revealed, the verifier can check that it matches that commitment. A hash alone is only one part of an outcome check.
Recompute the recorded outcome
A complete proof carries the inputs and frozen rules needed by its game. The verifier checks the supported proof format and recomputes the draw or recorded actions. Different games use different versioned proof formats.
Keep a pre-round commitment when it is available. Comparing a revealed seed with an independently saved commitment gives a stronger check than comparing fields from the same pasted record.
Keep the original receipt
A matching computation checks the supplied result against its inputs. It does not establish supplier stock, payment approval, delivery or a future profit. An animation presents a result; it does not select it.
If a proof fails, keep the original receipt and request ID and contact support. If a request is interrupted, recover that original request before starting another.
About these stories
CS2 and crypto, with sources
Follow Counter-Strike updates, tournament moments and major crypto developments. Our articles link to original announcements and records so you can read the source behind the story.
A date for the event, a date for the article
Event dates show when the reported announcement or milestone happened. Each article separately shows its actual publication date. Historical features look back at the event rather than claiming to have been published at the time.
Images are credited on the article. Illustrative images are identified in the credit; they are not photographs of the reported event.