Sonic · Chain ID 146 · S
Sonic NFT verification and token-gated Discord roles.
Run token-gated roles for a Sonic community from one dashboard. Sonic 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.
Sonic at a glance. What NXT supports here.
- Chain ID
- 146
- Native coin
- S
- Block explorer
- sonicscan.org
- OpenSea data
- Not available: use Contract rules
- Sales detected
- Paid in S
- Status
- Built in
What works on Sonic. Every rule type, plus the bots.
NFT rules
Contract, Token IDs, Quantity, and Trait rules read Sonic 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 Sonic, with a minimum and optional maximum. Native balance rules require a minimum S balance, summed across a member's wallets.
Staking, Combo, Custom API
Count tokens held in a Sonic staking contract, combine up to five conditions across Sonic and other chains, or let your own HTTPS endpoint decide eligibility.
OpenSea features
OpenSea does not provide data for Sonic, so OpenSea collection rules and the floor bot are not available here. Contract, Trait, and Quantity rules cover the same ground by reading the chain directly.
Sales bot
Sales paid in S are detected from on-chain transfers and posted with the token image, price, buyer, seller, and a sonicscan.org transaction link. Sales paid in a wrapped token or a stablecoin are not detected on Sonic.
Art bot and real-time checks
Show any Sonic token with its image and traits on request. NFT transfers on gated Sonic contracts trigger a re-check of the sender and receiver within seconds, on every plan.
How Sonic 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 Sonic, that means a self-transfer of a fraction of S: the coin returns to the sender, so the only cost is the network fee in S.
The member can paste the transaction hash from sonicscan.org, or leave it blank and NXT searches recent blocks for the transfer. Members do not have to prove on Sonic specifically: any listed network works, so someone holding Sonic 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 Sonic 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 Sonic holdings count toward your rules.
Gate a role on Sonic. 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 Sonic
Choose Sonic as the network and paste the contract address, which you can copy from sonicscan.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.
Sonic RPC. Public by default, yours if you want.
Sonic 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 Sonic endpoint, for example a paid plan with higher limits, add it in Dashboard > Networks with chain ID 146. 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.
Sonic questions. and straight answers.
Do Sonic holders need to connect a wallet to verify?
Can NXT gate roles on an OpenSea collection on Sonic?
Does the sales bot post Sonic sales?
How quickly do roles change when a Sonic NFT is sold?
Can I use my own Sonic RPC endpoint?
Other networks. Same rules, same panel.
Immutable zkEVM
Token-gated roles on Immutable zkEVM, chain ID 13371, with IMX self-transfer proofs.
opBNB
Token-gated roles on opBNB, chain ID 204, with BNB self-transfer proofs.
Base
Token-gated roles on Base, chain ID 8453, with ETH self-transfer proofs.
Robinhood Chain
Token-gated roles on Robinhood Chain, chain ID 4663, with ETH self-transfer proofs.
Unichain
Token-gated roles on Unichain, chain ID 130, 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.