i tried hacking a zora token to render an html file instead of an image.

created a new json file that matched the metadata but replaced the ipfs uri for the with the html ipfs

then went to the explorer and updated the token uri but...

it didnt work lol

any suggestions on how to better hack this?

the html: https://turquoise-fashionable-guanaco-363.mypinata.cloud/ipfs/QmU3fP7diTXPbWpTF9s2vCp6gnLBXeqYQKorUjLcNh2Vgg

the token:

i tried hacking a zora token to render an html file instead of an image.

created a new json file that matched the metadata but replaced the ipfs uri for the with the html ipfs

then went to the explorer and updated the token uri but...

it didnt work lol

any suggestions on how to better hack this?

the html: https://turquoise-fashionable-guanaco-363.mypinata.cloud/ipfs/QmU3fP7diTXPbWpTF9s2vCp6gnLBXeqYQKorUjLcNh2Vgg

the token: https://zora.co/collect/zora:0x5abf0c04ab7196e2bdd19313b479baebd9f7791b/299

zora probably cached the original metadata?

Currently deploying. Unofficial head platypus of /lp 

the uri includes an image so they’re probably just showing that

yeah but i assume you originally minted this with just the image? and then updated the JSON via smart contract? i'm assuming zora caches the data and stores it on a CDN rather that fetching directly from the smart contract and nothing would have triggered an update there. Like opensea has an option to refresh metadata. Does zora? Maybe you need a good ol @jacob refresh.