Fig. 11

Posting AES-encrypted documents on the blockchain to protect the privacy of sensitive information. First, the document is encrypted with a highly secure password (AO6kvkm6iR9nWFBjLuYf1HyJvEXslIGo). The encrypted document is then converted to Base64 and posted on the blockchain (https://bscscan.com/tx/0x3ea60e3b37c8565481bedb57b36ab0f81bf5c58ae9008703975b4a5afd7fb038). The Base64-encoded file can then be sourced from the transaction data and converted back to the original encrypted file. After recreating the encrypted file, it is only possible to decrypt the file and generate the original document with the correct password. It is important to rename the file to its correct extension after decoding Base64. For instance, we renamed the encrypted document file to the “.aes” extension, and after decrypting the file, it was renamed to the original “.docx” extension. For this procedure, we used AES Crypt for encrypting the document (https://www.aescrypt.com/), Base64 guru for Base64 encoding and decoding (https://base64.guru/), and INNBC DApp for posting the data on the blockchain (https://database.innovativebioresearch.com/). All of these are freely available tools