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 works with EVM chains. If any requirement depends on something other than EVM holdings or your own endpoint, plan how to handle it before you switch.

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, and Staking.

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.

  1. Write requirements down

    For each role, list the conditions and whether they combine with and or or.

  2. 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.

  3. 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?
Use a Combo rule with up to five conditions. Every condition must pass for the role to be granted.
How do I let either of two conditions grant a role?
Create two rules that grant the same role. The member keeps it while any one of them passes.
Can my own backend decide eligibility?
Yes. A Custom API rule sends the member's wallets to your HTTPS endpoint, which answers success true or false. Set a secret to sign requests with HMAC-SHA256.
Which chains can rules use?
44 EVM networks are built in, and any other EVM chain can be added with its chain ID and RPC URLs.

Moving from Guild.xyz?
Start free, switch at your pace.