> 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-vamping.md).

# What Is Vamping?

Vamping is launching a token under the same — or a deceptively similar — **name + ticker** as an existing or reserved project to confuse users and siphon its attention and liquidity.

{% hint style="danger" %}
A vamp doesn't need to be a perfect copy. Swapping one letter for a look-alike, adding a `$`, or using a hidden Unicode character is enough to fool a trader glancing at a ticker.
{% endhint %}

## Overview

When a real project gains traction, its **identity** — the name and ticker traders recognize — becomes valuable. A vamp exploits that recognition: it borrows the identity to intercept buyers who think they're aping the original.

The victim is usually the trader who buys the wrong token, and the legitimate creator whose momentum and liquidity get bled off. Because tickers are short and read quickly, look-alikes are dangerously effective.

## How it works

Here's a concrete example. Say a real project launches as:

`Green Robin` · ticker `ROBIN`

A vamper can try to ride it with any of these:

| Vamp attempt             | Trick used                         | Normalized identity |
| ------------------------ | ---------------------------------- | ------------------- |
| `Green Robin` / `ROBIN`  | Exact copy on another chain        | `GREENROBIN::ROBIN` |
| `Green Rоbin` / `ROBIN`  | Cyrillic `о` homoglyph in the name | `GREENROBIN::ROBIN` |
| `Green Robin` / `$ROBIN` | Extra `$` symbol on the ticker     | `GREENROBIN::ROBIN` |
| `Green​Robin` / `ROBIN`  | Hidden zero-width character        | `GREENROBIN::ROBIN` |

To a human, these look different enough to slip through and identical enough to deceive. To AntiVamp, they all fold to the **same** identity key — so once `GREENROBIN::ROBIN` is protected, every one of these attempts is caught.

## How AntiVamp stops it

```mermaid
flowchart LR
  A[Vamp attempt] --> B[Normalize v2]
  B --> C{Key matches a protected identity?}
  C -- yes --> D[Launch blocked / authorized-only]
  C -- no --> E[Launch allowed]
```

1. The vamp's `Name + Ticker` is normalized — names + tickers are folded to one canonical, confusables-aware key, so homoglyphs, symbols, casing, and hidden characters are folded away (spec at <https://docs.antivamp.io>).
2. The key is checked against the on-chain registries for an active reservation or post-launch lock.
3. If it collides with a protected identity, the integrated launchpad **refuses the launch** (or restricts it to the authorized wallet).

Because AntiVamp is a cross-launchpad network, a vamp can't just hop to a different platform or chain to escape the check — every integrated launchpad honors the same decision.

## How to use it

* **Creators** — [check your identity](/identity-protection/identity-checker.md) and [reserve it](/identity-protection/reserving-a-name-and-ticker.md) before launch so vampers can't get there first.
* **Traders** — treat the [Protected-by-AntiVamp badge](/identity-protection/protected-badge.md) as a signal you're looking at the recognized identity, and verify any token yourself.

## Important details

| Property           | Detail                                                                                   |
| ------------------ | ---------------------------------------------------------------------------------------- |
| What's targeted    | The recognizable `Name + Ticker` identity of a real project                              |
| Common tricks      | Homoglyphs, `$`/symbol padding, casing, zero-width/hidden characters, cross-chain copies |
| AntiVamp's defense | Canonical normalization + on-chain reservation and post-launch locks                     |
| Cross-launchpad    | A vamp can't escape by switching platforms or chains                                     |

## What happens next?

* If the identity is reserved or protected, the copycat launch is refused across the network.
* If it isn't protected yet, the identity stays available — which is exactly why reserving early matters.

## Troubleshooting

| Symptom                                      | What to do                                                                                                                                                                                    |
| -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You spotted a suspected vamp of your project | If it hit its market-cap goal, it may already be locked; otherwise consider [reserving](/identity-protection/reserving-a-name-and-ticker.md) and report abuse via <https://docs.antivamp.io>. |
| Your legitimate launch was flagged as a vamp | AntiVamp guardians can reverse mistakes — see <https://docs.antivamp.io>.                                                                                                                     |

{% hint style="warning" %}
Stopping copycats protects an identity, not a token's value. AntiVamp does not vouch that any token — original or otherwise — is safe or legitimate. See [Risk Disclosure](/legal-and-safety/risk-disclosure.md).
{% endhint %}

## Continue exploring

* [🛡️ What Is AntiVamp?](/identity-protection/what-is-antivamp.md)
* [✅ Identity Checker](/identity-protection/identity-checker.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-vamping.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.