The different Blockchain platforms are surely and steadily making headway and currently consist of public and private platforms. While Bitcoin has stirred up quite a sensation in the media, it is a mere Blockchain platform for transferring this digital currency.
There are other more generic networks for other types of transfers or exchanges such as Ethereum or Hyperledger.
For instance, healthcare centres can use private platforms to share patient data, thus enabling any healthcare providers to have access to the corresponding medical records of all visiting patients. Blockchain is infinitely scalable and can be deployed across a country, continent or as wide a scope as limited by our own imagination. This example could be used at universities to transfer student data, by banking entities for posting stolen credit card numbers, or for transferring public files.
We are going to develop a file transfer network step by step:
Let’s begin with Blockchain Ethereum in private mode, DocStamp and IPFS and PGP for encryption.
What is DocStamp?
DocStamp is an application for verifying signatures and seals on files and will work as a notarisation tool.
What is IPFS?
IPFS (InterPlanetary File System) (InterPlanetary File System) is a peer-to-peer public network that indexes file hashes and stores the file. To get a better idea of this concept: like a BitTorrent.
So, let’s start:
The following illustrations show the architecture in AWS (Amazon Web Services) and the architecture at a functional level. In order to explain in more detail, we’ve prepared an example of two persons realizing a file-transfer.
The architecture in AWS (Amazon Web Services)would look like this:
At a functional level:
- Mario (the user who will share the file) records the document and signs it in DocStamp. Mario tells Lucy (recipient user) of the file’s hash and the DocStamp public key.
- The Blockchain block stores:
- File hash
- File name
- User that recorded it in DocStamp, which is Mario in our case.
- Mario uploads the document into the IPFS front-end web already encrypted (PGP) with Lucy’s public key
- The file is sent to the IPFS network and stored in Blockchain. The document is certified as follows:
- File hash
- Person recording the file in the IPFS
Users who want to recover the file will need:
- File hash in the IPFS
- Private encryption key
- Our file recipient, Lucy, simply has to go to the IPFS front-end web page,using the file hash to download the file.
- When downloading, she will be prompted to enter the private decryption key.
- To verify who and when it has been signed in the Blockchain, Lucy will go to DocStamp with the file and its public key.
- The query returns that it has been recorded properly in Blockchain, securing that it hasn´t been modified in the IPFS.
This could be useful solution for us to improve security and transparency when sharing documents, including documentation for official organisations or banking institutions, in which the sender of the file is identified and the security that the contents are authentic, which would open new opportunities to process civil documentation.