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)

0401 42a9 1cb2 dd3e 1292 1fef 892d 656f 238c f71c 5674 b9f4 c2e2 6640 dc1a a142 2003 fd4c 7e1b ce31 ed63 d791 54b4 6158 9689 c1dd 09a4 a1f3 c426 084e 901a 3a93

Witness Fingerprint (Witness Id)

7789 fed8 9129 538d 15ad fc96 8e51 9edb 6f91 fba9 6933 933e 545e fa6d 53f7 b610 e95d b057 4bed 410a 8296 4b1d 3396 2e03 ca6a 68d9 fa6b c483 0f04 139c 6fdf 5733

Timestamp

2020-09-24T19:02:44.5846117Z

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 2019
This photo was taken on 9/24/2020 7:02:41 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:
040142a91cb2dd3e12921fef892d656f238cf71c5674b9f4c2e26640dc1aa1422003fd4c7e1bce31ed63d79154b461589689c1dd09a4a1f3c426084e901a3a93
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:
040142a91cb2dd3e12921fef892d656f238cf71c5674b9f4c2e26640dc1aa1422003fd4c7e1bce31ed63d79154b461589689c1dd09a4a1f3c426084e901a3a93#2020-09-24T19:02:44.5846117ZWitnusApp userUserId9ccdfb85-52ee-4215-9105-b898eb197883Latitude57.73847508709878Longitude11.953345276415348
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:
7789fed89129538d15adfc968e519edb6f91fba96933933e545efa6d53f7b610e95db0574bed410a82964b1d33962e03ca6a68d9fa6bc4830f04139c6fdf5733
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):