Hey there! Here's a Digital Witness that has been shared with you:

Digital Witness

Issued to: WitnusApp user

In witness of the fact that data with the following digital fingerprint existed at the point in time below


Digital Data Fingerprint (Content ID)

99a7 bb9f 1244 d276 53da a500 91f0 c4ff 47a7 bb77 e666 61f7 0fdd dd0e 3798 5dc4 ecd9 9a01 648d eab7 975c 380d 3d79 6000 34c0 2c4a f05a d2dc 4f9a 89ed 2ae7 29ef

Witness Fingerprint (Witness Id)

788e c17c d64c 6e45 a339 de78 e9ff 16ed 2fb6 6556 1df3 3635 b037 b9e6 b17b 07f3 c388 2956 84b8 52e8 e6ef e020 7798 f260 de44 6222 b516 29fa 0474 4b90 60c0 d544

Timestamp

2020-09-24T13:46:53.2262357Z

A Digital Witness proves that something existed at a particular point in time. "Something" can be anything digital, in this case it's this photo taken by a user of the Witnus mobile app:
Evidence image
Here's a short description of the witness, from the person who shared it:
Annual report from Rutasoka Clinic, Uvira, DR Kongo 2018
This photo was taken on 9/24/2020 1:46:51 PM (Coordinated Universal Time, UTC)
It was taken here:
If you want to convince yourself that the Digital Witness is legitimate you can validate it yourself, using tools that are freely available on the Internet. Do you want to view the instructions on how to do that?
The app calculates a "fingerprint" of the photo file, and locks this fingerprint in a secure blockchain database to make sure it can't be manipulated. We call this fingerprint the Content Id, because it identifies the content.
A fingerprint is really a very large number, often presented as a long string of letters and numbers. In this case, that string looks like this:
99a7bb9f1244d27653daa50091f0c4ff47a7bb77e66661f70fdddd0e37985dc4ecd99a01648deab7975c380d3d79600034c02c4af05ad2dc4f9a89ed2ae729ef
That's pretty unreadable, so we've created an image matrix that represents that string in the form of an image instead. To compare two images, all you need to do is to drag one of them on top of the other. If they are identical, they will match up perfectly. If not, you'll notice because it looks like they are not properly aligned. Give it a try, just push one towards the other!
If the registered fingerprint matches the calculated, as it does here, it means that the content of the photo has not been modified since the time and date the photo was registered. Now let's validate that timestamp!
To do that, we again calculate a fingerprint. This time the fingerprint is based on a string that combines the first fingerprint, a signature that tells us who registered it, and the date and time this happened. Also, at the end of the string we tag on the Id of the user who created it, and the latitude and longitude where the witness was created. The combined string looks like this:
99a7bb9f1244d27653daa50091f0c4ff47a7bb77e66661f70fdddd0e37985dc4ecd99a01648deab7975c380d3d79600034c02c4af05ad2dc4f9a89ed2ae729ef#2020-09-24T13:46:53.2262357ZWitnusApp userUserId9ccdfb85-52ee-4215-9105-b898eb197883Latitude57.7385892Longitude11.9531966
We call the calculated fingerprint of this string the Witness Id, becuase it identifies the Digital Witness. For this particular witness, the Witness Id looks like this:
788ec17cd64c6e45a339de78e9ff16ed2fb665561df33635b037b9e6b17b07f3c388295684b852e8e6efe0207798f260de446222b51629fa04744b9060c0d544
Again, comparing images is easier (and more fun) than comparing strings of letters, so here you go:
If you want to validate the fingerprints yourself, you can do so by using any service that calculates SHA512 hashes. That's the technical name for the fingerprints, and if you just search for "sha512 online" on the Internet you'll find a number of such tools that are free to use.
To calculate the Content Id fingerprint, you download the media above and upload it to the hashing service and let it do its thing. The result you're looking for is matching fingerprints, that's what tells you that the media file is exactly the one that was registered.
Validating the Witness Id is even easier, you just copy the combined witness string (the one that contains the Content Id, the Signature and the Timestamp, among other things) and paste it into your SHA512 calculator service. It should then print a string that is identical to the Witness Id above. If it does, you know that the timestamp in the witness is identical to the one you just copied and pasted.
The final step is to validate that the Witness Id also has been inserted into a blockchain database, so that you can validate the timestamp of the blockchain transaction. That process is described for this particular Digital Witness on the following page (fair warning, there's quite a bit of math on the page):