trace

Prove a file
hasn’t changed.

Trace creates a cryptographic fingerprint of your document and publishes the proof to Avail DA.

Your file stays on your device.

Register a documentVerify a document
Avail Turing TESTNET

Verify a document

Check whether a file matches the version represented by an existing Trace proof.

Trace proof

A receipt or verification link.

Document optional

Hashed only in this browser.

How it works

  1. 01

    Hashes your file locally

    Your browser generates a SHA-256 fingerprint of the document. The file itself is never uploaded.

  2. 02

    Publishes the fingerprint to Avail

    Trace creates a small proof record and submits it under its Avail App ID.

  3. 03

    Verifies the file later

    Provide the file with its Trace proof. Trace retrieves the original record from Avail and compares the fingerprints.

Use cases

A simple integrity layer for files that matter.

  • Contracts

    Check that an agreement matches the final version registered.

  • Certificates

    Check that a certificate matches its registered version.

  • Reports

    Verify published audits, financial statements, and research reports.

  • Software releases

    Check that a downloaded artifact matches the registered release.

  • Internal records

    Verify the registered versions of policies, approvals, and specifications.

  • Public disclosures

    Let readers check published documents against their registered versions.

Trace proves a file matches its registered fingerprint—not that its contents are true or legally valid.

What does Trace prove?

A matching fingerprint shows that your file is byte-for-byte identical to the version referenced by an Avail record. It does not establish authorship, truth, or legal validity.

What lives on Avail?

The fingerprint and protocol fields. Your document, filename, and file size stay local.

Why Avail?

Publishing to Avail keeps the record separate from the application displaying it. Trace retrieves that record to compare fingerprints.

Retrieval depends on network and RPC availability; testnet records are not guaranteed to remain accessible indefinitely.

Privacy by design

Your file.
Always yours.

Trace fingerprints your document in your browser. The original never leaves your device.

Register and Verify
01 / On your device

File stays local.

Your document, filename, and contents stay with you. SHA-256 runs locally, without uploading or storing your file on a server.

Your document is never published to Avail.
02 / On Avail

Proof goes on-chain.

A small public record holds the fingerprint and proof fields. Trace can compare fingerprints later without needing your document contents.

Treat published fingerprints as public data.