Skip to content

Frequently Asked Questions


1. What is NFTFair? How is this platform different from other NFT platforms? (e.g. OpenSea)

NFTFair is a platform powered by Conveyor to ensure NFTs are being distributed (or sold) fairly. The average user is able to avoid being front-run by snipers, technically sophisticated buyers, or trading bots. Conveyor achieves this by enforcing the fair ordering of transactions.

Click here to try it out yourself.

2. What is a Fairdrop?

A Fairdrop is a single NFT distribution event being held for a certain duration. A vault contract is deployed and to be used only for a single Fairdrop event, which stores a fixed number of NFTs that is ready to be claimed by Fairdrop participants.

A user-facing activity site is also created for a Fairdrop event, for participants to easily interact with the vault contract to claim NFTs.


1. Can I start a Fairdrop activity to sell or give away NFTs from an existing contract?

Yes. Simply transfer the NFTs to a vault contract on NFTFair to begin setting up the activity. The platform offers support for contracts that follow the ERC721 and ERC1155 standard.

Drop us a message at to get started with your own Fairdrop.


1. Why am I not qualified to claim NFTs?

Certain Fairdrops may be be open only to participants on a whitelist. If you are not eligible, please reach out to the project directly, as we do not have control over whitelists.

2. How much does it cost to claim NFTs?

The price varies by the Fairdrop and its category. You can find NFT pricing on the activity site.

3. How many NFTs can I claim?

This also varies by the Fairdrop and its category. More details can be found on the activity site.

4. Why am I prompted to send an approve() transaction? What am I approving?

If this is your first time using Conveyor, you will likely be prompted with (at most) two approve() transactions.

The first approve() transaction grants permission for the collection of gas payment ERC20 tokens. There are certain scenarios which may omit this requirement, such as:

  • Fairdrops that opt for relayer-sponsored transactions. In this case, users do not have to bear the cost of transaction fees.
  • The user's token of choice has previously been approved for other Conveyor projects.

The second approve() transaction grants permission to the Treasury contract for collecting payment from NFT sales. This permission is valid for all vaults and other contracts on the platform that are receiving payments via the Treasury contract.

5. Why do I still have to sign two EIP712 messages?

Sending approve() transactions as a mean of assigning allowance for the transfer of ERC20 tokens requires users to hold native currencies to pay for gas. Requesting an approval for every single token transfers does not provide the smoothest user experience. A good workaround is to allocate a large amount of allowance for the spender, so users would only have to approve() once. This however places a huge amount of trust in the spender to not drain the user's allowance at will. To prevent exploitation, the spender is subjected to a secondary approval process which requires the user's signed EIP 712 message, without needing to pay for gas.

The first signature is verified by the Conveyor relayer to collect ERC20 payment token, with the amount closely equivalent to the market gas price.

The second message is sent to the NFTPlatform treasury contract to collect sales payment for the purchase of NFTs. Users may not be required to sign this message, if an NFT were to be distributed free of charge.