Here the step-by-step procedure for the independent verification of the data or document notarization :
This is a courtesy page provided by Quadrans Foundation for convenience to easier proove the
correct notarization of the submitted data hash.
This is a free service, as such Quadrans cannot be held responsible for any loss or damage.
Please print or save this page and store it in a safe place for later reference and use. With those it's easy to proove ownership, timestamping, time of existence, consistency and immutability of data.
It is necessary to:
Quadrans will not store any of those. No guaranties are provided that this page will still be available at any time in the future. Therefore the owner of the data and email address is responsible for the storage of both.
The evidence is the double hash of the concatenation of 2 binary hashes of data available to the sender:
|owner email hash||06da5cb0a3bd50ecc1bffbb21e99bd263a6c62ff0d12260caa5006f205a034f5|
Using any Linux console, it is possible to check the evidence using the hash submitted for the data [hd] and the hash of the email address [he] used with:
echo -n [hd][he] | tr "[:lower:]" "[:upper:]" | xxd -r -p | sha256sum | xxd -r -p | sha256sum
According to the properties of cryptographic hash functions, excluding the extremelly unlikely event of collisions, that evidence can only result as hash of the to previously provided elements.
The evidence is stored with many others into a covenient data structure called
All those evidences are coupled and hashed together in a binary tree until a single hash can be derived, called Merkle Root.
In order to proove matematically that an evidence is part of a merkle tree, a list of the other hashes (called Merkle Proof) must be provided, and those have to be hashed together and result in the same Merkle Root.
For this particular evidence the list of hashes is :
d70cb656d5193d81b643bb7f6b3aef9f89517c2fa564862f61ff50021284e305 (your data)
6d9986d6702134c43fe4b6931dd8fff4fb3481ad38687a9813ed190270a47a3b (your evidence)
6d9986d6702134c43fe4b6931dd8fff4fb3481ad38687a9813ed190270a47a3b (merkle tree root)
6d9986d6702134c43fe4b6931dd8fff4fb3481ad38687a9813ed190270a47a3b (calculated root)This clearly shows :
Those hashes are calculated on binary numeric values (byte arrays). Using any Linux console it is possible to check each pair of hashes [h1] and [h2] with:
echo -n [h1][h2] | tr "[:lower:]" "[:upper:]" | xxd -r -p | sha256sum
This proves that the evidence 6d9986d6702134c43fe4b6931dd8fff4fb3481ad38687a9813ed190270a47a3b is part of the merkle root 6d9986d6702134c43fe4b6931dd8fff4fb3481ad38687a9813ed190270a47a3b
Provided that the evidence is part of the merkle root, that specific value has been notarized in the Quadrans blockchain in this position and date:
With the merkle tree and the transaction it was recorded in, it is possible to use web3 api to get the
Running that procedure the result is the following:
|_hash||6d9986d6702134c43fe4b6931dd8fff4fb3481ad38687a9813ed190270a47a3b (merkle root)|
The recorded "_hash" value matches the merkle root, this shows that the all the evidences, with the provided merkle proof, where successfully notarized on the Quadrans blockchain.
Don't trust, verify.