> For the complete documentation index, see [llms.txt](https://docs.nftx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nftx.io/contracts/creator-token-approvals.md).

# Creator Token Approvals

How ERC721-C collections work with NFTX: allow NFTX's operators for feeless trading, or enforce creator royalties through the Royalty Gate.

An ERC721-C collection decides, through its transfer validator, which contracts may move its NFTs. There are two ways to set one up for NFTX:

|                                | Allow NFTX's operators                                  | Enforce royalties with the Royalty Gate                                           |
| ------------------------------ | ------------------------------------------------------- | --------------------------------------------------------------------------------- |
| Configure                      | Whitelist **Locker, Listings and NFTXZap** as operators | List the **Royalty Gate** as an authorizer; keep the Locker **off** the whitelist |
| Royalty on NFTX                | None: feeless in and out                                | Paid on every NFT entering the vault                                              |
| Deposits and sales             | Free                                                    | Through the gate, less the royalty                                                |
| Buys, redeems, listing fills   | Free                                                    | Free                                                                              |
| Listings and NFT-for-NFT swaps | Available                                               | Not available yet                                                                 |
| Status                         | Live                                                    | Live on every mainnet; each collection opts in                                    |

Either way this is a **collection-admin configuration**. Holders still approve the contract used by their transaction with ERC-721 `approve` or `setApprovalForAll`. A holder's approval cannot override a transfer-validator rejection.

The rest of this page covers the operator allowlist first, then [enforced royalties](#enforced-royalties-with-the-royalty-gate).

## Allow NFTX's operators

Ask the collection's developer team to allow **Locker, Listings, and NFTXZap** as operators in the collection's active transfer-validator policy on the chain where the collection is deployed. These three contracts cover NFTX's standard deposit, redeem, swap, listing, and ETH-to-NFT trading flows.

### Addresses to send to the collection team

The addresses match across the six current deployments, but validator settings are chain-specific. Configure each chain separately if the collection exists on more than one chain. Testnet approvals do not carry over to mainnet.

| Chain                      | Chain ID   | Locker                                       | Listings                                     | NFTXZap                                      |
| -------------------------- | ---------- | -------------------------------------------- | -------------------------------------------- | -------------------------------------------- |
| Ethereum Mainnet           | `1`        | `0xb4C5b5235b98114E9DC227b54e088C11680b2385` | `0x11F09e7eeD242FAd875D3565B3D9CA8AADE445ae` | `0x000000144106C1BfC69fBbD04D56220e1A0A9A3C` |
| Arbitrum One               | `42161`    | `0xb4C5b5235b98114E9DC227b54e088C11680b2385` | `0x11F09e7eeD242FAd875D3565B3D9CA8AADE445ae` | `0x000000144106C1BfC69fBbD04D56220e1A0A9A3C` |
| Ink                        | `57073`    | `0xb4C5b5235b98114E9DC227b54e088C11680b2385` | `0x11F09e7eeD242FAd875D3565B3D9CA8AADE445ae` | `0x000000144106C1BfC69fBbD04D56220e1A0A9A3C` |
| Arc                        | `5042`     | `0xb4C5b5235b98114E9DC227b54e088C11680b2385` | `0x11F09e7eeD242FAd875D3565B3D9CA8AADE445ae` | `0xDf288b66a77f25197544877eaF4626d7E64cb5A8` |
| ApeChain                   | `33139`    | `0xb4C5b5235b98114E9DC227b54e088C11680b2385` | `0x11F09e7eeD242FAd875D3565B3D9CA8AADE445ae` | `0xDf288b66a77f25197544877eaF4626d7E64cb5A8` |
| Robinhood Chain            | `4663`     | `0xb4C5b5235b98114E9DC227b54e088C11680b2385` | `0x11F09e7eeD242FAd875D3565B3D9CA8AADE445ae` | `0x000000144106C1BfC69fBbD04D56220e1A0A9A3C` |
| Ethereum Sepolia (testnet) | `11155111` | `0xb4C5b5235b98114E9DC227b54e088C11680b2385` | `0x11F09e7eeD242FAd875D3565B3D9CA8AADE445ae` | `0x000000144106C1BfC69fBbD04D56220e1A0A9A3C` |
| Robinhood Chain Testnet    | `46630`    | `0xb4C5b5235b98114E9DC227b54e088C11680b2385` | `0x11F09e7eeD242FAd875D3565B3D9CA8AADE445ae` | `0x000000144106C1BfC69fBbD04D56220e1A0A9A3C` |

Copyable operator list for any one of those chains:

```json
[
  "0xb4C5b5235b98114E9DC227b54e088C11680b2385",
  "0x11F09e7eeD242FAd875D3565B3D9CA8AADE445ae",
  "0x000000144106C1BfC69fBbD04D56220e1A0A9A3C"
]
```

Arc and ApeChain run a different `NFTXZap`: Arc's is configured for USDC payments, and ApeChain's pays in native APE and swaps through `NFTXArmory`. Use this list on either of them instead:

```json
[
  "0xb4C5b5235b98114E9DC227b54e088C11680b2385",
  "0x11F09e7eeD242FAd875D3565B3D9CA8AADE445ae",
  "0xDf288b66a77f25197544877eaF4626d7E64cb5A8"
]
```

Addresses checked against the protocol's deployment JSON manifests on **9 September 2026**. The [deployment reference](https://docs.nftx.io/contracts/addresses.md) includes explorer links and external dependencies. Earlier Base deployments use different addresses and are outside this table.

### Why these operators are required

The operator is the contract that calls the NFT's transfer function, even when a transaction enters through another NFTX contract.

| Flow                                | NFT movement                                    | Operators checked                   |
| ----------------------------------- | ----------------------------------------------- | ----------------------------------- |
| Deposit or seed a collection        | Holder → Locker                                 | Locker                              |
| Redeem                              | Locker → recipient                              | None: the Locker sends as the owner |
| Swap                                | Incoming NFT → Locker; outgoing NFT → recipient | Locker on the way in                |
| Create a listing                    | Holder → Listings → Locker                      | Listings, then Locker               |
| Sell an NFT for ETH through the Zap | Holder → NFTXZap → Locker                       | NFTXZap, then Locker                |
| Buy an NFT through the Zap          | Locker → buyer                                  | None: the Locker sends as the owner |

Listings and NFTXZap hold incoming NFTs temporarily; Locker holds vaulted NFTs. If the collection's policy also restricts contract receivers, check that all three can receive NFTs. Operator permission alone may not satisfy every policy. Validate outbound transfers too, including delivery to a buyer's smart wallet.

The collection's ERC-20 token, flETH, Permit2, PoolManager, and NFTX hooks are not additional NFT operators for these standard flows. ERC-20 allowances used for payment are separate.

### Collection-team setup

1. Read `getTransferValidator()` on the NFT collection and identify its validator version and currently attached policy/list. Use that validator's admin tools or verified ABI; the setup functions differ between versions.
2. From the account authorized to manage the collection policy and its list, add the three addresses above as allowed **operators**. If the collection uses a shared list your team cannot edit, create or copy a list your team controls, preserve the existing entries, and attach it to the collection.
3. Review receiver restrictions for Locker, Listings, and NFTXZap. Preserve the collection's intended policy and any existing marketplace permissions.
4. Read the policy back and simulate the transfer paths below before announcing that the collection is ready. Record the chain ID, collection address, validator address, list/policy ID, and configuration transaction hashes.

Limit Break's [transfer-validator documentation](https://github.com/limitbreakinc/creator-token-transfer-validator) explains the current rulesets and lists; older collections may use the [earlier creator-token validator](https://github.com/limitbreakinc/creator-token-contracts/blob/main/contracts/utils/CreatorTokenTransferValidator.sol). Being tradable on OpenSea does not establish permission for NFTX's operators.

{% hint style="info" %}
Allowlisting NFTX's operators does not enforce a royalty: deposits and sales through them are royalty-free. To enforce one, use the [Royalty Gate](#enforced-royalties-with-the-royalty-gate) instead.
{% endhint %}

### Verify the integration

Use a local fork with representative owned token IDs and the same holder approvals as the frontend. Exercise a deposit and redeem, listing creation and purchase, an NFT sale through NFTXZap, and a swap. Verify final NFT ownership as well as transaction success. Include smart-wallet recipients when supported.

A rejected deposit points to the Locker transfer or receiver policy. A rejected listing can occur on either the holder → Listings or Listings → Locker leg. A rejected Zap sale can occur on either holder → NFTXZap or NFTXZap → Locker. Capture the revert from the collection/validator and check the actual operator, source, and destination before changing permissions. Missing holder approval, paused transfers, frozen tokens, and receiver restrictions require different fixes.

### Optional integrations

The three-address list covers the standard NFTX trading routes. Review these additional paths separately when enabling them:

* [**Legacy migration**](https://docs.nftx.io/contracts/migrator-zap.md) **(Ethereum Mainnet):** the legacy vault transfers NFTs to MigratorZap (`0x08222EA6aBe9111b77cf006Dc7F0a7c71fcCF390`), then Locker pulls them into v4. Check the selected legacy vault as operator and MigratorZap as receiver; MigratorZap's role as transaction entry point does not make it the NFT transfer operator on these legs.
* [**Collection shutdown**](https://docs.nftx.io/contracts/collection-shutdown.md)**:** Locker sends NFTs to CollectionShutdown, and the Sudoswap factory transfers them into a newly created liquidation pair. Review the factory/pair operators and shutdown/pair receivers on the relevant chain. The pair is created for that shutdown, so there is no universal fixed three-address list covering liquidation.

## Enforced royalties with the Royalty Gate

Instead of allowing the Locker to pull NFTs freely, a collection can make every entry into the vault go through the [Royalty Gate](https://docs.nftx.io/contracts/royalty-gate.md), which pays the collection's ERC-2981 royalty. [Creator Royalties](https://docs.nftx.io/how-it-works/creator-royalties.md) explains what this means for traders.

The Royalty Gate is at `0xB1C4E21393b3F9A3f75F3a7c7AbC18Cd07FBba4F` on every mainnet (Ethereum, Base, Arbitrum One, Ink, Arc, ApeChain and Robinhood Chain). That is `$ROYALTY_GATE` in the commands below, and the Locker (`0xb4C5b5235b98114E9DC227b54e088C11680b2385`) is `$LOCKER`.

### What to configure

1. **List the Royalty Gate as an authorizer** on the collection's list. An authorizer can give one-time permission for specific tokens; the gate uses it only for NFTs it's depositing, and clears it straight after.
2. **Keep the Locker off the operator whitelist.** A whitelisted Locker lets anyone deposit around the gate. Remove it if it's already there, and check for a codehash entry on Limit Break v3 too.
3. **Use a list the collection owns alone.** Shared lists (for example a list several collections on one chain point at) can't drop the Locker for one collection without dropping it for all. Create a list, copy across the operators the collection still wants, and apply it to the collection.
4. **Keep over-the-counter transfers enabled.** The Locker sends NFTs out as their owner. Security levels 4, 7 and 8 block owner transfers and level 9 blocks all transfers, so nothing could leave the vault; the gate refuses entries at those levels.

The validator settings differ between versions:

{% tabs %}
{% tab title="OpenSea strict registry" %}
Registry `0xA000027A9B2802E1ddf7000061001e5c005A0000`. Level 3, with authorization and wildcard **enabled**:

```sh
cast send $VALIDATOR "addAccountsToAuthorizers(uint120,address[])" $LIST "[$ROYALTY_GATE]"
cast send $VALIDATOR "removeAccountsFromWhitelist(uint120,address[])" $LIST "[$LOCKER]"
cast send $VALIDATOR "setTransferSecurityLevelOfCollection(address,uint8,bool,bool,bool)" $COLLECTION 3 true true false
```

{% endtab %}

{% tab title="Limit Break v3" %}
Validator `0x721C002B0059009a671D00aD1700c9748146cd1B`. Level 3, with authorization mode **not disabled** (v3's flags are *disables*; wildcard operators may stay either way):

```sh
cast send $VALIDATOR "addAccountsToAuthorizers(uint120,address[])" $LIST "[$ROYALTY_GATE]"
cast send $VALIDATOR "removeAccountsFromWhitelist(uint120,address[])" $LIST "[$LOCKER]"
cast send $VALIDATOR "setTransferSecurityLevelOfCollection(address,uint8,bool,bool,bool)" $COLLECTION 3 false false false
```

{% endtab %}
{% endtabs %}

Run these from the account that owns the list and administers the collection. Validators without authorizers (Limit Break v1 and v2, OpenSea's Operator Filter Registry) can't host the gate; move the collection to one of the two above first.

### Check it worked

Read both views on the Royalty Gate:

* `isAuthorizerFor(collection)` must return `true`.
* `isBypassable(collection)` must return `false`.

When both hold, the NFTX app routes the collection's deposits and sales through the gate and shows traders the royalty. If `isBypassable` is `true`, the Locker can still pull the collection's NFTs directly, so the royalty is voluntary. On a fork, confirm that a plain `Locker.deposit` reverts, that a deposit through the gate pays the receiver `royaltyInfo(tokenId, 1e18)` in floor tokens, and that a redeem still delivers the NFT.

### What stops working

Every path where the Locker pulls an NFT directly reverts for an enforced collection: `Locker.deposit`, `Locker.swap` and `swapBatch`, `Listings.createListings`, `NFTXZap.sellNFTForETH`, and `Locker.initializeCollection`. Set up the vault **before** switching enforcement on. Exits keep working: redeems, buys through the Zap, and listing fills and cancels. Collection shutdown hands the NFTs to a liquidation pool, whose own pull needs the gate or a temporary whitelist entry.

To switch enforcement off, whitelist the Locker again. The gate keeps working as a voluntary route.

## Deployment and implementation sources

This table uses protocol revision [`e26724c`](https://github.com/flayerlabs/nftx-v4-protocol/tree/e26724caf6fa074c20002db4ae174f636d68350b).

* [Ethereum Mainnet deployment](https://github.com/flayerlabs/nftx-v4-protocol/blob/e26724caf6fa074c20002db4ae174f636d68350b/deployments/deployment-1.json)
* [Arbitrum One deployment](https://github.com/flayerlabs/nftx-v4-protocol/blob/e26724caf6fa074c20002db4ae174f636d68350b/deployments/deployment-42161.json)
* [Ink deployment](https://github.com/flayerlabs/nftx-v4-protocol/blob/e26724caf6fa074c20002db4ae174f636d68350b/deployments/deployment-57073.json)
* [Arc deployment](https://github.com/flayerlabs/nftx-v4-protocol/blob/804c2d0/deployments/deployment-5042.json)
* [ApeChain deployment](https://github.com/flayerlabs/nftx-v4-protocol/blob/878bafb/deployments/deployment-33139.json)
* [Robinhood Chain deployment](https://github.com/flayerlabs/nftx-v4-protocol/blob/e26724caf6fa074c20002db4ae174f636d68350b/deployments/deployment-4663.json)
* [Ethereum Sepolia (testnet) deployment](https://github.com/flayerlabs/nftx-v4-protocol/blob/e26724caf6fa074c20002db4ae174f636d68350b/deployments/deployment-11155111.json)
* [Robinhood Chain Testnet deployment](https://github.com/flayerlabs/nftx-v4-protocol/blob/e26724caf6fa074c20002db4ae174f636d68350b/deployments/deployment-46630.json)

Transfer paths: [Locker](https://github.com/flayerlabs/nftx-v4-protocol/blob/e26724caf6fa074c20002db4ae174f636d68350b/src/contracts/Locker.sol), [Listings](https://github.com/flayerlabs/nftx-v4-protocol/blob/e26724caf6fa074c20002db4ae174f636d68350b/src/contracts/Listings.sol), [NFTXZap](https://github.com/flayerlabs/nftx-v4-protocol/blob/e26724caf6fa074c20002db4ae174f636d68350b/src/contracts/zaps/NFTXZap.sol), and [NFTTransferLib](https://github.com/flayerlabs/nftx-v4-protocol/blob/e26724caf6fa074c20002db4ae174f636d68350b/src/contracts/libraries/NFTTransferLib.sol).

When an operator is redeployed, update this table and the deployment reference, and arrange collection-team approval of the replacement before routing users through it.
