Abstract · Chain ID 2741 · ETH
Abstract NFT verification and token-gated Discord roles.
Run token-gated roles for a Abstract community from one dashboard. Abstract is one of 44 built-in networks, so there is nothing to configure: add a rule, post the verify panel, and NXT handles proofs and re-checks. Abstract communities can gate on contracts, OpenSea collections, traits, and token balances, and the sales bot recognises sales paid in ETH and in WETH on Abstract.
Abstract at a glance. What NXT supports here.
- Chain ID
- 2741
- Native coin
- ETH
- Block explorer
- abscan.org
- OpenSea data
- Available: collection rules and floor bot
- Sales detected
- Paid in ETH or WETH
- Status
- Built in, featured network
What works on Abstract. Every rule type, plus the bots.
NFT rules
Contract, Token IDs, Quantity, and Trait rules read Abstract 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 Abstract, with a minimum and optional maximum. Native balance rules require a minimum ETH balance, summed across a member's wallets.
Staking, Combo, Custom API
Count tokens held in a Abstract staking contract, combine up to five conditions across Abstract and other chains, or let your own HTTPS endpoint decide eligibility.
OpenSea collection rules
OpenSea covers Abstract, 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 Abstract collections.
Sales bot
Sales paid in ETH and in WETH are detected from on-chain transfers and posted with the token image, price, buyer, seller, an OpenSea link, and a abscan.org transaction link.
Art bot and real-time checks
Show any Abstract token with its image and traits on request. NFT transfers on gated Abstract contracts trigger a re-check of the sender and receiver within seconds, on every plan.
How Abstract 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 Abstract, that means a self-transfer of a fraction of ETH: the coin returns to the sender, so the only cost is the network fee, paid in ETH on Abstract.
The member can paste the transaction hash from abscan.org, or leave it blank and NXT searches recent blocks for the transfer. Members do not have to prove on Abstract specifically: any listed network works, so someone holding Abstract 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 Abstract 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 Abstract holdings count toward your rules.
Gate a role on Abstract. 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 Abstract
Choose Abstract as the network and paste the contract address, which you can copy from abscan.org. 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.
Abstract RPC. Public by default, yours if you want.
Abstract 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 Abstract endpoint, for example a paid plan with higher limits, add it in Dashboard > Networks with chain ID 2741. 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.
Abstract questions. and straight answers.
Do Abstract holders need to connect a wallet to verify?
Can NXT gate roles on an OpenSea collection on Abstract?
Does the sales bot post Abstract sales?
How quickly do roles change when a Abstract NFT is sold?
Can I use my own Abstract RPC endpoint?
Other networks. Same rules, same panel.
Monad
Token-gated roles on Monad, chain ID 143, with MON self-transfer proofs.
Scroll
Token-gated roles on Scroll, chain ID 534352, with ETH self-transfer proofs.
Mode
Token-gated roles on Mode, chain ID 34443, with ETH self-transfer proofs.
Flow EVM
Token-gated roles on Flow EVM, chain ID 747, with FLOW self-transfer proofs.
Manta Pacific
Token-gated roles on Manta Pacific, chain ID 169, with ETH 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.