How to certify your signature with quantum computing and blockchain

These days there is a big political scandal in Spain due to a presumed faked degree that an university had emitted for the Madrid regional president, and we are facing this problem due to the handwritten signatures, some of those involved claim that they had not signed those documents, or they signed them under pressure. The thing is, we are in the 21st century using a technology from the Ancient Egypt to certify:

  • An identity
  • A date
  • That we are agree 100% with the text we are signing.

This should change.

The handwritten signature we are using today started in the Ancient Egypt, due to the scribes.

Imagine that you were under pressure to sign something you are not fully agree with, and you need a quick way to represent that in your signature without being too evident, or that you need to place a real date on your signature. Well, this is why I have created QBitSign.

How QBitSign works?

QBitSign uses a real quantum computer, the IBMQx4, it has 5 QBits, basically a QBit works like a bit, could be one-or-zero, also has the superposition property that allows it to be a one-and-zero at the same time, and when you read it it has a real 50% chance to be a one or a zero. So I used this property to put the 5 QBits in superposition and read it in an specific moment to generate a real random number that selects one of the runes of the Runic Unicode block. Also I save the quantum computer execution ID, and the file that demostrates that it has been executed in a quantum chip, as a QPoW, Quantum Proof of Work, a new concept I will speak about very soon.

After that I store the QPoW file, the file that demonstrates the execution, (contaning data like the calibration values of each qbit, timestamps, temperatures, etc.) in the IPFS (InterPlanetary File System), a relatively new distributed P2P network to share content, that can be stored permanently if you have a decent amount of nodes online.

Storing the whole file in the blockchain is very expensive, so I only store in the Ethereum blockchain:

  • The IPFS addresses to locate the file
  • The timestamp
  • The quantum result
  • The ASCII code of the runic symbol to be included in the signature
  • A MD5 hash that is the public representation of a private text that an individual can attach to a signature secretly.
The stored data in the Ethereum blockchain. Original data and converted to ASCII.

So finally you end with a very decent proof on the blockchain that can back your handwritten signatures, by only adding a small runic symbol difficult to notice in your usual signature.

What is going to be the future of this project?

Well, I love to create this useful projects for me, usually to experiment with new technologies like IPFS, or to teach about them and sharing the use case.

I am thinking now about adding a button to create your own signature by paying a small fee for the transaction, because if I create a Runic symbol per day, in 75 day I should start adding 2 symbols per signature, and that is not so nice or easy. So probably I will stop generating new symbols soon an move this service to a paid one where anyone can certify any signature in one click.

For now it has been a good proof of concept about using a Quantum Computer, which is something Quantum Computers needs to create, business use cases, cause their uses are still very limited for research.

Also it has been a good way to store big amounts of information in the blockchain by referring the information to the InterPlanetary File System, where you can store big files almost for free while writing some bytes in the Ethereum Blockchain for 2 cents.

If any of you fall in love with this idea, and want to help, you can contact me, you could be the CEO of this :-)

I will keep using these technologies and keep you posted about the results, thanks for the claps, comments and see you in the next article!