Verification Reports
A verification report is a formal, multi-document audit artifact: it proves that a set of documents were anchored on the Stacks blockchain at the time of generation, with a table of contents, summary statistics, and per-document verification details. Build one at /report.
Report types
The single-document certificate attests to one anchor. A verification report covers many documents at once and is suited to audits, submissions, and compliance records. It is offered in three formats:
| Format | Use case |
|---|---|
| HTML | A self-contained, printable document for sharing or archiving. |
| JSON | Structured data for programmatic checks and pipelines. |
| CSV | A flat table for spreadsheets and record keeping. |
Building a report
- Drop files to hash them in your browser (the files never leave your device), paste hashes one per line, or import anchors from your connected wallet.
- Each hash is checked across every contract: single anchors, batch anchors, the registry, group anchors, and proof NFTs.
- The report shows how many of the documents are verified, a breakdown by anchor source, and full metadata for each entry, with a verification URL anyone can re-check.
Reports are also reachable from the My Anchors, bulk verify, group, and dashboard pages, which hand off their hashes to the builder.
API
Generate a report server-side by POSTing a list of hashes. Add ?format=html or ?format=csv to receive the rendered document instead of JSON.
curl -s -X POST "https://thesis-lock.vercel.app/api/report" \
-H "Content-Type: application/json" \
-d '{"hashes":[{"hash":"9afe6f57ea2af60478ad37b2d44ae8ede492c4f3b7e70bcc7dfea92128585d06","filename":"thesis.pdf"}]}' | jqEvery verification is independently reproducible against the public Hiro mainnet API, so a report can be re-checked without trusting ThesisLock.