In this article we are going to explain from a more technical point of view how documents are registered in blockchain in the different solutions we provide (iBS-API for developers and Certyfile, Musicdibs and Davcopy for companies and end users), protecting at all times their integrity and confidentiality as well as giving full legal compliance regarding the protection of personal data.
Blockchain technology helps to verify the authorship and traceability of any document, thanks to its encryption and certification in an immutable and decentralized blockchain, reducing costs and ensuring the security and speed of any transaction. All these features are necessary to maintain privacy and security in confidential or important documents for the business.
The first thing we do is to generate a verified digital identity of the entity (person or company), through an automated biometric and documentary KYC/KYB process. With this we can guarantee the identity and non-repudiation in the records that the entity carries out.
Subsequently, in order to register a file or a text in blockchain, the different solutions collect the information to be certified (title, description and file with the content). It is important to note that, once entered, these data are immutable; that is, they cannot be modified in any way, so it is essential to save the original file. From this form, we extract a code consisting of a series of numbers called digital trace or “hash” that is unique and different for each certificate and that will be what is recorded in blockchain (instead of the original content).
To encrypt the data, iCommunity uses two algorithms. The first is known as MD5 (Message Digest Algorithm), which processes the message, text or file to be encrypted and returns its encryption in a series of 128 bits. It is one of the most secure and widely used ways to verify the integrity of a document. Then, the second Base64 algorithm adds the binary encoding to text and vice versa, returning a string of 24 hexadecimal characters that turn out to be the digital trace of the encrypted block.
In this way there is no need for iCommunity to store or access the original documents, as the algorithms make the record independently and automatically with the data sent to certify to the blockchain. The unique digital trace generated together with the time stamp, both obtained with the blockchain registration, provide the best digital evidence to guarantee the authenticity of the document.
As for the certificate, all our solutions generate it from the digital trace. By simply entering the transaction ID and the network on which it was executed in our block explorer, we return a “pdf” file that certifies the associated blockchain record. For this reason it is always necessary to save the original document, as any kind of modification to the file will result in an error when generating and downloading the verification certificate. Therefore, care must be taken when sharing the file through applications or systems that may compress or transform the document in any way.
If you want to know more about our solutions you can contact us or read more about them at https://noticias.icommunity.io/en/#casosdeuso.
