This part of the document may be printed in A4 paper or in PDF, with no margins.
You will have to remove the margins in the print preview.
We describe the process and technologies involved in the issuance and validation of this certificate Terminology is available in the Glossary at the bottom.
To leave evidence that the documents contained in this certificate existed before a certain date CONSTATA produced files, called BULLETINS, that contain the HASHES of each PART of a DOCUMENT contained in this CERTIFICATE, and the HASHES of the DIGITAL SIGNATURES applied to some of thos PARTS.
Then, we left proof of the HASH> of each BULLETIN in separate BITCOIN TRANSACTIONS that were written in the BITCOIN BLOCKCHAIN distributed database on a date referred to as BLOCK DATE
We can establish then that DOCUMENTS, and DIGITAL SIGNATURES applied to them, existed at the time BLOCK DATE of the BULLETIN associated with them.
You can validate that the DIGITAL SIGNATURES applied to DOCUMENTS are correct independently, but the link between those signatures and actual persons and companies is only endorsed by CONSTATA's signature that was applied to this file as a whole.
Unlike timestamps, validating signatures requires you acquire a copy of constata's public key from a trusted source. Constata's website is one such way. If you are unsure about Constata's public key, then you cannot be sure about who signed this document, and who's endorsing the signer identities.
This file contains the timestamp and digital signature validation routines implemented in the Javascript language, you can find it in this file's source code. When you opened your web browser, this routine was executed, and several public copies of the Bitcoin blockchain were queried in search for bulletin fingerprints.
The process was successful, otherwise, this certificate would have shown an error message.
If you're not familiar with Javascript, or if you rather perform the validation manually, this are the steps to follow. This steps are to be reproduced in a command prompt on any Linux, MacOS or compatible operative system.
With this process, we validate that the BULLETINS were published on the BITCOIN BLOCKCHAIN at the matching date. This way we can know that the DOCUMENTS referred to existed at that date.
Calculate its HASH.
$ shasum -a 256 /path/to/bulletin_614.txt
ec0816638b2f7bef22c644d8db94d3948282015c2a03405adeeed2dc5d7b5dbe
Query the BITCOIN TRANSACTION to find the BULLETIN HASH. Its transaction id is f9feb3ba4e5903bb2e92db2c14720f31ddee8ed498fdee8a94098c5646234ed5.
With this process we validate all the DOCUMENTS are being referenced by one of the included BULLETINS we just validated, and therefore, existed in the date specified by the matching BULLETIN.
This document is composed of 1 single part, was included in BULLETIN #614, with date
Calculate its HASH.
$ shasum -a 256 /path/to/1_document.html
08846b46d0f800cce9010043ffd2557fe302a9d8d96dbe1afe04e9b8fca4254a
Find this part's HASH in BULLETIN 614 you saved previously, if the 'grep' command returns '1' it means the HASH is present there.
$ grep --count 08846b46d0f800cce9010043ffd2557fe302a9d8d96dbe1afe04e9b8fca4254a /path/to/boletin_614.txt
1