Skip to content
Permalink
main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

rkvst-docs/content/docs/user-patterns/authenticity-and-attestation/index.md

Go to file
 
 
Cannot retrieve contributors at this time
Example: Evidential documents and photographs Considerations
28 lines (21 sloc) 1.62 KB
Raw Blame
Open in GitHub Desktop
title description lead date lastmod draft images menu weight toc
Authenticity and Attestation
Assurance with RKVST
Assurance with RKVST
2021-05-31 15:18:01 +0100
2021-05-31T15:18:01:31+01:00
false
docs
parent
user-patterns
30
true

A very simple yet powerful pattern for using RKVST is the Authenticity pattern. This is a good choice when dealing with data or documents that need to be broadly proven. In a single action, files can be uploaded to RKVST so their integrity, origin, and timestamps can be verified forever. Both private and public stakeholders relying on these files can verify that what they see on their screen is authentic and untampered.

Example: Evidential documents and photographs

There are a great many documents that serve as evidence in formal discussions: pictures of a traffic accident; education diplomas; contracts; statements of account. RKVST adds strong integrity to any document to allow easy verification.

Considerations

Track Documents: Create a very simple Asset structure with minimal attributes to identify the document and store the key metadata, such as a hash of the document.

Collections: If the document is strongly related to another one, consider adding and tracking them all as Events against a single Asset record.

Versions: If the document is a new version of something already stored in RKVST, then use Events to replace the document's metadata with the updated version. Any authorized stakeholder fetching the Asset record will automatically get the most up-to-date version, and prior versions can be retrieved if necessary from the Event history.