Cookies help us deliver our services. By using our services, you agree to our use of cookies. Learn more
Bytestamplogo Eng Ita
The Internet Timestamp Service
Privacy Policy


What is Bytestamp?

Bytestamp is an Internet Timestamp Service. It can be used to put a timestamp on a file not based on trust.

Bytestamp is based on a blockchain similar to Bitcoin's one, but of another crypto-curreny, called DataCoin.

Datacoin has a unique feature: it permits to record different types of data into its blockchain.

So, it can be used in order to put timestamps on files.

How does ByteStamp work?

Each time a document is uploaded, it is processed by an hash function that outputs its digest. Each file has its own digest and from the digest you cannot go back to the corresponding file.

This digest (and not the file) is recorded in the Datacoin blockchain and than confirmed by miners together the transaction. Because the digest is subjected to the proof of work, than at that time the digest had to exist. But, because that digest can be generated only by one file, the file's owner can prove that he/she made it before that date/time.

This is a timestamp system not based on trust.

What are some examples of use?

Bytestamp can be used in several situation.

Eg, you can be forced by law to generate some document before a certain date. You don't need to go to a notary, but only to upload a file to bytestamp site.

Or, if you are an author who has written a book, you can upload that book to bytestamp site before public it. Than, if someone else writes the same book, you can prove you did it before.

Or, you can protect an invention (just like a patent) without tell anyone what is the invention. Because you upload to the Datacoin blockchain only the digest of the file that describes the invention.

Same thing for the software: you can generate the digest of the entire source code.

Or you can take a picture and upload it to bytestamp site in order to prove when it was taken.

Last but not least, World Wide Web.

When googling for something on the web, you can find dozens of websites that say the same thing. Who did it before and who did the copy and paste?

Now before you public your site, you can register its content in order to prove who is the real author.

For example:


Bytestamp (Internet Timestamp Service) can be used to put a timestamp on each type of electronic document. So the owner of the document can prove that the file was made before that date. The timestamp system is not based on trust, because the timestamp is done recording the file's digest in the blockchain of DATACOIN. Because the blockchain transaction is processed by miners (proof -of-work), the transaction itself has a timestamp. But we put the digest in the transaction, so the owner of the file that generates that digest can prove he/she made that file before that date. By – September 13, 2014


The file is timestamped at UTC Date/Time: 2014-09-13 11:09:51 UTC with 44 confirmations in block number 491855 - ID transaction: ebe74c49cf661c27f1a35bb78c47c0c98f867a752773ebb0235fb409a1d59d59 info

  1. Copy the rows betwenn -----BEGIN TIMESTAMPED TEXT----- and -----END TIMESTAMPED TEXT---- excluding these two lines that begin and end with 5 hyphens (-----)

  2. Paste them in the textbox in the section Register or check a document

  3. You can see the date and time in which the file was recorded. If someone else says the same thing on another site and record the file on ByteStamp, its timestamp will be latest

    When you record a document, you must put who is the author in the document itself, or someone else can claim he/she is the author. You should digitally sign a file before uploading it.

What are nested documents?

Read this document:

(timestamps are not real)


You hereby transfer the ownership of the A property from Bob to Alice

New York, 1/1/2014


You hereby transfer the ownership of the A property from George to Bob

New York, 1/6/2001


You hereby transfer the ownership of the A property from Tom to George

New York, 9/3/1993

digitally signed by Tom

digitally signed by George


Recorded at block 105000 at date/time UTC 1993-03-09 18:45:32 – transaction ID 89eb4cf32346903e563123456781025d80909aece307f1212818b04041403034bf46eb

digitally signed by George

digitally signed by Bob


Recorded at block 215000 at date/time UTC 2001-06-01 13:10:00 – transaction ID 3ae670902346903e563123456781025d80909aece307f1212818b04041403034bf46eb

digitally signed by Bob

digitally signed by Alice


Recorded at block 345000 at date/time UTC 2014-01-01 10:00:00 – transaction ID 7ae670360bc4903e5637a7007211025d80909aece307f1212818b04041403034bf46eb

This is a document that has inside another document that has inside another document.

As you can see, the ownership is transferred three times.

The first time from Tom to George, with timestamp March 9, 1993.

The second time from George to Bob, with timestamp June 1, 2001. But because this file contains the first one, in it is attested not only that A ownership is transferred from George to Bob, but also that George had ownership of A because had been transferred from Tom.

Similarly the third time the ownership is transferred from Bob to Alice, and is attested that Bob had ownership because had been transferred from George. But it is also attested another time that George had ownership of A because had been transferred from Tom.

Now if a criminal Mr. X wants to reclaim the ownership of A in place of Alice, who gave him A?

He should not only falsify the last document, but also all the previous steps in the chain of ownership. In fact, since Bob does not give him the good A (obviously), Mr. X should falsify a document in which he obtained the ownership of good A from Mr. Y. But then it should falsify another document which shows that Y had A by Z and so on.

And at every falsification Mr. X should use a huge computational power, repeating all the proofs-of-work that have been done over the years.

Just like the blockchain of Bitcoin has in each transaction the hash of the previous transaction, here each ownership transfer confirms the previous one. – September, 13 2014


The file is timestamped at UTC Date/Time:
2014-09-13 12:58:33 UTC
with 3 confirmations in block number 491902 - ID transaction: dc24fc405758068c3b6f515c35a46cef7aa42fcca3ed548fdd22a7f7b17266f2

Website Security Test