> For the complete documentation index, see [llms.txt](https://docs.antivamp.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.antivamp.io/readme.md).

# Welcome to AntiVamp

One registry. Every launchpad. No copycat launches. — the cross-launchpad token identity-protection network.

AntiVamp is a cross-launchpad **identity-protection network**. It protects the combined, normalized **Name + Ticker** identity of a token so participating launchpads can detect and prevent unauthorized **copycat** launches across every supported chain.

## Overview

AntiVamp never launches tokens for you. Creators reserve identities; launchpads validate every launch against the shared registry and enforce a signed decision before the token is created.

|                       |                                                                                   |
| --------------------- | --------------------------------------------------------------------------------- |
| **What is protected** | The normalized `Name + Ticker` pair — not price, contract security, or legitimacy |
| **Who enforces it**   | Integrated launchpads, at launch time, server-side                                |
| **Authority**         | On-chain registry + Ed25519-signed API decisions                                  |
| **Chains**            | Solana · Base · BNB Chain · Robinhood Chain · Ethereum · Hyperliquid              |

{% hint style="info" %}
Identity protection is not a guarantee of a token’s value, safety, or investment performance. See the [Risk Disclosure](/legal-and-security/risk-disclosure.md).
{% endhint %}

## How protection works

A reservation is only as strong as the launchpad that enforces it. Every integrated launchpad follows the same sequence:

|        | Step         | What happens                                                                                                                   |
| ------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------ |
| **01** | **Reserve**  | A creator locks a normalized Name + Ticker for a duration. The hold is recorded on-chain and in the shared registry.           |
| **02** | **Validate** | At commit time the launchpad backend calls `POST /v1/launches/validate` with the final identity and launcher wallet.           |
| **03** | **Enforce**  | The launchpad verifies the Ed25519 signature and fails closed on `block`, `recheck_required`, expiry, or outage.               |
| **04** | **Report**   | After a successful launch confirms on-chain, the launchpad reports it so the registry moves to the protected / launched state. |

{% hint style="danger" %}
Integrating the API is not enough. Every launch path — UI, API, admin tools, and direct contracts — must enforce the signed decision. See the [Production Enforcement Guide](/for-launchpads/enforcement-guide.md).
{% endhint %}

## Start here

| I want to…                           | Go here                                                              |
| ------------------------------------ | -------------------------------------------------------------------- |
| Protect a Name + Ticker              | [Reserve a Name + Ticker](/for-creators/reserve.md)                  |
| Check whether an identity is held    | [Check an Identity](/for-creators/check-an-identity.md)              |
| Integrate my launchpad               | [Partner Quickstart](/for-launchpads/quickstart.md)                  |
| Prove we block unauthorized launches | [Production Enforcement Guide](/for-launchpads/enforcement-guide.md) |
| Call the API or install the SDK      | [Developer Overview](/developers/overview.md)                        |
| Browse exact endpoint schemas        | [API Reference](https://antivamp.io/api)                             |

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>For creators</strong></td><td>Reserve, check, launch with protection, and understand post-launch locks.</td><td><a href="/for-creators/overview.md">Creator Overview</a></td></tr><tr><td><strong>For launchpads</strong></td><td>Validate launches, verify signatures, process webhooks, and ship to production.</td><td><a href="/for-launchpads/overview.md">Partner Overview</a></td></tr><tr><td><strong>For developers</strong></td><td>Auth, environments, SDK, errors, rate limits, and the full API reference.</td><td><a href="/developers/overview.md">Developer Overview</a></td></tr></tbody></table>

## What AntiVamp gives you

| Capability                 | Detail                                                                                                                              |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Identity normalization** | Folds each Name + Ticker to one confusables-aware key so casing, leet, symbols, and homoglyphs cannot smuggle a look-alike through. |
| **Reservations**           | Time-limited, on-chain holds enforced across every integrated launchpad.                                                            |
| **Pre-launch validation**  | Signed `allow` / `allow_authorized_only` / `block` / `recheck_required` decisions — or HTTP 503 on outage (fail closed).            |
| **Post-launch protection** | Bond and market-cap milestone locks that extend copycat protection after launch.                                                    |
| **Webhooks**               | HMAC-signed lifecycle events for reservations, launches, and protection state.                                                      |
| **SDK & sandbox**          | Type-safe client with `enforceLaunch`, plus a self-serve sandbox before production keys.                                            |

## Integration surface

Partners and indexers use two surfaces: these guides, and the machine-readable API.

| Surface                 | URL                                          |
| ----------------------- | -------------------------------------------- |
| Documentation           | [docs.antivamp.io](https://docs.antivamp.io) |
| Website                 | [antivamp.io](https://antivamp.io)           |
| API portal              | [antivamp.io/api](https://antivamp.io/api)   |
| OpenAPI                 | `GET /api/v1/openapi`                        |
| Signing keys            | `GET /api/v1/keys`                           |
| Identity check (public) | `GET /api/v1/identity/check`                 |
| Launch validation       | `POST /api/v1/launches/validate`             |

## Support

Hands-on help for launchpad integrations, enforcement reviews, and production onboarding:

|              |                                            |
| ------------ | ------------------------------------------ |
| **Partners** | <partners@antivamp.io>                     |
| **Support**  | <support@antivamp.io>                      |
| **Security** | <security@antivamp.io>                     |
| **X**        | [@antivamp\_io](https://x.com/antivamp_io) |

Complete the sandbox bypass test in the [Production Enforcement Guide](/for-launchpads/enforcement-guide.md) before requesting a production key.

***

## Continue exploring

* [What Is AntiVamp?](/welcome/what-is-antivamp.md) — the network in one page
* [What Is Vamping?](/welcome/what-is-vamping.md) — the threat we stop
* [How the Network Works](/welcome/how-it-works.md) — the full flow
* [Supported Chains](/welcome/supported-chains.md) — where AntiVamp is live
* [Official Links](/resources/links.md) — verified surfaces and contacts


---

# 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.antivamp.io/readme.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.