> For the complete documentation index, see [llms.txt](https://gabriel-j-shapiro.gitbook.io/metalex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gabriel-j-shapiro.gitbook.io/metalex-docs/protocol-how-to-guides/deploy-liquilex-pool.md).

# Deploy a LiquiLeX pool

**LiquiLeX** provides AMM-native secondary liquidity for cyberSCRIP using Uniswap v4 pools, with the **`MetalexIssuerFeeHook`** routing swap fees to MetaLeX and the issuer.

## Prerequisites

* A cyberCORP with a deployed `CyberScrip` for the class you want to make liquid (see [Tutorial 3](/metalex-docs/protocol-tutorials/scripify-and-settle.md)).
* A chosen compliance model:
  * **Whitelisted pool** — a `WhitelistTransferHook` on the cyberSCRIP, with the pool address whitelisted; full credential checks at the swap layer.
  * **Open pool** — no transfer hook; compliance enforced at the de-scripification boundary, optionally with a zkPassport check at swap.

## Approach

1. Deploy the `MetalexIssuerFeeHook` ([`src/hooks/uniswap/`](https://github.com/MetaLex-Tech/cybercorps-contracts/tree/develop/src/hooks/uniswap)). Uniswap v4 imposes hook-address-suffix requirements, so deploy at a mined address (the standard `HookMiner` salt-mining flow).
2. Initialise a Uniswap v4 pool pairing the `CyberScrip` against a stablecoin, with `hooks` set to the deployed fee hook.
3. Seed liquidity. If the cyberSCRIP has a `WhitelistTransferHook`, whitelist the pool address.

> The `MetalexIssuerFeeHook` constructor and fee configuration are not reproduced here — consult the contract source for the current shape.

## Related

* [Hooks](/metalex-docs/protocol-reference/hooks.md), [CyberScrip](/metalex-docs/protocol-reference/contracts/cyberscrip.md).
* Explanation: [Composability and DeFi](/metalex-docs/protocol-explanation/composability.md).


---

# 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://gabriel-j-shapiro.gitbook.io/metalex-docs/protocol-how-to-guides/deploy-liquilex-pool.md?ask=<question>&goal=<endgoal>
```

`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.