Allowlist

Be on a list of wallet or email addresses you upload.

An allowlist requirement checks that a member is on a list you upload: wallet addresses, email addresses, or both.

What it's for

Use it when you already know who should get in: early testers, hackathon winners, a snapshot from another platform, customers, event sign-ups. Allowlists suit lists you compile yourself; when the condition lives onchain, a token or contract query requirement stays current without uploads.

Set it up

1. Prepare a .txt or .csv file with one EVM wallet address or email address per line. You can mix both kinds in one file. Choose View example file in the form to see the format.
2. Under Who gets it, press Requirement and pick Allowlist.
3. Choose Upload allowlist and pick the file. Wait for Uploaded allowlist.
4. Give the requirement a name under Custom image and name, such as "Hackathon winners 2026", so you can tell your lists apart.
5. Press Add requirement.

Choose View uploaded allowlist to search the list, or download it.

Gotchas

• A member matches with any wallet or email address connected to their Guild account.
• To change who is on the list, edit the requirement and upload a new file. Members who are no longer on it lose the role when they're next checked.
• Choose Should not satisfy to turn it into a blocklist: everyone except the people on the list.

Examples

• Beta testers: Allowlist with the wallets from your beta sign-up form.
• Customers: Allowlist with your customers' email addresses.

Requirement type

This is the exact type the requirement picker offers, with its fields as you see them in the form.

Allowlist

Members connect a wallet and an email address to be checked.