> For the complete documentation index, see [llms.txt](https://docs.xp-protocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xp-protocol.io/products/xp-protocol/integrations/nft-watcher.md). # NFT Watcher Our NFT Watcher integration is available via the XP Dashboard at [Dashboard](https://dashboard.xp-protocol.io). ## Overview Our NFT watcher integration enables communities that are built around or have used NFT collections to connect their members. This integration works well for artists that publish their music as NFTs via Sound/Zora/etc or even for NFT PFP communities where their main incentivize is to collect and trade NFTs. This integration adds gamification and helps community managers track and incentivize people trading their NFTs. ### Use Cases: **Platform Owners:** Are you running an NFT marketplace, or NFT platform similar to Sound/Opensea, you now have a simple way to encourage and track custom collections. **Music Artists:** Incentivize your music collectors across platforms such as Zora, Sound, and Catalog. **PFP/Memberships**: Add deeper incentives around collectors to help push people to initial sales, and repeat sales. ### Capabilities * [x] Reward members for minting an NFT (first person to collect an NFT) * [x] ERC-721 & ERC-1155 Support * [x] Reward/Demote members for transfering NFTs (Trigger a + point or - point per transfer) * [x] Reward/Track Open collections not owned by you, monitor collectors on other contracts. * [x] Ignore certain addresses that you want to be blocked from rewards for(internal wallets) * [x] Choose a Block to start monitoring from, which allows deep historical rewards. * [x] Monitor contracts on **Polygon**, **Ethereum**, **Arbitrum** **One**, **Arbitrum** **Nova**, **Optimism**, **BNB**, **Avalanche** ### How does it work? We've built a data ingestion system that can scrape multiple blockchains in parallel and parse its historical data for clues of transfers. Our system is clever enough to distinguish between the initial mints of an NFT and transfers to others after mints. Thus allowing you as an XP instance owner to trigger different **Actions** per each of those events. The data as always is then outputted to our [**Rest API** ](/products/xp-protocol/integrations/rest-api.md)for on-chain updates to your instance. When configuring this integration you can choose when to start the data ingestion depending on the block. This allows us to scrape historical data as far back as you would like. Depending on how far back you enable this feature the longer it will take to parse the data up to the current block. To estimate -> 6 months ago takes around 8 hours to scrape all transactions into your instance. Of course, there is a status bar on the integration page to show the current status. After all contracts have been caught up, the system goes into "Watcher" mode and watches all new transfers and automatically triggers score updates. ### How to Enable 1. Go to your dashboard instance at 2. Select "NFT Watcher" under the "Integrations" section of the navbar.

Snapshot Section

3. Set up the **Point Configuration** section, this allows you to specify what **Actions** get triggered for which type of transaction is detected by your collections. 4. ```
``` 5. Add at least one contract to one of the currently supported networks. Here you add the start block of that chain, highly suggested to input the block the contract was deployed. Then the contract address and NFT type need to also be added. Currently, we have a limit of 10 contracts under our free plan.
Done! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.xp-protocol.io/products/xp-protocol/integrations/nft-watcher.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.