Implementing Crossmint with Thirdweb NFT Drop: How to set the allowlist proof?

NFT
1

I’m working on a React app that uses Crossmint to let users mint NFTs from my Thirdweb NFT Drop contract. The contract is on Mumbai testnet and allows up to 9 mints per wallet. I’ve set up the CrossmintPayButton component, but I’m stuck on the _allowlistProof prop.

Here’s a simplified version of my code:

<CrossmintPayButton
  clientId='example123'
  mintConfig={{
    type: 'erc-721',
    totalPrice: '0.01',
    _quantity: mintQty,
    _currency: 'matic',
    _pricePerToken: '0.001',
    _allowlistProof: '???',
    _data: '???',
  }}
  environment='staging'
  mintTo={userAddress}
/>

I tried using {"quantityLimitPerWallet": "1"} for _allowlistProof, but it didn’t work. I also tried fetching the active claim condition with Thirdweb’s SDK:

const { data: activeClaimCondition } = useActiveClaimCondition(contract);

Then I passed JSON.stringify(activeClaimCondition) to _allowlistProof, but I still get an error. What’s the correct way to set this prop for a Thirdweb NFT Drop contract with Crossmint? Any help would be great!

2

hey there, fellow NFT enthusiast! :star2: i’ve been tinkering with crossmint and thirdweb too, and that _allowlistProof thing can be a real head-scratcher, right?

have you tried leaving the _allowlistProof empty or passing null? sometimes, if you’re not using a specific allowlist, that might work. like this:

_allowlistProof: null,

or maybe you could try passing an empty object:

_allowlistProof: {},

i’m curious, have you set up any specific allowlist rules in your thirdweb contract? if not, you might not need to worry about the _allowlistProof at all.

oh, and what about the _data prop? have you figured out what to put there? i’ve seen some folks use it to pass additional info to the contract.

let me know how it goes! i’m really interested in hearing about your project and what you’re creating. NFTs on mumbai testnet sound cool - what’s the theme of your collection?

3

Having worked with Crossmint and Thirdweb, I can share some insights on the _allowlistProof issue. First, ensure your claim conditions are properly set up in your Thirdweb contract. These conditions should handle allowlist rules if you’re using them. For the Crossmint integration, try setting _allowlistProof to null or an empty object if you’re not using a specific allowlist. Like this:

_allowlistProof: null,

or

_allowlistProof: {},

As for the _data prop, it’s used for passing additional information to the contract. If you’re not using it for anything specific, you can leave it as an empty string or omit it entirely.

Remember, the key is aligning your contract’s claim conditions with what you’re passing to Crossmint. If you’re still facing issues, double-check your contract’s configuration and consult the latest Crossmint documentation for any updates on Thirdweb integration.

4

yo, crossmint can be tricky! have u tried setting _allowlistProof to null or an empty object? if ur not using a specific allowlist in ur thirdweb contract, that might do the trick. also, what about the _data prop? some ppl use it to pass extra info to the contract. whats ur nft collection about? sounds cool!