> For the complete documentation index, see [llms.txt](https://docs.novamp.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novamp.io/identity-protection/reserving-a-name-and-ticker.md).

# Reserve a Name + Ticker

Reserving holds your `Name + Ticker` pair together for a fixed window so nobody can front-run your launch or squat your identity.

{% hint style="info" %}
Reserving is **optional** and pre-launch — it deploys nothing. During your window, only your authorized wallet can launch that exact pair. Any free, unlocked pair is launchable by anyone.
{% endhint %}

## Overview

A reservation is a paid hold on the combined [`Name + Ticker` identity](/identity-protection/what-is-antivamp.md), recorded on-chain by the `TickerReservationRegistry` for the chain you reserve on. It's the strongest pre-launch protection: it guarantees the identity is waiting for you, and if you later reach a market-cap goal, a reserved launch earns the **longest** [post-launch protection](/identity-protection/post-launch-protection.md) windows.

Reservations are time-limited. There are **no permanent locks** — the only non-time-limited state anywhere in AntiVamp is a manual guardian block on an abusive identity.

## How it works

```mermaid
flowchart LR
  A[Name + Ticker] --> B[Normalize + check]
  B --> C[Pick tier + pay on-chain]
  C --> D[Reservation recorded on-chain]
  D --> E[Only your wallet can launch]
  E --> F[Launch → market-cap goal → time-limited lock]
```

1. Your `Name + Ticker` is normalized — names + tickers are folded to one canonical, confusables-aware key ([spec](https://docs.antivamp.io)) — and [checked](/identity-protection/identity-checker.md) for availability.
2. You pick a tier and pay on-chain. The USD tier converts to the exact amount via a **fail-closed** oracle (stale answer → the reservation reverts); stablecoins settle 1:1.
3. The reservation is written to that chain's `TickerReservationRegistry` and your window begins.
4. During the window, only your authorized wallet can launch the exact pair.
5. After launch, copycat protection is earned by hitting a market-cap goal — not by launching.

## How to use it

1. Open the **Reserve** page and connect the wallet you'll launch from.
2. Enter your token **name** and **ticker** — they're checked live as you type.
3. Pick your chain and a [tier](/identity-protection/reservation-tiers.md).
4. Review the quoted on-chain amount and confirm the transaction.
5. When it confirms, your identity is protected for the window. When you're ready, launch the reserved pair from the same wallet — see [Launch a Token](/creators/launching-a-token.md).

{% hint style="success" %}
Signed ≠ protected. Your reservation is only active once the transaction **confirms on-chain**, not when you sign it.
{% endhint %}

## Important details

### Tiers

| Tier            | Price      | Best for             |
| --------------- | ---------- | -------------------- |
| ⏱️ **24 hours** | **$100**   | Fast launch prep     |
| 🗓️ **3 days**  | **$250**   | Short campaigns      |
| 🛡️ **7 days**  | **$500**   | Coordinated launches |
| 🔒 **30 days**  | **$1,500** | Extended prep        |

{% hint style="danger" %}
Fees are flat and **non-refundable** — a reservation is not a launch credit and is not returned if you don't launch or let the window lapse.
{% endhint %}

### Paying

| Chain          | Native asset (via oracle)   | Stablecoins (1:1)  |
| -------------- | --------------------------- | ------------------ |
| `🟪 solana`    | **SOL** — push oracle       | —                  |
| `🟣 hyperevm`  | **HYPE** — push oracle      | —                  |
| `🔵 base`      | **ETH** — Chainlink ETH/USD | **USDC**           |
| `🟢 robinhood` | **ETH** — push oracle       | —                  |
| `🟡 bnb`       | **BNB** — Chainlink BNB/USD | **USDC**, **USDT** |
| `⚪ ethereum`   | **ETH** — Chainlink ETH/USD | **USDC**, **USDT** |

You pay in the native asset of the chain you reserve on, or an accepted stablecoin. Contract and program addresses: [Contracts & addresses](/protocol/contracts-and-addresses.md).

### Anti-Sybil

To stop one wallet hoarding identities, each additional active reservation on the same wallet **costs more** than the last, and there's a **per-wallet cap** on active reservations.

### What protection you get

| Stage                                           | Protection                                            |
| ----------------------------------------------- | ----------------------------------------------------- |
| During your reservation window                  | Only your authorized wallet can launch the exact pair |
| Bare launch (mint only)                         | None — launching alone never locks a ticker           |
| Reserved launch hits market-cap graduation goal | **60 days** copycat lock (48h if unreserved)          |
| Reserved launch hits \~$1M market cap           | **90 days** copycat lock (7d if unreserved)           |

Locks apply `max(existingUntil, now + duration)` — a new lock never shortens a longer one. See [Post-Launch Protection](/identity-protection/post-launch-protection.md) for the full model.

## What happens next?

* Your reserved identity shows a [Protected badge](/identity-protection/protected-badge.md) and appears in your wallet's holds.
* Launch the pair any time during the window from your authorized wallet.
* If the window lapses without a launch, the identity frees up again — the fee is not returned.

## Troubleshooting

| Symptom                                 | Fix                                                                                                      |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| Reservation reverted with a price error | The oracle was stale (fail-closed) — retry shortly.                                                      |
| Cost higher than the listed tier        | Anti-Sybil escalation — you already hold active reservations.                                            |
| "Reservation cap reached"               | You've hit the per-wallet limit — let one lapse or launch it.                                            |
| Identity shows as taken                 | Someone reserved or protected it — [check it](/identity-protection/identity-checker.md) or pick another. |
| You believe a block is wrong            | AntiVamp guardians can reverse mistakes — see <https://docs.antivamp.io>.                                |

{% hint style="warning" %}
Reserving protects your **identity**, not your token's value or legitimacy. It reduces `Name + Ticker` copycats; it does not guarantee a token is safe. See [Risk Disclosure](/legal-and-safety/risk-disclosure.md).
{% endhint %}

## Continue exploring

* [💰 Reservation Tiers](/identity-protection/reservation-tiers.md)
* [🎓 Post-Launch Protection](/identity-protection/post-launch-protection.md)
* [🚀 Launch a Token](/creators/launching-a-token.md)
* [🛡️ What Is AntiVamp?](/identity-protection/what-is-antivamp.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://docs.novamp.io/identity-protection/reserving-a-name-and-ticker.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.