Re:Exporting image assets from ethereum smart contract with ...
by ghayes on Saturday March 27, 2021 @03:47PM
(#26605002)
The other common approach here (for non-generative images) is to store the Sha3 hash of an image and then simply require that someone, somewhere has the actual data. You could also pass the image as a LOG message which is significantly cheaper (3 gas per byte, versus 20,000 gas per 32-bytes to store data) which means if you can read older chain blocks, you can ensure you have the underlying data.
[ Parent
| on HN ]
Re:Exporting image assets from ethereum smart contract with ...
by choxi on Saturday March 27, 2021 @05:27PM
(#26605800)
Would this be equivalent to storing the encryption key on the blockchain such that only people with an NFT have the key, and can decrypt the image (wherever the encrypted image is stored)?
Re:Exporting image assets from ethereum smart contract with ...
by verdverm on Saturday March 27, 2021 @07:53PM
(#26606751)
No, storing the SHA3 means that if you have the image, you can verify that it has not changed
Re:Exporting image assets from ethereum smart contract with ...
by nmaleki on Monday March 29, 2021 @10:01AM
(#26621663)
Few questions,
By "actual data" I'm assuming you mean the image itself?
What does a request for the actual data look like, because it is my understanding the actual data wouldn't be stored on the blockchain?
The LOG message is built into the Ethereum blockchain?