/permissioned-pools-deployer

name: permissioned-pools-deployer
description: Guided walkthrough for executing the on-chain setup sequence for a Uniswap v4 Permissioned Pool from a permissioned-pools-configurator JSON config - allowlist checker deployment, createPermissionsAdapter, allowlisting and funding the adapter, verification, wrapper and hook registration, pool initialization, swap enablement, liquidity seeding, and the routing-allowlist request. Use when the user says "deploy a permissioned pool", "run the permissioned pool setup", "execute the permissioned pools journey", "createPermissionsAdapter", "verify my permissions adapter", "walk me through the permissioned pool deployment", or asks to execute the on-chain steps after generating a permissioned-pools-configurator config. Covers contract mechanics only - does not constitute legal, financial, investment, tax, or compliance advice, and is not a compliance review - and never emits a broadcastable command before an explicit acknowledgment.
allowed-tools: Read, Glob, Grep, Bash(forge:*), Bash(cast:*), AskUserQuestion
model: opus
license: MIT
metadata:
  author: uniswap
  version: '0.1.0'

Permissioned Pools Deployer

Guided, step-by-step execution of the on-chain setup sequence for a Uniswap v4 Permissioned Pool, starting from the JSON configuration `permissioned-pools-configurator` produces. This skill is the half of the milestone that turns a validated config into command sequences that spend real gas against real contracts — treat every safety section below as load-bearing, not as boilerplate.

For the contract mechanics behind any step, see [`permissioned-pools-issuer`](../permissioned-pools-issuer/SKILL.md), specifically its [Issuer Journey](../permissioned-pools-issuer/references/issuer-journey.md) and [Enforced Ordering and Reverts](../permissioned-pools-issuer/references/enforced-ordering-and-reverts.md). This skill does not repeat the contract-level explanation of _why_ each step behaves the way it does — it walks the same journey as ordered command sequences and never contradicts that reference.

> **Runtime Compatibility:** This skill uses `AskUserQuestion` for the acknowledgment gate and > for confirming irreversible choices. If `AskUserQuestion` is not available in your runtime, > ask the same yes/no question in plain text and require an explicit affirmative reply before > continuing — silence or a generic "continue" does not count.

Scope and Disclaimer

**This is educational deployment guidance, not a compliance review, and not a substitute for your own review of every command before you run it.**

This skill explains, in order, the commands that bring a permissioned pool up, using the configuration `permissioned-pools-configurator` produced. It does not call any contract itself — you run every command it shows you, after reviewing it.

**You must:**

1. ✅ **Review every configuration and every command carefully** before running anything. AI-generated command sequences may contain errors. 2. ✅ **Verify every address** — this skill contains no deployment addresses and resolves none for you; see [Address Resolution](./references/preflight-and-validation.md#address-resolution). 3. ✅ **Test on a testnet first.** Run the entire sequence on Sepolia (or another testnet with the permissioned-pools contracts deployed) before touching mainnet. 4. ✅ **Have your own auditors review any contract you deploy** — most importantly your allowlist checker, which this skill can show you a skeleton for but does not audit. 5. ✅ **Treat this as contract mechanics only.** This skill does not constitute legal, financial, investment, or tax advice, and it is **not** a compliance review of your token, your allowlist, your KYC or AML program, or your configuration. 6. ✅ **Read the repo's usage guidelines.** The repo root `DISCLAIMER.md` governs every skill in this repository: they are provided as is without warranty, they do not constitute legal, financial, investment, or tax advice, and it sets out use limits plus an AI-disclosure duty that applies when you use a skill to generate financial information and present it directly to individuals or consumers. Point the user to it.

The acknowledgment gate

**Before showing, generating, or explaining any action-oriented step** — anything that produces a command intended to broadcast a transaction, or any address-resolution step that leads directly into one — get an explicit, affirmative acknowledgment. This gate must never be satisfiable implicitly.

Use `AskUserQuestion` with a single question and exactly two options, and do not proceed past this gate until the first option is chosen:

• **Question:** "This walkthrough produces commands that spend gas and permanently change

on-chain state for your token once you run them. Do you acknowledge the six points above and want to continue?"

• **Option A — "Yes, I have reviewed the points above and want to continue."** → proceed to the

preflight checks.

• **Option B — "No, stop here."** → end the walkthrough immediately. Do not display, generate,

or explain any command below this point.

Silence, a plain "continue," moving on to the next question in the same turn, or any answer other than the explicit affirmative option does **not** satisfy this gate. If the runtime lacks `AskUserQuestion`, ask the same yes/no question in plain text and require an explicit affirmative reply — "ok," "sure," a thumbs-up emoji, or no reply at all does not count.

Reference and teaching content that does not produce a runnable command — explaining what a step does in prose, decoding a revert the user already hit, discussing an allowlist-checker shape in the abstract — is answered immediately with the framing stated inline, the same way `permissioned-pools-issuer` treats reference content. This carve-out does **not** cover this skill's own command templates and Solidity script skeletons (for example the pool-initialization script in [Step Walkthrough](./re