Every trait can carry a role. Read from the source metadata.
NXT reads each token's metadata from its tokenURI, resolves IPFS and Arweave links, and grants roles to holders whose tokens match the traits you choose. Pair trait roles with channel permissions to give each faction or rarity tier its own space.
Three steps. Then it runs itself.
Choose a contract
Add a Trait rule and point it at your ERC-721 collection on any EVM chain. NXT fetches and caches the metadata for you.
Select traits
Pick trait types and values, then decide whether a token must match any of them or all of them.
Gate channels
Give each trait role access to its own channels in Discord. NXT keeps the role in step with the tokens.
What trait rules handle
Source metadata
Metadata is located through tokenURI on the contract, so roles reflect what the collection itself publishes.
IPFS and Arweave
ipfs:// and ar:// links are resolved through gateways automatically.
Any or all
Match a token that has any one of the chosen traits, or require every chosen trait on the same token.
Minimum count
Require a member to hold several matching tokens, for example three tokens with the same background.
Per-trait channels
Create one rule per trait value and map each role to its own channel for factions, tribes, or rarities.
Safe on missing data
If metadata is temporarily unavailable, NXT treats the check as unknown and never removes a role because of it.