# Verify a proof

> Free and instant, with nothing to sign up for — verify one credentialed audio file, or pair an older track with its .poh, and read the report-only process record.

**Verify a Proof.**

Free and instant, with nothing to sign up for. Drop in a credentialed WAV and Chronatum reads its embedded record. For an older export, add the track and the .poh that travels with it. Either way, Chronatum confirms the record is genuine and bound to that exact file, then shows the report-only process account. Transparency anyone can check.

## How it works

1. **Credentialed audio** — drop the supported WAV that carries its Chronatum record · up to 65 MB.
2. **Legacy pair** — for an older export, add the exact audio and its .poh sidecar instead.
3. **Verify proof** — the tool reads the credential, checks the exact audio binding, and verifies it with Chronatum.

No proof of your own yet? Try it with a sample proof, built into the page.

Your audio is uploaded only to check its fingerprint against the proof. It lands in a short-lived store that clears automatically — it isn’t reused or added to anything.

## What a result means

The evidence status is keyed by what Chronatum can actually support:

### Evidence consistent.

Observed activity and creator declarations do not conflict within the captured scope. This does not establish authorship outside that scope.

### Evidence conflict.

Direct observations, rule inferences, or creator declarations materially disagree. The report shows the conflict instead of choosing the more favorable narrative.

### Coverage insufficient.

Chronatum did not capture enough of the relevant process or source relationship to support a conclusion. Missing evidence remains explicitly unverifiable.

### Report unavailable.

The report contract, version, or data could not be validated. Verification of the signature and audio binding can still be shown independently.

## The report-only evidence account

**Four evidence bases.** Each item is labeled as a direct system observation, a rule-based inference, a creator declaration, or something Chronatum could not verify. The report never gates issuance and does not show Human/AI authorship percentages.

**Imported or generated material.** Chronatum reports only the source relationship capture actually establishes. A batch edit is not silently upgraded into proof of an import, and absence of a signal is not proof that no imported or generated material exists.

**How this session came together.** AI may select only approved evidence IDs from the scoped report; fixed server wording presents them. No audio is sent to that model, and the note is not an authorship verdict.

## If a check can't be processed

A failed check is neutral and specific — “Unable to process” plus the reason, never an accusation:

- This file isn’t a readable Chronatum proof.
- This proof wasn’t signed by Chronatum — it may have been altered.
- This audio doesn’t match the proof. They aren’t the pair that was sealed.
- Chronatum has no record of issuing this proof.
- This proof was sealed on the artist’s Mac but never registered with Chronatum, so it can’t be verified here. That’s a settings choice in the Chronatum app — not tampering. Ask the artist for a Chronatum-registered proof.
- That doesn’t look like a .poh proof file. Pick the proof that shipped with the track.
- That audio is larger than 64 MB. Use the exact bounce the proof was sealed to.
- Something went wrong reaching the verifier. Please try again.

> Chronatum attests its signature, the exact audio binding, and the scoped evidence account it received. It does not independently certify authorship or that the music is AI-free.

---

More: [llms.txt](https://chronatum.com/llms.txt) · [sitemap](https://chronatum.com/sitemap.md)