A Guild.xyz alternative for token-gated Discord roles, with requirements you can express precisely.
If your community uses Guild.xyz to manage Discord role requirements and you are considering other tools, this page shows how requirement logic maps to NXT rules and how to switch without interrupting access.
Translate requirements into rules
Role requirements often combine conditions: hold an NFT and a token balance, hold one of two collections, or pass a check your own backend runs. Before switching, write each role's requirements out as plain sentences with "and" and "or".
In NXT, "and" lives inside a Combo rule, which requires up to five conditions at once across contracts and chains. "Or" is several rules for the same role: the member keeps the role while any of them passes. Anything that is not an on-chain check, such as an allowlist in your database, can be handled by a Custom API rule that asks your HTTPS endpoint, with optional HMAC signing.
NXT checks holdings on EVM chains and Solana. If any requirement depends on something else, such as activity on another platform, a Custom API rule can answer it from your own backend.
Building blocks for requirements
Combo (and)
Two to five conditions in one rule. The first condition that fails makes the rule fail.
Several rules (or)
Multiple rules can grant the same role. Any passing rule keeps it.
Custom API
Your endpoint answers success true or false. Requests can be HMAC signed.
Balances
ERC-20 with min and max, and Native balance for a chain's own coin.
NFT conditions
Contract, OpenSea collection, Token IDs, Trait, Quantity, Staking, and Solana collection and trait rules.
Unknown is safe
If a condition comes back unknown before any has failed, no role is removed.
Switching from Guild.xyz. Both bots run side by side.
Write requirements down
For each role, list the conditions and whether they combine with and or or.
Build the NXT rules
Use Combo for and, several rules for or, and Custom API for off-chain checks. Point them at the same Discord roles.
Re-verify and retire
Post the NXT verify panel, watch the verified count in Dashboard > Members, then remove the previous setup.
Checking your rules
When you add or change a rule, NXT sweeps your server, so verified members who already qualify receive the role without clicking Verify again. The member directory lets you run a live holdings check on any member's profile to confirm a rule behaves as you expect, which is especially useful for Custom API rules.
NXT never removes roles from members who have not linked a wallet on NXT, so members who take a while to re-verify keep the roles your current bot gave them.
Guild.xyz is a trademark of its owner. NXT is an independent product and is not affiliated with or endorsed by Guild.xyz. This page describes NXT only; check the other product's own documentation for its current features.
Questions and straight answers.
How do I require two conditions together?
How do I let either of two conditions grant a role?
Can my own backend decide eligibility?
Which chains can rules use?
Other alternatives.
Collab.Land alternative
Move token-gated roles to NXT without members losing access.
Vulcan alternative
Bring verification, captcha, tickets, and giveaways into one bot.
Matrica alternative
Holders with several wallets and chains, verified once.
MEE6 alternative
Reaction roles, polls, embeds, and welcome steps next to holder verification.
Carl-bot alternative
Reaction roles and embeds, plus roles that follow what members hold.
Ticket Tool alternative
Ticket threads that show staff which wallets and roles a member has.
Wick alternative
An image captcha gate, followed by wallet verification in the same bot.