# Saved hooks

Pools that follow a saved hook swap and pay exactly as they would without it, and saving one costs gas only.

## What a saved hook holds

| Part | What it says |
| --- | --- |
| Core | Which core its pools bind. A pool that follows a saved hook keeps the hook's own core, so a Hook Block that runs only on another core is not offered on it. |
| Blocks allowed | Any of Anti-Snipe, dynamic fees, Auto Burn, LP Rewards and the creator royalty |
| Fee ceilings | Hookr's own, or lower |
| Add-on blocks | Up to 4 to pick from. Each pool still runs one. |
| Gates | Up to 4 |
| Arbitrage recapture | Allowed or not |
| Listing | Public, so anyone can list a pool that fits, or owner-only |

## How a pool follows it

- A pool names the saved hook when it opens, and is listed under it once its frozen settings fit.
- On a public saved hook anyone can list a pool, and on an owner-only one only its owner can.
- Anyone can drop a pool the current version no longer fits, and the owner can drop any pool.
- A saved hook never changes a pool, holds no assets, and nothing on a swap reads it.

## Versions

Saving again writes a new version, and every earlier version stays readable. A saved hook's id comes from its writer and a salt, so nobody can take another writer's id.

## A hook of your own

A saved hook is also the template a hook of your own is deployed from: the same blocks at an address of your own. See [Owned roots](/docs/pools/owned-roots).

## For integrations

- A saved hook keeps Hookr's hook address, so its pools route like any Hookr pool.
- An app can read a saved hook's bounds and a complete default from chain, and pre-fill a launch from it.

---

This page: https://hookr.fun/docs/pools/saved-hooks. Every docs page as Markdown: https://hookr.fun/docs.md.
