> 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/how-it-works/flex-pools.md).

# Flex Pools

Pair a collection's floor token with any token you like — USDC, another project's token, ETH — in extra Uniswap V4 pools beside the canonical flETH pool.

Every collection on NFTX launches with one Uniswap V4 pool: its floor token against **flETH**, created by the [Locker](https://docs.nftx.io/contracts/locker.md) through the [NFTX V4 Hook](https://docs.nftx.io/contracts/nftx-v4-hook.md). That pool is still the heart of a collection's market. **Flex pools** add to it. A flex pool pairs the *same* floor token with a different token — USDC, a partner project's token, or plain ETH — in a second Uniswap V4 pool that runs on the [NFTX Flex Hook](https://docs.nftx.io/contracts/nftx-flex-hook.md).

Anyone can open one. Nothing about the collection, its vault, or its existing pool changes when they do.

## Canonical pool and flex pools

Both kinds of pool trade the same floor token, and that token is still redeemable 1:1 for a floor NFT through the Locker. That shared redemption anchors every pool to the collection's floor: if MILADY trades cheaper in a MILADY/USDC pool than in the MILADY/flETH pool, someone can buy it there, redeem a Milady, and sell it where it is dearer, until the two agree.

The pools are otherwise independent. Each has its own liquidity, its own price, its own LP positions and its own fee accounting. The differences that matter:

|                                                     | Canonical pool                                    | Flex pool                                |
| --------------------------------------------------- | ------------------------------------------------- | ---------------------------------------- |
| Pair token                                          | flETH, always                                     | Any token the whitelist allows (v1: any) |
| Created by                                          | The Locker, once per collection                   | Anyone, any number per collection        |
| Hook                                                | `NFTXV4Hook`                                      | `NFTXFlexHook`                           |
| Swap fee                                            | Dynamic, set by the hook                          | Dynamic, set by the hook (same model)    |
| AMM fee to the protocol                             | Yes                                               | Yes                                      |
| Listing-tax donations                               | Yes — every listing fee is donated into this pool | No                                       |
| Used by NFTX's own flows (Zap, Launchpad, Listings) | Yes                                               | Not yet                                  |

That last two rows are the honest caveat. Listing fees are routed **only into the canonical pool** (see [Fees](https://docs.nftx.io/core-concepts/fees.md)), so a flex pool's LPs earn swap and AMM fees but none of that extra yield. Expect a flex pool's returns to trail the canonical pool's, and its liquidity to stay thinner unless the pair itself is the attraction — a stablecoin, or a token a community already holds.

## Who can create a flex pool

Anyone. Pool creation is permissionless at the Uniswap V4 `PoolManager`; the Flex Hook only checks the pool's shape, then lets it through. Whether a pair token is acceptable is decided by a small separate contract, the **pair-token whitelist**, which the hook's owner can swap for a stricter one later without touching the hook.

The first whitelist, `OpenPairTokenWhitelist`, says yes to every pair — native ETH included. So from day one a collection's floor token can be paired with any ERC-20.

{% hint style="info" %}
Native-ETH flex pools exist on-chain, but the NFTX app does not add liquidity to them yet. If you want a floor-token/ETH pool today, create and fund it through Uniswap's own interface; the NFTX app will list it on the collection's Pools tab once it holds enough of the floor token.
{% endhint %}

## The rules the hook enforces

When a pool is initialised on the Flex Hook, the hook checks, in order:

1. **Pool creation is not paused.** The owner has an emergency switch. Pausing only blocks *new* pools; existing pools keep trading.
2. **The fee is dynamic.** Flex pools use Uniswap V4's dynamic-fee flag so the hook sets the swap fee, exactly as canonical pools do. A static-fee pool is refused.
3. **The tick spacing is 10, 60 or 200.** 60 matches the canonical pools; 200 suits volatile pairs; 10 suits tight ones. Anything else is refused.
4. **Exactly one side is a floor token.** One currency must be a collection token registered on the Locker, and the other must not be. Pools pairing two floor tokens are refused in this first version.
5. **Neither side is flETH.** A floor-token/flETH pool would duplicate the canonical pool without its listing-tax donations, so the hook rejects it outright — this is the one rule the whitelist cannot override.
6. **The pool was not previously retired** (see below).
7. **The whitelist approves the pair.** The hook asks `isPairTokenAllowed(collectionToken, pairToken)`; a `false` refuses the pool.

If every check passes, the hook records the pool, seeds its price oracle, and emits `FlexPoolInitialized`. Liquidity is then added through Uniswap's `PositionManager` like any other V4 pool.

## Adding liquidity

### On nftx.io

Each collection page has a **Pools** tab listing every Uniswap V4 pool that holds the collection's floor token — canonical, flex, and pools with no NFTX hook at all. Pools holding at least **$100** of the floor token lead the table; smaller ones are shown dimmed below. Each row shows the pair, the hook, the fee, both sides' depth, TVL, price, volume, fee APR and the pool's share of the eligible depth. **Add liquidity** on any NFTX-hooked row opens the add-liquidity page pointed at that pool; pools without an NFTX hook link out to Uniswap.

On the add-liquidity page, the **Pool** section at the top asks which pool the position goes into:

* **Existing pools** — pick one of the collection's NFTX-hooked pools.
* **New pairing** — paste the address of the token you want to pair with. The app checks on-chain that it is a real ERC-20 (and not the floor token, not flETH, and not a token that already has a pool), then asks for a tick spacing and an opening price. Creating the pool and minting your first position happen in the same transaction.

{% hint style="warning" %}
The Pools tab and the Pool section are rolling out on nftx.io behind a feature flag. Until they are switched on for everyone, use Uniswap's interface below — the pools are the same either way.
{% endhint %}

### On Uniswap

Any flex pool is an ordinary Uniswap V4 pool. In Uniswap's position creator, choose the floor token and your pair token, select **dynamic fee**, pick a tick spacing of 10, 60 or 200, and set the hook to the Flex Hook address for the chain (`0xC26A5Cb51b1818F62a4C6693a9a1feDB3340efc4` on Ethereum Mainnet). If the pool does not exist yet, Uniswap initialises it and mints your position together.

One thing to know if you script this: `PositionManager.initializePool` swallows a hook revert and returns without creating the pool. Read `poolParams(poolId).initialized` on the hook afterwards, or call `PoolManager.initialize` directly so a refusal reverts loudly.

## Fees on a flex pool

Flex pools use the same fee model as canonical pools, run by the same shared hook logic:

* **LP fee.** Dynamic, resolved by the hook per pool, with the same per-origin fee exemptions the canonical hook offers. The Flex Hook starts with the canonical hook's default (0.9% on Ethereum Mainnet at deployment) and the owner can set a pool-specific override.
* **AMM fee.** A protocol fee taken from every swap's unspecified leg (0.1% at deployment) and credited to the protocol's fee receiver through the hook's escrow. On a flex pool this fee is whatever token that leg is in — USDC in a USDC pool, ETH in a native pool — and the hook credits what actually arrived, so a pair token that charges a transfer fee cannot leave the escrow short.

What flex pools do **not** receive is listing tax: those donations only ever reach the canonical pool.

## Existing collections

A collection does not need to do anything to gain a flex pool, and it cannot prevent one. Take Milady: its floor token is registered on the Locker, its canonical MILADY/flETH pool has been live since launch, and neither fact changes. Anyone can now initialise a MILADY/USDC pool on the Flex Hook and fund it. The Locker, Listings and the canonical hook are not involved and need no update.

## What is not possible yet

* **One purchase drawing on two pools.** The [Zap](https://docs.nftx.io/contracts/zap.md) — the contract behind "buy this NFT with ETH" — resolves exactly one pool per collection, the canonical one, and settles in flETH only. A buy that sources floor tokens from both the canonical pool and a flex pool in a single transaction needs a flex-aware zap, which is planned but not deployed. Until then, flex pools are for trading and providing liquidity in the floor token itself; NFT buys and sells still route through the canonical pool.
* **Two floor tokens in one pool.** Refused by the hook in v1.
* **Adding liquidity to a native-ETH pool from the NFTX app.** Use Uniswap.

## Retired pools

The Locker never "un-registers" a floor token, so when a collection is [wound down](https://docs.nftx.io/how-it-works/collection-lifecycle.md), a flex pool would otherwise keep quoting a token that can no longer be redeemed. The hook's owner can **deregister** such a pool: swaps on it revert from then on, liquidity can still be withdrawn, and the pool can never be re-opened. This is part of the shutdown runbook, not a routine control.

## Risks to weigh before you provide liquidity

* **Thinner liquidity and lower yield than the canonical pool.** No listing-tax donations reach a flex pool.
* **Prices can diverge between venues** until arbitrage closes the gap. Redemption bounds the gap, but it does not remove it.
* **The whitelist is open in v1.** Any token can be paired, including tokens with odd transfer behaviour. The hook protects its own fee escrow against that; it cannot protect the pool's LPs from a pair token that misbehaves.
* **The opening price of a new pool is set by whoever creates it.** Check it before adding to a pool someone else opened.
* **Native pools split ETH liquidity** with the canonical flETH pool. If that proves harmful, a stricter whitelist can deny `address(0)` for new pools; it would not close existing ones.

For the contract-level detail — every error, event and admin function — see the [NFTX Flex Hook](https://docs.nftx.io/contracts/nftx-flex-hook.md) reference.
