Open redDwarf03 opened 2 years ago
One way to do this without involving contracts can be to encode in base64 the image in the NFT. But for this option, while for single file deployment this might work, for multi files this could be complex; particularly to determine which files to lock in a website deployment context
this issue concerns only the host of one file (eq 1 NFT). Not a folder or a website
It could be a nice feature indeed
Is your feature request related to a problem?
For example in case of NFT, if we host an image in the content of a transaction, we shouldn't change the image. It's necessary to block this information
Describe the solution you'd like
add a smart contract in code field
Additional context
No response