XSeal adds a sealed document version history for revised files
XSeal now links every revision of a document into one sealed document version history, so v1, v2 and v3 of a contract each keep their own signed certificate and stay together.
XSeal now keeps a sealed document version history. When a contract, policy or report is revised, you open the seal of the current version in your XSeal dashboard and upload the new file as the next version.
Each version gets its own signed certificate with its own SHA-256 fingerprint and timestamp, exactly like any other seal, and the versions are linked in order. Every version's page shows the full history, from version 1 to the latest, with the date and fingerprint of each step.
Two rules keep the history honest. Only the latest version can be extended, so the chain never forks, and a file that is byte for byte identical to the sealed version is refused, because nothing changed.
Cloud version history in a shared drive can be rewritten by whoever administers it. A sealed history cannot: each step is an independent signed record that anyone can check against the public key.
Sealed version history is available now for every signed in account at xseal.nl.
