KeeeX Timestamp Certificate

24dMaRv6UYFMi5Bs2FxzpaKPGbaxzcJQkaJQfhs

Anchored on the Bitcoin Blockchain

This document is a static immutable timestamp certificate.

Download: 24dMaRv6UYFMi5Bs2FxzpaKPGbaxzcJQkaJQfhs.html

24dMaRv6UYFMi5Bs2FxzpaKPGbaxzcJQkaJQfhs
b281671cb7fe4a2266d5db48fd06c4e57fd8593a528bbe2d18791bb1c7dc3420
BlockCypher.com Blockchain.info Blocktrail.com
Sun Apr 01 00:00:01 UTC 2018
List of files timestamped in this transaction:
  • xuteb-bakam-fibun-nidun-vocip-cycab-senom-fopip-hanez-fabyr-padur-pagep-rusif-gamob-ladir-gefyr-bixyx
    3KsPFzokoMFUP5dC7uX5LGGM9YyV2eaaBHeW4gH
    2018-03-31 14:42:51.0
  • xofep-dican-hedim-movof-gepog-pokar-kytip-vobim-tebiv-razuv-surem-dohyp-sykyv-fehin-kezol-luruv-cixax
    3HQSwTzyBZaQvzUPqNgX4eFe6r6Ef1Hb64pAYPb
    2018-03-31 14:43:27.0
  • xubol-fonul-rocol-zefab-zedep-hycev-hinoc-zuvak-teneh-rofas-binyg-zyder-cokih-rabam-kegir-lovuz-guxix
    2XtqNuxd9q7AFvrtV26pDwJZSgC1RgZBh1SwyKC
    2018-03-31 14:44:08.0
  • xomes-dolyn-bupik-dikeh-zukuv-nanuv-kifek-gifug-hefob-recek-dopok-mumyb-nyfaz-bizyg-himar-lisug-maxix
    2cecnAsTTwV4Jno7RCKJxw4zb46PA5uNiPRHjZN
    2018-03-31 14:44:28.0
  • xiron-lyvin-zihud-guvub-munof-hodik-kabef-necoc-tytup-papug-cehum-zynaf-gyfug-minyz-pamok-pokef-vaxux
    2sSvfeKaFbS2c4T1uYccTp6ZWsMQEqoxG4r2dvP
    2018-03-31 14:44:50.0
  • xehac-furun-kadof-dupeb-zekos-bylad-fedyn-kynel-dyhoz-gipyb-hogyn-cafot-dolun-higoz-muryr-batap-zaxix
    2eY6Ykvq2zVBfLHzirdFkTXezv6hSZeDbw3M3zZ
    2018-03-31 14:45:03.0
  • xegat-cytep-ginoc-dokym-nutig-tebub-rehag-hudol-figyf-zacyt-vigat-tatop-cizir-secuf-rypac-ryhoz-doxix
    1SN7pd8ZvmBGaUtvNuwN4LLAjy6Ur2DsRbAbAUX
    2018-03-31 15:48:13.0
  • xenop-tetat-sylig-lapek-pokyl-talok-zapaf-fanul-hofak-tytab-vinok-koful-lozec-cefug-cozun-coced-hoxix
    1opNFFRY1UypncWCMCVPC5B75VaY6VZFDDAdcMf
    2018-03-31 15:54:31.0
  • xukeh-henaz-zusar-fyvek-cufef-mimak-sanyn-cisen-totuk-migon-bekes-pemoc-nasit-zycul-pasiz-nomar-sexyx
    2uDPW57updLQMziwwR4y6bDxpxdhL1agTPAfvEt
    2018-03-31 20:42:08.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.