Polygon · Chain ID 137 · POL
Polygon NFT verification and token-gated Discord roles.
Run token-gated roles for a Polygon community from one dashboard. Polygon 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. Polygon is a common home for large-supply collections, game items, and ERC-1155 editions. Contract rules accept ERC-1155 token IDs, and the sales bot recognises sales paid in POL as well as in WETH or wrapped POL.
Polygon at a glance. What NXT supports here.
- Chain ID
- 137
- Native coin
- POL
- Block explorer
- polygonscan.com
- OpenSea data
- Available: collection rules and floor bot
- Sales detected
- Paid in POL or WETH or wrapped POL
- Status
- Built in, featured network
What works on Polygon. Every rule type, plus the bots.
NFT rules
Contract, Token IDs, Quantity, and Trait rules read Polygon 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 Polygon, with a minimum and optional maximum. Native balance rules require a minimum POL balance, summed across a member's wallets.
Staking, Combo, Custom API
Count tokens held in a Polygon staking contract, combine up to five conditions across Polygon and other chains, or let your own HTTPS endpoint decide eligibility.
OpenSea collection rules
OpenSea covers Polygon, 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 Polygon collections.
Sales bot
Sales paid in POL and in WETH or wrapped POL are detected from on-chain transfers and posted with the token image, price, buyer, seller, an OpenSea link, and a polygonscan.com transaction link.
Art bot and real-time checks
Show any Polygon token with its image and traits on request. NFT transfers on gated Polygon contracts trigger a re-check of the sender and receiver within seconds, on every plan.
How Polygon 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 Polygon, that means a self-transfer of a fraction of POL: the coin returns to the sender, so the only cost is the network fee in POL.
The member can paste the transaction hash from polygonscan.com, or leave it blank and NXT searches recent blocks for the transfer. Members do not have to prove on Polygon specifically: any listed network works, so someone holding Polygon 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 tokens in a cold wallet can delegate the full wallet on delegate.xyz (v2) to a hot wallet, and NXT reads those delegations on Polygon, so the cold wallet never has to sign or send anything.
Gate a role on Polygon. 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 Polygon
Choose Polygon as the network and paste the contract address, which you can copy from polygonscan.com. 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.
Polygon RPC. Public by default, yours if you want.
Polygon 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 Polygon endpoint, for example a paid plan with higher limits, add it in Dashboard > Networks with chain ID 137. 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.
Polygon questions. and straight answers.
Do Polygon holders need to connect a wallet to verify?
Can NXT gate roles on an OpenSea collection on Polygon?
Does the sales bot post Polygon sales?
How quickly do roles change when a Polygon NFT is sold?
Can I use my own Polygon RPC endpoint?
Other networks. Same rules, same panel.
Zora
Token-gated roles on Zora, chain ID 7777777, with ETH self-transfer proofs.
Celo
Token-gated roles on Celo, chain ID 42220, with CELO self-transfer proofs.
Gnosis
Token-gated roles on Gnosis, chain ID 100, with xDAI self-transfer proofs.
Sei
Token-gated roles on Sei, chain ID 1329, with SEI self-transfer proofs.
Kaia
Token-gated roles on Kaia, chain ID 8217, with KAIA 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.