KeeeX Timestamp Certificate

3A8UXTwqH6fuoFdAFRhym8wjyFHfxweEyhRT6Gh

Anchored on the Bitcoin Blockchain

This document is a static immutable timestamp certificate.

Download: 3A8UXTwqH6fuoFdAFRhym8wjyFHfxweEyhRT6Gh.html

3A8UXTwqH6fuoFdAFRhym8wjyFHfxweEyhRT6Gh
46be281c22222df47b56e047e0dc831085ec03c36f5f7a6f47183caa7b50d643
BlockCypher.com Blockchain.info Blocktrail.com
Tue Dec 05 12:00:01 UTC 2017
List of files timestamped in this transaction:
  • xebop-gygek-kuryf-nygot-syrag-doheh-vonep-kiryv-cipec-segub-tymyh-lyfeb-nekog-vipob-rohez-sokuh-fixux
    1ZZNGnzD1Zx9T4t3yKsRS63VFthSG5v1s2Fkn9K
    2017-12-05 08:27:22.0
  • xogeb-mocaz-nidyz-cofog-tykap-kygor-mebaf-timyc-todaf-zytyd-hegec-nipyz-veroz-bonik-ripis-mevim-haxox
    1riKaxK6fnEw2CGs1Tj7HMWUgGLQEiwZ5W1CY6T
    2017-12-05 09:23:29.0
  • xihov-puvuv-lipuv-pabob-cunud-tovoz-ramyf-zamad-lirol-tylab-domut-ripip-kedih-hodyd-horos-dirig-cyxyx
    2Lg3Tn7mnvJhc7fxfo1YvHH6Nmtx1LvuphnA76V
    2017-12-05 10:28:42.0
  • xilak-dumad-cufyp-lakal-molap-razan-menaz-buval-kugot-huper-cicuc-mitof-ridip-losiz-zisyc-pitic-kexix
    3GkVVeGbQcvmPvfsUzKiLVCsmwCe4RnegYyPw4f
    2017-12-05 10:29:02.0
  • xubev-sugih-nupyg-fifat-bevis-fadar-kytyr-bupog-zodid-tufyc-vehom-zotug-heguf-pugac-domyn-vynub-haxex
    1heaffKwy8LjxbZU38F5SFRbVfLDXL3VFf8qRa1
    2017-12-05 10:30:12.0
  • xisag-logaf-fahyn-dysov-lemyn-cahor-facyr-biciv-pubok-kigyh-mulel-nyroz-lohav-valoc-hetik-pusut-zoxux
    2RguTiu1sKox3L3tMW9MKQcpBZ4xGGd5jauhnuL
    2017-12-05 10:30:19.0
  • xumok-nirok-fesac-fosyv-tisyk-minim-dosib-dyfuv-tulof-socof-cugyb-fusum-mipib-nupot-dypik-figup-luxax
    19EnCAMptpyQePs9bzx5zYX11Avrr6V3xSrw5TV
    2017-12-05 10:30:22.0
  • xehaz-zyrec-bikof-paled-pybyg-tirot-dytal-rizev-vusap-byseg-bekuk-dokor-puluh-pazon-fafob-covoc-coxex
    1exxhBZieVyceUkDaCMXo9gsGJ73N3LJ9Ft1WaM
    2017-12-05 10:30:34.0
  • xekat-gihal-guhub-telic-pezuv-boreb-felen-segik-zynag-talag-bezoc-fufup-kekyg-latuz-kukev-pylyr-dexyx
    2ud5nGesjvQKKYbsWtmBXgtNfdq1P7zd4agQqyC
    2017-12-05 10:32:21.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.