Tokens and NFTs

Hold a coin, a token or an NFT, now.

Token and NFT requirements check what a member's connected wallets hold right now: a chain's native coin, an ERC-20 token, or NFTs from a collection.

What it's for

Use them for holder roles and tiers: "hold at least 1 of our NFTs", "hold 1,000 of our token", "hold a specific token ID". They are checked against the chain's current state, so a member who sells drops below the requirement and loses the role.

To check what someone held in the past, or that they held without a break, use Holding history.

Set it up

  1. Under Who gets it, press Requirement and pick Token balance or NFT Balance.
  2. For Token balance, choose under What to check between Native currency balance (ETH on Ethereum, for example) and ERC20 balance.
  3. Pick the chain the token or collection lives on.
  4. Paste the contract address. Find it on the project's site or in a block explorer such as Etherscan or Basescan: open the token or collection page and copy the address at the top. Guild shows the token's name and symbol once it recognizes the address.
  5. For an NFT, leave the token ID empty to count any NFT from the collection, enter one Token ID, or switch to Multiple Token IDs and paste a list.
  6. Set the balance and how to compare it, then press Add requirement.

Gotchas

  • Enter amounts as a wallet shows them (1.5 tokens), not in the token's smallest unit.
  • Make sure the address is on the chain you picked. The same project often has different addresses on different chains.
  • By default a member meets an NFT requirement if one of their wallets holds enough. Tick Sum across connected wallets to add up all their wallets instead.

Examples

  • Holders: NFT Balance, your collection on Base, at least 1.
  • Whales: Token balance, ERC20 balance, your token on Ethereum, at least 10,000.
  • Genesis owners: NFT Balance with Multiple Token IDs set to the first 100 IDs, at least 1.

Requirement types

These are the exact types the requirement picker offers, with their fields as you see them in the form.

Chains (53): Ethereum, OP Mainnet, Cronos Mainnet, Rootstock Mainnet, LUKSO, XDC Network, BNB Smart Chain, Gnosis, Polygon, Sonic, Manta Pacific Mainnet, Mint, X Layer Mainnet, opBNB, Boba Network, Filecoin Mainnet, ZKsync Era, World Chain, Astar EVM, Hyper EVM, Metis, Polygon zkEVM, Core Dao, Lisk, Moonbeam, Moonriver, Sei Network, Soneium Mainnet, Ronin, Kava EVM, Mantle, Superseed, MegaETH, ZetaChain, Cyber, Klaytn, Base, IOTA EVM, Mode Mainnet, Arbitrum One, Celo, Avalanche, Sophon, Ink, Linea Mainnet, Taiko Mainnet, Scroll, Zora, Neon EVM MainNet, Monad Mainnet, Hemi, Harmony One, Syndicate Commons. See supported chains.

Coin Balance

Members connect a wallet to be checked. Works on every chain listed above except Syndicate Commons.

Field Type Details
Balance Number Compare: at least, more than, at most, less than, exactly, anything but, between, within the last, older than.

Token Balance

Members connect a wallet to be checked.

Field Type Details
Balance Number Compare: at least, more than, at most, less than, exactly, anything but, between, within the last, older than.
Token Address Text For example 0x1234567890123456789012345678901234567890.

NFT Balance

Members connect a wallet to be checked.

Field Type Details
Balance Number Compare: at least, more than, at most, less than, exactly, anything but, between, within the last, older than.
NFT Address Text For example 0x1234567890123456789012345678901234567890.
Token Id Text, optional The id of the NFT the user should have For example 1234567890.

NFT multiple token ids balance

Members connect a wallet to be checked.

Field Type Details
Balance Number Compare: at least, more than, at most, less than, exactly, anything but, between, within the last, older than.
NFT Address Text For example 0x1234567890123456789012345678901234567890.
Token Id List Id Text Reference to the stored token id list

All Guild docs