A new version of OpenTimestamps has been developed, this post could be outdated.
Consider visiting the OpenTimestamps web site
The path towards third party auditable verification
Eternity Wall is making efforts towards allowing a fully independent timestamps verification.
We already provided our users instructions and open-source tools to verify our notarizations. We would like to improve the auditability of our service by having an externally developed independent stamp verifier.
Peter Todd showed us his OpenTimestamps format during his recent visit in Milan.
We immediately realized this was what we needed to create a trustworthy timestamping ecosystem. One of the best part of the format is flexibility, without changing the way Eternity Wall is stamping documents we added in ours stamps the OpenTimestamps format, under the
ots1 property as in this example.
The basic idea of the format is that if you can create a path of generic operations from the document to the hash of a block you are proving that the document is committing to that block.
All the operations you need are hashing functions (like
ripemd), generic functions (
reverse) and concatenations of binary data as a prefix or a suffix.
We are using the bitcoin blockchain to prove the timestamping but the format is flexible enough to support also other blockchains.
How to verify
The following are the steps you need to verify an Eternity Wall notarized document using Peter’s python tool. The tool needs a bitcoin node with a reachable RPC endpoint (basing on the settings in your
INFO:root:Success! riccardo-casatta-profilo.jpg was created on or before 2016-01-31 09:46:31
Getting this messages means the document has been timestamped in the bitcoin blockchain on or before 2016-01-31 09:46:31
The actual verification is still cumbersome but we are hoping that a wider ecosystem support of the OpenTimestamps format will grant an easier verification process in the future.
We are already working in this direction to promote broader adoption of the standard. Stay tuned!