vynt://provenance
A record anyone can check
Provenance answers a narrow, useful question: is this the same content and the same metadata that VYNT indexed at that moment? Hashes are computed server-side over canonical JSON and stored with the record.
Construction
Three hashes, one record
Canonical JSON means keys are sorted and formatting is normalised before hashing, so the same metadata always produces the same digest.
content_hash = SHA256(content_bytes)
metadata_hash = SHA256(canonical_json(metadata))
provenance_hash = SHA256(content_hash + metadata_hash
+ timestamp + source)Example record · demo data
SHA-256
9f2c4d7b18a35e0c6f4b1d8e2a97c530be41d7f6c82a09b3e5d14f7c6a2b8093
Verification states
Four honest outcomes
Verification never guesses. If a record cannot be confirmed, VYNT says so.
verified
The supplied hash matches a stored provenance record exactly.
changed
A record exists for this item, but the content or metadata hash differs.
not_verified
The record exists but has not completed verification yet.
unknown
No record matches the supplied hash or identifier.
Optional anchoring
Public anchoring is opt-in, and privacy-preserving
Records can optionally be anchored to a public network so the timestamp is independently attested. Only hashes are ever anchored — never content, never personal data. Anchoring is never required to use VYNT.
What is stored where