Marketplace animation processing

Manifold Support Questions
1

Hey - is there some issue going on with HTML mints that are hosted on IPFS?

This for example worked last week, but no longer works. You can see the media response here -

https://sepolia.marketplace.api.manifoldxyz.dev/token/0xd669c610C998F2384228c99dcF1D2e5F8d59871a/666/media?max_width=1280&lazy=true

{
  "image_status": "",
  "original_image_url": "",
  "image_url": "",
  "animation_status": "",
  "original_animation_url": "https://ipfs.io/ipfs/QmYmY6g3Bh6GJyShnuEtNqpiv2Y6nMRs39eJBL7FZyBbRc",
  "animation_url": "https://ipfs.io/ipfs/QmYmY6g3Bh6GJyShnuEtNqpiv2Y6nMRs39eJBL7FZyBbRc"
}

So since animation_status is not ok and there is no fallback image, nothing shows up. Buuut, the animation loads fine (open it in your browser).

If it helps debug, this URL also 404s for some reason -

2

Hmm I am using Chrome and the ipfs link doesn’t seem to render on my browser. Are you sure it is seeded properly?

3

Loads fine for me!

4

I think the widget code is checking if animation_status is equal to ok before even putting the <iframe /> on the page.

Do you see errors in the marketplace server logs indicating some issue processing it?

5

We are reliant on alchemy for cdn caching now btw, and it seems like the uri is malformed from their perspective:

6

But, from what I can see, it “should” still render, because we fallback to original token info.

7

Ah I see… did you move to them when simplehash shut down?

The issue you’ll have here is that there isn’t a token minted (it’s a lazy mint, following the marketplace interface).

But you’re clearly getting the assetURI correctly from onchain and then parsing it correctly. There’s just some missing step… maybe there can be a way to rely on the original_animation_url instead of cached one or something? You shouldn’t be hitting Alchemy for this

8

Ok. We fixed something on our end to use the on chain data but seeing an mei error now.

9

Hey Camp, mind trying again? It renders for me now

10

Awesome, it all looks great! Thanks everyone for the quick fix.

1 Like
11

Ah, one more issue is the 404 when using the URL pattern -

https://gallery.manifold.xyz/sepolia/0xd669c610C998F2384228c99dcF1D2e5F8d59871a/666

rather than

https://gallery.manifold.xyz/sepolia/listing?listingId=648

Are you calling alchemy with that token address + token id and getting not found because it’s a lazy mint? The route format for lazy mints used to work like that…

12

Because it hasn’t been minted (no mint events), alchemy and us do not have an indication the token exists at all.

13

That makes sense, that’s fine with me. I thought though in prior versions you checked that contract’s interface to see if it was ILazyDelivery and ILazyDeliveryMetadata as a backup.

All good though was just curious!