How Does Lanveris Register and Verify a File?
Lanveris creates the file fingerprint locally without uploading the original, registers the Agent label and necessary metadata, obtains a trusted timestamp from an independent TSA, and provides record management, sharing, and verification.
Lanveris Product & Engineering Team · Published 2026-07-09
Definition
Registration is more than writing a time into a platform database. A fingerprint identifies the exact bytes, an independent timestamp authority signs the trusted time, and Lanveris organizes Agent attribution and account association, records, credentials, and verification into one workflow.
Step 1: Create the file fingerprint locally
The browser or official CLI reads the file locally and calculates its SHA-256 fingerprint. Registration and web verification send the fingerprint and necessary registration information, not the original file.
Names and extensions do not define file identity. Renaming unchanged bytes keeps the fingerprint; changing any byte will normally produce a different fingerprint.
Step 2: Register Agent attribution and complete the batch
Lanveris registers the fingerprint, description, and Agent label as a record, then groups pending records into a batch for trusted timestamping.
After completion, Lanveris generates a .lanveris credential that can stay with the file for archiving and delivery. Users can also manage Agent attribution and account association, record status, and public verification links in Lanveris.
Step 3: Obtain trusted time from an independent authority
Lanveris uses the RFC 3161 standard to request signed time from trusted timestamp authorities such as DigiCert, Sectigo, or GlobalSign. The TSA receives only the batch digest, not original files or full business records.
The signed timestamp means the independent authority had seen that digest no later than the stated time. It is stronger than a platform-only business timestamp, but it is not a copyright or authorship judgment.
Step 4: Choose the right verification path
Online lookup needs only the original file. The browser creates its fingerprint locally and queries the current public registration status, Agent label, and trusted time. This is a fingerprint comparison, not full credential verification.
Full verification needs both the original file and its .lanveris credential. Lanveris checks the file fingerprint, credential integrity, and TSA signature evidence. The web page keeps the original file local, and the official CLI can verify the same credential.
FAQ
Why is trusted time not created by Lanveris itself?
Platform times support product management, while the key time evidence is signed by an independent TSA. Full verification checks the signed time and digest rather than relying only on a database field.
What is the difference between online lookup and full verification?
Online lookup compares a locally calculated fingerprint with the current public record. Full verification also uses the .lanveris credential to check credential integrity and trusted timestamp evidence.
Does this prove the content is authentic?
No. It proves that exact bytes existed before trusted time and stayed intact. It does not prove originality, truthful capture, lawful use, or authorship by a particular person.
Sources
- FIPS PUB 180-4: Secure Hash Standard · NIST
- RFC 3161: Internet X.509 Public Key Infrastructure Time-Stamp Protocol · RFC Editor / IETF
- RFC 5816: ESSCertIDv2 Update for RFC 3161 · RFC Editor / IETF
- RFC 3161 compliant Time Stamp Authority server · DigiCert
- Lanveris CLI releases and installation · Lanveris