Skip documentation navigation

Custom hooks

Custom launches use release-specific Uniswap v4 hook logic with behavior and controls defined by each release.

What Custom is

A Custom launch creates a token whose Uniswap v4 market uses hook logic defined for that release. The hook can change how swaps, fees, liquidity or other permitted callbacks work.

Current availability

Custom releases are activated individually. Approved applicants can launch an approved release through the gated flow. General public submissions and open public wallet self-service are unavailable.

Behavior varies by release

Do not infer one Custom release's permissions, controls, fee path or liquidity path from another. Use the deployment and release records for the launch you are inspecting.

Release requirements

Before activation, a release must define the following information.

  • The allowed token and pool configuration.
  • The fee path, reward recipients and mutable controls.
  • Liquidity custody and every withdrawal path.
  • Transaction preparation, simulation and wallet validation.
  • Deployment records, runtime verification and supported network.

Launch-specific information

Read the launch's token, pool, hook and release records together. They identify the deployed contracts, supported network, hook permissions, fee and reward path, mutable controls, liquidity custody and any withdrawal path. Project artwork, descriptions and links are presentation data and are not substitutes for these records.

Router provenance

A Custom launch executed and stamped through the Launch Stamp Router can be identified by its canonical Router origin, launch ID, launch kind, token, pool and recorded components. The published verification procedure must pass before an application uses that provenance. The published start block is the first block to scan for this Router. It does not cover earlier launches, and direct factory calls remain outside the Router record even when they occur later.

What activation does not prove

Activation makes the configured release path available. It does not establish current tradability, liquidity, price, pool state, support in an external terminal or the behavior of an interface outside the release. Project artwork, descriptions and links do not verify the hook or make another launch path available.