I followed the instructions provided here to upload my own metadata that was stored via IPFS. I would have done this via the studio like the video commented shows, but i wasn’t seeing this ability for burn redeems. The metadata is uploading fine, but they’re linking to the wrong tokens. You can see the first screenshot that shows the token I am looking at, and then the second screenshot is the URL i am brought to upon clicking that token ID. Is there a method I can call that correctly links the two? It seems like its using the token id from the arweave paths that used to exist.
As you pointed out, this points to ...ipfs.../3, when you might expect it to be more like ...ipfs.../16
What this indicates to me is that this is the 3rd token that was minted on this specific Burn-Redeem campaign (Mehretu)
So - what you essentially need to do is -
Upload a new folder to IPFS, with the correct numbering
Update on-chain like you’ve been doing
This is typically not too difficult, as you can usually just shift the numbering. Say on contract X you’ve minted 5 tokens, and then the BurnRedeem tokens are tokens 6-10. Then you just shift by 5. Looks like you have a mix of different methods to mint on your contract (0x04385b64cbeec318d2621d066d4597300fad83f8) such as a few different BurnRedeems. So it may be a bit of manual work there.
Let me know if this makes sense or if you need any other help!
I updated the metadata a few days ago. Its not reflecting on OS even after hitting refresh endpoint. When i go to the contract’s tokenUri method its showing the correct link in ipfs format (anything over token 7 uses IPFS). But OS is still showing the arweave links. The metadata has been updated several times and this issue is the first time its arose. Any thoughts?