> 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/what-is-antivamp.md).

# Identity Protection on Novamp

Novamp protects every token's **name + ticker** identity — powered by AntiVamp, a cross-launchpad identity-protection network that stops copycats from reusing that identity to siphon attention and liquidity.

> **One registry. Every launchpad. No copycat launches.**

{% hint style="info" %}
AntiVamp is a **separate protocol** with its own network, normalization spec, partner API, and SDK. Novamp is one of its launchpad customers. For protocol depth, integration, and the full reference, see <https://docs.antivamp.io>.
{% endhint %}

{% hint style="info" %}
AntiVamp protects a project's **identity** — its `Name + Ticker` pair — not its price, its team, or its investment outcome. Partner launchpads integrate the same registry and honor its decisions.
{% endhint %}

## Overview

Every token has a public identity: the **name** people read and the **ticker** they trade. Scammers exploit that by launching look-alikes — same name, same ticker, or a deceptively similar variant — to hijack a real project's momentum. AntiVamp treats that identity as something worth defending.

AntiVamp does three things:

* **Normalizes identity** — names + tickers are folded to one canonical, confusables-aware key, so homoglyphs, symbols, casing, and hidden characters can't smuggle a look-alike past the check (full normalization spec at <https://docs.antivamp.io>).
* **Protects identity across chains and launchpads** — reservations and post-launch locks are recorded on-chain and enforced everywhere AntiVamp integrates, not just on Novamp.
* **Publishes identity status** — anyone can check an identity or read the [Protected-by-AntiVamp badge](/identity-protection/protected-badge.md) with no API key.

It protects the **combined** identity `Name + Ticker`, not the ticker alone. Two projects can share a ticker if their names differ; the copycat problem is reusing *both*.

AntiVamp spans these chains:

`🟪 solana` · `🟣 hyperevm` · `🔵 base` · `🟢 robinhood` · `🟡 bnb` · `⚪ ethereum`

## How it works

```mermaid
flowchart LR
  A[Name + Ticker] --> B[Normalize v2]
  B --> C[Check registry]
  C --> D[Reserve optional]
  D --> E[Validate launch]
  E --> F[Report milestones]
  F --> G[Post-launch protection]
```

1. A creator's `Name + Ticker` is **normalized** to a canonical identity key (`NAME::TICKER`).
2. The key is **checked** against the on-chain registries for existing reservations or active protection.
3. The creator may **reserve** the identity for a fixed window so nobody else can launch it first.
4. At launch, the integrated launchpad **validates** the identity with AntiVamp and honors the decision.
5. Keepers **report** launch and market-cap milestones back to AntiVamp.
6. When a launch reaches its market-cap graduation goal, **post-launch protection** fires as a time-limited cross-chain copycat lock.

## How to use it

* **Creators** — [check an identity](/identity-protection/identity-checker.md), then optionally [reserve your Name + Ticker](/identity-protection/reserving-a-name-and-ticker.md) before you launch.
* **Traders** — look for the [Protected-by-AntiVamp badge](/identity-protection/protected-badge.md) and check any identity yourself, free.
* **Launchpads** — integrate the validation API and honor AntiVamp decisions on every launch — see <https://docs.antivamp.io>.

## Important details

| Property             | Detail                                                                                              |
| -------------------- | --------------------------------------------------------------------------------------------------- |
| What it protects     | The combined, normalized `Name + Ticker` identity                                                   |
| Scope                | Cross-launchpad and cross-chain — one shared registry                                               |
| Reservation model    | Flat, non-refundable, time-limited windows (see [tiers](/identity-protection/reservation-tiers.md)) |
| Post-launch locks    | Time-limited, triggered by market-cap goals — **no permanent locks**                                |
| Only permanent state | A manual **guardian block** for abusive identities (guardian-reversible)                            |
| Public surfaces      | Identity checker and Protected badge — no API key required                                          |
| Enforcement          | Cross-chain guardian fan-out to each chain's on-chain registry                                      |

## What happens next?

* A reserved identity is held for you during your window; only your authorized wallet can launch it.
* A launch that hits its market-cap goal earns a time-limited copycat lock across every AntiVamp chain.
* When a lock lapses, the identity frees up again — protection is never a silent forever-ban.

## Troubleshooting

| Symptom                          | What it means                                                                                                                         |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| "Identity unavailable" at launch | The Name + Ticker is reserved or protected — pick another or [reserve it](/identity-protection/reserving-a-name-and-ticker.md) first. |
| Non-ASCII identity rejected      | The identity can't fold to a valid ASCII key — see the normalization spec at <https://docs.antivamp.io>.                              |
| You believe a block is wrong     | AntiVamp guardians can reverse mistakes — see <https://docs.antivamp.io>.                                                             |

{% hint style="warning" %}
AntiVamp reduces `Name + Ticker` copycats. It is **not** a guarantee that a token is safe, legitimate, or a good investment. Always do your own research — see [Risk Disclosure](/legal-and-safety/risk-disclosure.md).
{% endhint %}

## Continue exploring

* [🧛 What Is Vamping?](/identity-protection/what-is-vamping.md)
* [🔒 Reserve a Name + Ticker](/identity-protection/reserving-a-name-and-ticker.md)
* [🎓 Post-Launch Protection](/identity-protection/post-launch-protection.md)
* [📖 AntiVamp Documentation](https://docs.antivamp.io)


---

# 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/what-is-antivamp.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.