miskir

Origin · Context · Continuity

What a verification receipt can establish

Check the bytes, the signer, the time evidence, and the scope independently.

Published 2026-10-15 · Version 2026-10-15.1 · Editorial guidance

JSONMarkdownCitable version

Integrity

A digest comparison checks whether supplied bytes match an expected digest. It does not identify who supplied the expected value, whether the source was complete, or whether the content is true. Obtain the expected digest through a source you have reason to trust.

Signer and authority

A valid signature demonstrates possession of a signing key for the signed bytes. Separately establish whose key it is, its intended authority, validity period, and any revocation information. A self-declared key is not independent identity verification.

Time evidence

A timestamp claim and an independently verifiable timestamp proof are different artifacts. Check the actual proof and its assumptions. A digest alone supplies no trusted creation time. Publication time on this website is not a Bitcoin anchor.

Scope and completeness

A receipt should identify exactly which artifacts and assertions it covers, any exclusions, and the verification method. The existence of a record does not establish that omitted records never existed or that a sample represents a population.

Try a local integrity check

The file checker compares SHA-256 digests in your browser without uploading your file. It provides a narrow integrity comparison, not signature verification, an issued Miskir receipt, or certification.

Check a file locally →

Cite this guide

Miskir. What a verification receipt can establish. Version 2026-10-15.1. https://miskir.com/guides/receipt-verification/

This editorial guide is not a signed receipt.