KeeeX Timestamp Certificate

2d3oobmciMh6FogEUTf52UQdEhC8Gp8UeqdWNxQ

Anchored on the Bitcoin Blockchain

This document is a static immutable timestamp certificate.

Download: 2d3oobmciMh6FogEUTf52UQdEhC8Gp8UeqdWNxQ.html

2d3oobmciMh6FogEUTf52UQdEhC8Gp8UeqdWNxQ
0c16d0a3c478feec3b34e4a285c43bf59b51e4df6cb61a08ccfbe2d200b6549d
BlockCypher.com Blockchain.info Blocktrail.com
Wed Jun 06 00:00:30 UTC 2018
List of files timestamped in this transaction:
  • xisan-bulek-siveh-nigyh-hyzek-nulyv-dakol-pafun-fonym-gygug-rimyd-gilus-cipoc-mecuk-dyfap-hirez-lexox
    1VYLoUipWBjzKcAntijPhJ17UhcbXA3VTyfwSXa
    2018-06-05 12:55:49.0
  • xipah-hymyv-zivif-vokel-rihys-tybyl-fatuk-tovuk-kihyg-piduc-lufos-nyvig-vumav-tenic-mocal-mumod-sexyx
    2018-06-05 14:10:01.0
  • xites-vamus-faned-cysub-sanen-byket-zohid-fuvek-vozab-tucef-kytis-nokar-guduh-hozig-hizun-pipez-dixex
    2Cu4SnNcqoQTQMujx551hFRbF97CvDLPoUb62pP
    2018-06-05 17:49:11.0
  • xigom-cicyf-likof-lipas-mevoc-bukav-zemos-gopec-mogeb-suluz-dafyr-ligeg-hosel-gybih-hocec-hofer-kaxix
    3KtmhjBkNybD7k9KmSnhn6e8A7SHAa3uhGRBN5o
    2018-06-05 17:49:16.0
  • xuceg-tyfov-copom-dycim-giped-mucuf-saveg-nypal-ponid-zusut-leluc-dyvev-tupys-zudiz-rebet-gyvif-cuxox
    3RW6y1HtGimfyKf3hdkSSt2xXWY5jqX6YjJVrES
    2018-06-05 17:55:53.0
  • xeled-hikem-zosyr-tisyv-nafet-vyrid-belag-pohez-sepuf-nezyh-bufer-tyvov-nagit-mygoc-bisad-kanoc-koxex
    2iC1SGqgZzVSpQBCWyd5Hbus2MgLkdMrQdAJVcq
    2018-06-05 17:56:04.0
  • xibis-senob-tedys-luzuf-subyk-vafih-patym-guhap-burev-pucot-zysip-zyler-dalum-bepib-kunik-pemyf-muxox
    2Xk8TUQDnpxoxo4h9g2urb7zppNtSfuFmv5i9SS
    2018-06-05 21:35:01.0
  • xucap-solih-sucoh-cykaz-hivuv-ciket-pulag-lisos-sibyl-tufik-cihin-mesuc-cozyg-vacod-nikah-gusob-syxux
    3HDAyaHnu3QAt4Bt1gWwT8W37QN74Xb3Cu9WqSY
    2018-06-05 21:35:17.0
Technical Explanations

This certificate mentions file identifiers (also known as KeeeX 'idx') that are computed from sha256 hashes that cannot under the current state of technology be counterfeited. No two distinct files can share the same identifier.

The KeeeX server produces a certificate summary like this one every several hours. This timestamp certificate may hence adequately seen as a kind of sidechain, that prevents from pushing too many transactions on the Bitcoin blockchain. It also mutualizes the cost of timestamping of course, which allows KeeeX to provide this as an unlimited service.

This certificate displays at the top below its own b58 encoded identifier computed from an sha224 hash. These settings produce a 39 character string that fits within the current 80 byte Bitcoin blockchain limit. Again, under the current state of the technology, it is not possible to counterfeit this identifier by producing another certificate file with the same id.

This certificate's id has been registered as OP_RETURN data on the Bitcoin transaction above that can for your convenience be verified by following the links below. The present certificate file hence creates a proof chain from the Bitcoin blockchain ledger to your file, that provides evidence that at the transaction date you had knowledge of the identifier of your file, which you may or not have decided to keep private or share publicly. This idx does not by itself expose your data in any way. By using KeeeX, you also have a chance to digitally sign your original file.

Although KeeeX will make its best efforts to keep this certificate accessible and indexable by search engines, we cannot guarantee this. If some file identifiers are of interest to you it is thus your responsibility and interest to download it and make sure to preserve it indefinitely. Once downloaded, you may verify its integrity using the KeeeX app. Depending upon its version, the KeeeX app may automatically retrieve this file on your behalf.

You may wonder why we chose to mutualise this certificate for potentially a large number of files. The reason is that a single certificate may provide a proof of existence for an unlimited number of files and no blockchain, Bitcoin inclusive, is designed to satisfy the massive notarisation needs, since both the block size and rate are constrained.