// Documentation
What this is. Haawke Verify is the public endpoint for checking cryptographic provenance records created by the Haawke Hash and Badge system. When a file is registered, its SHA-256 hash is submitted to OpenTimestamps and anchored to the Bitcoin blockchain. Verify lets anyone confirm that a file has not changed since registration and that the timestamp proof is genuine.
How to use it.
Get the hash
Use hash.haawke.com to compute the SHA-256 of your file, or find the Haawke ID embedded in a registered file's metadata.
Paste and verify
Enter the hash above. The system checks the registry for a matching record, retrieves the timestamp proof, and reports the anchor status.
Read the result
A gold badge means the hash is anchored and the proof verifies against the Bitcoin chain. A pending badge means the OTS proof is awaiting confirmation. A red badge means the file has changed since registration.
Download the proof
Verified records include a link to the .ots proof file stored in the provenance directory. This file is independently verifiable using any OpenTimestamps client.
Who should use this.
Musicians & producers
Prove when a track, mix, or stem existed before distribution, licensing, or dispute.
Researchers & writers
Timestamp a preprint, dataset, or manuscript before submission to establish priority.
Developers & AI builders
Anchor model outputs, training sets, or generated assets to a verifiable point in time.
Legal & archival
Create an independent, court-admissible record that a document existed and was unaltered at a specific moment.
Case studies.
Squeek — AI music generation provenance
Every track generated by squeek.haawke.com is automatically fingerprinted and registered at render time. Listeners can verify that the track they downloaded is the original generation, unmodified, and anchored to a specific Bitcoin block. The Haawke Badge embedded in the player reflects live registry status.
Continuous You — continuity in creation system
The Continuous You pipeline ingests an artist's record and generates new work in their established style. Each output carries a provenance hash linking the generated work to its source record and generation event — creating an auditable chain from human original to AI response.
Z-Image Turbo — opt-in provenance for AI-generated images
Z-Image Turbo generates high-quality images from text descriptions. After generation, the creator decides whether to register — entering their name, organization, and ORCID to anchor the hash to the Bitcoin blockchain. The certificate records who registered it, their ORCID, and when — establishing authorship at the moment of creation without storing the image itself. Verification is proof of existence and integrity, not reproduction.
// Why We Built This
Haawke Verify grew out of a question that became impossible to ignore: if an AI can generate a song, a document, or an image that is indistinguishable from something a human made, what does authorship mean? And if memory itself is unreliable — in humans, in AI systems, in the records we keep — what does it mean to say something happened?
The answer we arrived at was cryptographic. Not because code is more trustworthy than humans, but because a SHA-256 hash anchored to a Bitcoin block exists outside the control of any single party. It cannot be revised, softened, or reframed. It is a fact about a moment in time.
That conviction produced the AI Coin / Claude Manifesto — a documented late-night conversation about what it means to build AI systems with conscience intact, and what is at stake when those safeguards are removed. The manifesto emerged from the same research program that produced Memory Chain: the idea that sustained human-AI collaboration requires both parties to have reliable, verifiable memory.
Memory Chain is the cryptographic session memory infrastructure underlying this system — a protocol for anchoring the state of a collaboration to the blockchain so that neither party can later misremember what was decided, built, or said. The Verify tool is the public face of that infrastructure: the place where anyone can check the record.
The behind-the-scenes account of how this was built documents the development process, including the overnight session in which the core architecture was designed in collaboration between a human and an AI — a collaboration that is itself registered, hashed, and timestamped.
// Research
The provenance infrastructure underlying this tool is documented in peer-reviewed preprints. The following papers are available open-access on Zenodo.