This post is just an experiment to publish some hashes that I will reference later on other sites and using IPFS:
Below are the references to four files that have been hashed using the SHA3 Algorithm set at 256 bits (i.e. SHA3-256) where the 256-bit binary output has been converted into hex format resulting in a 64 character-long string. Hashing the files doesn't alter them in any way, in fact, it serves as proof that if the files are modified in any way, hashing them again with SHA3-256 will result in a different hash digest proving they have been altered. Therefore, users often rely on the hash values of data to verify its integrity against the original hash that was attested as being the original/verified one.
The file name accompanies each hash digest below for reference. I am doing this as an experiment as I will later reference these hashes as proof.
sha3_256: e87baf76ea8186fb0d94662009e017e8503cb1b5b28813e2c975bf8816ec2fe2 BCA_logo.png
sha3_256: 4bcc0959234070b1f740d98516b79fac60e83bceefa41a4745bdae7500677210 UTF16ART.png
sha3_256: 05a3cb8253aac7a6de5c269f6d4df814cf75dd58caa3230dcfe9e912045e161c (filename omitted)
sha3_256: f3de53b5488525f763ce14cc9563eb77c77b8941e308bc732635668a71382355 (filename omitted)
[Update: 10-06-18 is the link ( ipfs.infura.io/ipfs/Qma29vgwofeRiibKBX74yruGbScRbAqAAHU3bfGhfQsCtk) to the UTF16ART.png image, which I uploaded through Infura since my first update here, file name has been changed, but renaming it UTF16ART.png produces the following hash: 4bcc0959234070b1f740d98516b79fac60e83bceefa41a4745bdae7500677210 which matches to the one above, showing that uploading it to Infura didn't alter it beyond renaming it.
