Contract Compatibility

Manifold Support
1

Hello Manifold Support,

My Manifold Creator contracts (ERC-721/ERC-1155 on Base) are not rendering in Base’s OnchainKit NFTMintCard component, even with the “bring your own data” pattern.

Issue: Component doesn’t render (zero DOM output) despite correct implementation and all required fields.

Contracts:

  • ERC-721: 0x8ef0772347e0caed0119937175d7ef9636ae1aa0 (Base)

  • ERC-1155: 0x1c6d27a76f4f706cccb698acc236c31f886c5421 (Base)

Questions:

  1. Known compatibility issues with Base/OnchainKit?

  2. Special requirements for Base integration?

  3. Recommended approach for Base NFTMintCard?

*Your docs confirm no SDK exists (standard ERC-721/ERC-1155), but someone on FC suggested the reason it was failing was because I had not integrated Manifold SDK.

Thank you.

2

Heyo thanks for reaching out. Not super familiar with their library. Can you send me some more documentation and a little summary of what you are trying to achieve with it? Then I can better help. I’m sure we can figure this out!

3

Hey Johnny,

Thanks for the quick response! Here’s more detail on what’s happening:

Test NFT Details

  • Title: Low Tide

  • Contract: 0x8ef0772347e0caed0119937175d7ef9636ae1aa0 (ERC-721 on Base)

  • Instance Number: 4149840112

  • Manifold URL: Low Tide | Manifold

  • Edition Size: 10 NFTs

The Problem

The NFTMintCard component renders but the image does not load from the contract metadata. When we set imageUrl: undefined (to let the component fetch from the token), the image remains in a “loading” state and never displays.

What works:

  • Component renders

  • Title “Low Tide” displays

  • Description displays

  • Connect Wallet button appears

![NFTMintCard 2025-12-01 at 6.33.19 PM|351x500](upload://nksptoMQvBLk5opBbJGkz5u6ux6.png)What doesn’t work:

  • Image stuck in “loading” state - cannot fetch from contract metadata

Our Implementation

We’re using Base’s OnchainKit NFTMintCard with the “bring your own data” pattern:


<NFTMintCard

contractAddress="0x8ef0772347e0caed0119937175d7ef9636ae1aa0"

tokenId={undefined} *// Optional for ERC-721*

useNFTData={useCustomNFTData}

buildMintTransaction={buildCustomMintTransaction}

>

<NFTMedia />

<NFTCollectionTitle />

<NFTAssetCost />

<NFTMintButton />

</NFTMintCard>

Custom useNFTData:

  • Returns NFTData with: name, description, imageUrl: undefined (to fetch from contract), isEligibleToMint: true, price, contractType: 'ERC721', network: 'base'

Custom buildMintTransaction:

  • Encodes mint(address to) function call via viem

  • Includes payment value (0.001 ETH)

Helpful Links

Screenshot: Included showing the component with image stuck in “loading” state.

Questions

  1. How should OnchainKit’s NFTMintCard access the token metadata/image from Manifold ERC-721 contracts?

  2. Does the contract’s tokenURI() function return the correct metadata format that OnchainKit expects?

  3. Is there a specific metadata format or endpoint that Manifold contracts use that OnchainKit should be aware of?

  4. Should we be calling a different function or endpoint to get the image URL for unminted tokens in an edition?

Additional Context

  • Base CDP Case 01454118: NFTMintCard not rendering with Manifold contracts

  • Direct contract calls work fine - issue is specifically with OnchainKit fetching metadata/image

  • Contract is standard ERC-721 (per your docs)

Any insights would be greatly appreciated!

Thanks,

Redline (Image attached)

4

Ah yes! So there’s an interesting reason behind this.

The tokenURI function for any given token ID will revert/error until that token is minted, and right now this drop has 0 mints. The data is retrievable on chain when none of the tokens are minted yet, but not from the tokenURI function. I don’t believe Coinbase’s SDK is built to work with our bespoke drop mechanics.

We can also see these tokens don’t show up on the contract page yet because of this:

Question though, you building a custom react page that has the ability to mint tokens from your edition page / manifold contract?

If so I have some good news, we’re in the process of releasing an npm package for exactly that and you seem like a perfect person to test it out. Let me know and I’ll pass that to you.

The bad news is, I do not believe the NFTMintCard from CoinBase/Base will work with our minting system since we haven’t collaborated with them on that yet. It’s probably bespoke to some “drop” system they have in their Dashboard.

1 Like
5

Hey Johnny,

Awesome. I’d love to test with you on a solution.

We tested your explanation about tokenURI() only working for minted tokens using the TANGY NFT, which has 6 minted tokens (94 remaining out of 100 edition).

Screenshot 2025-12-05 at 2.55.43 PM
Screenshot 2025-12-05 at 2.55.43 PM1780×2060 559 KB

Test Details:

  • NFT: TANGY (1966 Ford Mustang Convertible)

  • Contract: 0x8ef0772347e0caed0119937175d7ef9636ae1aa0 (ERC-721 on Base)

  • Instance: 4122044656

  • Manifold URL: Tangy | Manifold

  • Test Mode: imageUrl: undefined (to test tokenURI())

We used the exact code pattern from our previous message.

Results:

  • :white_check_mark: Component renders successfully

  • :cross_mark: Image/Asset still doesn’t display (shows placeholder icon)

  • :warning: Console shows 401 (Unauthorized) errors from api.cdp.coinbase.com

Key Finding:

Even with 6 minted tokens, tokenURI() approach still doesn’t work with NFTMintCard.**

This suggests the issue is not just about unminted tokens - there appears to be a deeper incompatibility between Coinbase’s NFTMintCard and Manifold’s contract structure.

Questions:

  1. Why doesn’t tokenURI() work even for minted tokens? (TANGY has 6 minted, so it should work per your explanation)

  2. Is there a different way to access metadata for Manifold contracts?

  3. Does your upcoming npm package solve this for both minted and unminted tokens?

What Works:

Our workaround (providing imageUrl directly) works fine - bypasses tokenURI() entirely and displays correctly.

6

Hey Johnny, Any progress on NPM?