All Categories
Contracts
NFT Drop claim function parameters

NFT Drop claim function parameters

SDK parameters required to claim NFTs from our Drop contracts

When claiming NFTs from our NFT Drop contract, it can be helpful understand the required contact parameters in our claim function.

 

There are 6 required parameters as you can see in the screenshot below.

  • receiver
  • quantity
  • currency
  • pricePerToken
  • allowlistProof
  • data

This guide will help you understand what is required for each of these.

Notion image

receiver

  • the receiver field is the wallet address that you want to receive the NFT upon claim.

quantity

  • the quantity field is how many NFTs you want to claim in this transaction.

currency

  • the currency field is ERC20 address that the drop is price in. For native currency to the chain (i.e. ETH on Ethereum, MATIC on Polygon, etc) use 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

pricePerToken

  • the pricePerToken field is cost per NFT valued wei units (1 'ether' == 10^18 'wei'). There's a website you can use for this simple conversion https://eth-converter.com/ so, e.g. 0.03ether will be 30000000000000000wei -- and that's what you'll provide as input in the pricePerToken field.

allowlistProof

  • the allowlistProof field is used for when you have an allowlist specified in the claim phase. If you do NOT have an allowlist specified, you can copy-paste the following for the proof field:

      • { "proof": ["0x0000000000000000000000000000000000000000000000000000000000000000"], "quantityLimitPerWallet": 0, "pricePerToken": 0, "currency": "0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee" }

data

  • the data field input is 0x00
 

Can’t get this working? If you’ve followed the above and still have issues, contact our support team for help.

 
 
Did this answer your question?
😞
😐
🤩
openPack Function out of gas NFT metadata structure