Avalanche · Chain ID 43114 · AVAX
Avalanche NFT verification and token-gated Discord roles.
NXT turns what members hold on Avalanche into Discord roles. Gate channels on a collection, a trait, an ERC-20 balance, or a minimum AVAX balance, and let members prove a wallet with a same-wallet transfer instead of a wallet connection. On the Avalanche C-Chain the native coin is AVAX, so self-transfer proofs and Native balance rules use AVAX, and OpenSea collection rules and the floor bot are available.
Avalanche at a glance. What NXT supports here.
- Chain ID
- 43114
- Native coin
- AVAX
- Block explorer
- snowtrace.io
- OpenSea data
- Available: collection rules and floor bot
- Sales detected
- Paid in AVAX
- Status
- Built in, featured network
What works on Avalanche. Every rule type, plus the bots.
NFT rules
Contract, Token IDs, Quantity, and Trait rules read Avalanche contracts directly. ERC-721 and ERC-1155 are both supported, with token IDs for ERC-1155, and trait rules read ERC-721 metadata from tokenURI.
Token and coin balances
ERC-20 rules gate on any fungible token deployed on Avalanche, with a minimum and optional maximum. Native balance rules require a minimum AVAX balance, summed across a member's wallets.
Staking, Combo, Custom API
Count tokens held in a Avalanche staking contract, combine up to five conditions across Avalanche and other chains, or let your own HTTPS endpoint decide eligibility.
OpenSea collection rules
OpenSea covers Avalanche, so you can reference a collection by its slug and NXT counts holdings across its contracts. The floor bot can report floor price, owners, and 24 hour volume for Avalanche collections.
Sales bot
Sales paid in AVAX are detected from on-chain transfers and posted with the token image, price, buyer, seller, an OpenSea link, and a snowtrace.io transaction link. Sales paid in a wrapped token or a stablecoin are not detected on Avalanche.
Art bot and real-time checks
Show any Avalanche token with its image and traits on request. NFT transfers on gated Avalanche contracts trigger a re-check of the sender and receiver within seconds, on every plan.
How Avalanche holders verify. No wallet connect.
Members never connect a wallet or sign a message. To prove a wallet, a member clicks Verify in your channel, enters an address, and sends a tiny, unique amount from that wallet back to the same wallet. On Avalanche, that means a self-transfer of a fraction of AVAX: the coin returns to the sender, so the only cost is the network fee in AVAX.
The member can paste the transaction hash from snowtrace.io, or leave it blank and NXT searches recent blocks for the transfer. Members do not have to prove on Avalanche specifically: any listed network works, so someone holding Avalanche NFTs can prove the same address on whichever network they have gas on, because an EVM address is the same on every chain. Where the server enables it, an OpenSea profile bio code is a second option.
A wallet proven once works in every NXT server. Holders who keep Avalanche tokens in a cold wallet can import it through a delegate.xyz v2 full-wallet delegation registered on Ethereum, Base, Arbitrum, Optimism, Polygon, or ApeChain. Once linked, the cold wallet's Avalanche holdings count toward your rules.
Gate a role on Avalanche. Three steps.
Add NXT and pick the role
Add NXT to your server and move its role above the holder roles it will manage. In Dashboard > Token gated roles, click Add role and choose a rule type.
Select Avalanche
Choose Avalanche as the network and paste the contract address, which you can copy from snowtrace.io. NXT reads the contract and, for ERC-20 tokens, fills in the symbol and decimals.
Post the verify panel
Post the verify panel in a channel members can see. Members click Verify once, and NXT re-checks them every 2 days on Free, daily on Growth, and hourly on Pro, plus on every NFT transfer.
Avalanche RPC. Public by default, yours if you want.
Avalanche works out of the box on NXT's public RPC endpoints with automatic failover between them. If an endpoint fails or times out, NXT moves to the next one, and if every endpoint fails the result is unknown, which never removes a role.
If your project has its own Avalanche endpoint, for example a paid plan with higher limits, add it in Dashboard > Networks with chain ID 43114. It is used only for your server's checks, proofs, and tests, NXT's public endpoints stay behind it as a fallback, and the dashboard shows only the host so an API key in the URL stays hidden. Removing it switches your server back to the public endpoints without touching your rules.
Avalanche questions. and straight answers.
Do Avalanche holders need to connect a wallet to verify?
Can NXT gate roles on an OpenSea collection on Avalanche?
Does the sales bot post Avalanche sales?
How quickly do roles change when a Avalanche NFT is sold?
Can I use my own Avalanche RPC endpoint?
Other networks. Same rules, same panel.
Soneium
Token-gated roles on Soneium, chain ID 1868, with ETH self-transfer proofs.
World Chain
Token-gated roles on World Chain, chain ID 480, with ETH self-transfer proofs.
Taiko
Token-gated roles on Taiko, chain ID 167000, with ETH self-transfer proofs.
Cronos
Token-gated roles on Cronos, chain ID 25, with CRO self-transfer proofs.
Fraxtal
Token-gated roles on Fraxtal, chain ID 252, with FRAX self-transfer proofs.
Keep reading.
Token gated roles
All ten rule types, how checks run, and how roles are removed only on a definitive result.
Pricing
Every feature on every plan. Plans differ by verified members, rules, and how often the sweep runs.
All chains
Every built-in EVM network with its chain ID, and how to add any other EVM chain to your server.