An OpenSea collection rule grants a role to members who hold items from a collection, identified by its OpenSea slug. It is the easiest choice when a collection spans more than one contract or chain.
Settings
| Field | Description |
|---|---|
| Collection slug | The part of the OpenSea URL after /collection/. For opensea.io/collection/my-project, the slug is my-project. |
| Minimum | Optional. Total items required across every contract in the collection. Defaults to 1. |
| Role | The Discord role to grant |
How it is checked
When you save the rule, NXT looks up the collection on OpenSea and records the contracts and chains that belong to it, up to ten. Holdings are then counted for each of those contracts and summed across the member's wallets. ERC-721 balances are read directly from the chain. Where NXT needs individual token IDs, for example for ERC-1155 contracts, it may use OpenSea's account data to find them and then confirms every token on-chain.
An OpenSea outage after setup never removes a role: if a count cannot be confirmed, the result is unknown. Blocked tokens are excluded from the count.
When the collection adds a contract
If a collection adds a new contract later, open the rule and save it again so NXT refreshes the list of contracts.
Requirements
OpenSea collection rules need OpenSea data to be available to NXT, and cover the chains OpenSea supports. If the option is unavailable, use one Contract rule per contract instead, or combine them in a Combo rule.