Anchor Comparison
Anchoring multiple versions of a document leaves you with several hashes. The comparison page at /compare puts two of them side by side, so you can confirm which version came first, whether one supersedes another, and exactly how their on-chain metadata differs. This is built for academic review boards and legal workflows that need to reason about document revisions.
Comparing two documents
Open /compare. Each column accepts a document independently: drop a file to hash it in your browser, or paste a 64 character hex hash directly. As with the rest of ThesisLock, files dropped for hashing never leave your device. For batch anchors, add the owner principal so the comparison resolves the right owner-keyed record. Once both hashes are present, choose Compare.
What the comparison shows
Each hash is resolved across every anchoring contract (single, batch, and group) and the results are laid out in a table. Cells that differ between the two documents are highlighted so changes stand out:
- Status: whether each hash is anchored on chain.
- Label: the on-chain label, parsed into template fields when it was created from a template.
- Source: the contract that backs the anchor, shown as a single, batch, or group badge.
- Owner: the anchoring principal, linked to its public profile.
- Stacks block and Proof NFT: the settlement block and any soulbound proof token minted for the hash.
Timeline and relationships
A timeline indicator shows which document was anchored first and the gap between them, measured in Stacks blocks and an estimated wall-clock time (Stacks blocks settle on Bitcoin roughly every ten minutes). Relationship badges summarize whether the two anchors share an owner and template type. When one label declares it supersedes the other (the word supersedes alongside a reference to the counterpart hash), a supersession badge is shown.
Shareable links and the API
Every comparison is a shareable URL. The Share comparison button copies a link with the compared hashes as query params, and opening it auto-runs the comparison:
/compare?a=<hashA>&b=<hashB>&ownerA=<principal>&ownerB=<principal>The same comparison is available as JSON for tooling. The response includes both resolved entries, the block and estimated time gap, which side is older, and the owner, label, source, template, and supersession relationships:
curl "https://thesis-lock.vercel.app/api/compare?a=<hashA>&b=<hashB>"Responses are cached at the edge for two minutes. You can also reach the page from any verified anchor: the verify page links to /compare with that hash pre-filled, and My Anchors lets you tick two anchors and compare them directly.