> 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/partners/antivamp_partner_package.md).

# Partner Package

*Version 2026-07-16 · antivamp.io · Confidential draft for prospective launch platform partners*

***

## 1. One-page overview

**AntiVamp is the shared identity-protection layer for token launchpads.**

Creators reserve a token **name + ticker pair** for a fixed window. Integrated launchpads query AntiVamp before accepting a launch, so a protected identity cannot be copied ("vamped") on any participating platform — including look-alikes: `R0BIN`, `$ROBIN`-style dollar prefixes, and full-width unicode all fold to the same canonical identity.

**Protection model (current defaults):**

| Trigger                                        | Lock                                                     |
| ---------------------------------------------- | -------------------------------------------------------- |
| Active reservation                             | 24h / 3d / 7d / 30d (creator-paid, flat, non-refundable) |
| Reserved launch that bonds                     | 60 days                                                  |
| Unreserved launch that bonds                   | 48 hours                                                 |
| Reserved launch verified at \~$1M market cap   | 90 days                                                  |
| Unreserved launch verified at \~$1M market cap | 7 days                                                   |

Rules that never bend: the **longest valid lock wins**, new locks **never shorten** existing protection, market-cap milestones require **authorized keeper verification** (manipulated FDV spikes cannot extend protection), and all protection is **time-limited and publicly verifiable** — no arbitrary permanent bans. Guardians can clear mistaken blocks; corrections appear in the public timeline.

**Why integrate:** protect legitimate creators, cut copycat scams on your platform, and show a verifiable protection standard your traders can check themselves at `antivamp.io/check`.

***

## 2. API quickstart (one afternoon)

Base URL: `https://antivamp.io/api/v1`

```bash
# 1. Sandbox key — instant, self-serve, free (shown exactly once)
curl -X POST https://antivamp.io/api/v1/sandbox/keys \
  -H "Content-Type: application/json" \
  -d '{"organization":"Your Launchpad","email":"dev@yourlaunchpad.xyz"}'

# 2. Validate before every launch
curl -X POST https://antivamp.io/api/v1/launches/validate \
  -H "Authorization: Bearer av_sbx_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"chain":"base","launchpad":"you","name":"Sandbox Fox","ticker":"SFOX",
       "launcher":"0x00000000000000000000000000000000000000a1"}'
```

Decisions: `allow` · `allow_authorized_only` · `block` · `recheck_required`. Treat any error or `recheck_required` as **do not launch** — AntiVamp fails closed, never open.

Every decision is **HMAC-SHA256 signed** with your per-key secret and expires after 5 minutes (no replaying stale allows). Verification snippets: `antivamp.io/developers`. Idempotent retries via the `Idempotency-Key` header.

Full lifecycle available in the sandbox: `POST /reservations` (sandbox-only seeding) → `validate` → `POST /launches/report` → `POST /events/bonded` → `POST /events/milestone` — protection extends with longest-lock semantics and the public explorer/identity pages update immediately.

**OpenAPI spec:** `https://antivamp.io/api/v1/openapi`

***

## 3. Chain support matrix

| Chain                  | Status            | Identity checks          | Reservations     | Notes                                                                                                    |
| ---------------------- | ----------------- | ------------------------ | ---------------- | -------------------------------------------------------------------------------------------------------- |
| Hyperliquid (HyperEVM) | **Live**          | Yes                      | On-chain, live   | Registry `0xC10928677f96A860Ee1D9ee3425f344dE37c7D36`                                                    |
| Solana                 | **Live**          | Yes                      | On-chain, live   | Program `BF63F2sNLXNJpMmXc6TVjAZHbcutX4jne4vE8PvAjmko` · multisig-controlled · reserve UI + validate API |
| Base                   | Integration ready | Yes (cross-chain claims) | Env-gated deploy | Chainlink ETH/USD + USDC planned                                                                         |
| Robinhood Chain        | Integration ready | Yes (cross-chain claims) | Env-gated deploy | Push oracle, fail-closed                                                                                 |
| BNB Chain              | In development    | —                        | —                |                                                                                                          |
| Ethereum               | Planned           | —                        | —                |                                                                                                          |

Live health, latest blocks, and index lag: `antivamp.io/status` (real probes, nothing simulated).

***

## 4. Normalization specification v1 (frozen)

One canonical fold for names **and** tickers, identical on-chain (`SymbolLib`), in the API, and in the index:

* Uppercase ASCII; leet digits fold (`0→O 1→I 3→E 4→A 5→S 7→T 8→B`); `$→S`, `@→A`
* Whitespace, punctuation, emoji dropped; **all non-ASCII dropped** (full-width unicode and homoglyphs cannot smuggle a look-alike past the fold)
* Identity key = `NAME::TICKER` after folding

Frozen reference vectors:

| Input                                         | Canonical                 |
| --------------------------------------------- | ------------------------- |
| `Green Robin` / `GREEN ROBIN` / `Green Robin` | `GREENROBIN`              |
| `$ROBIN`                                      | `SROBIN`                  |
| `robin`                                       | `ROBIN`                   |
| `ＲＯＢＩＮ` (full-width)                          | rejected (folds to empty) |

The complete vector suite ships in the repository (`web/src/lib/normalization.vectors.json`) and is enforced by CI tests. Any future v2 fold ships as a new registry version with documented migration — never a silent change.

***

## 5. Sandbox scenarios (pre-seeded)

| Pair                   | State                                     |
| ---------------------- | ----------------------------------------- |
| `SANDBOXFOX :: SFOX`   | Active reservation — `0x…00a1` authorized |
| `MOONBADGER :: BADGER` | Bond-protected (reserved, 60d)            |
| `IRONWHALE :: IRON`    | Milestone-protected (90d)                 |
| `NIGHTSHADE :: SHADE`  | Unreserved bond (48h)                     |
| `DUSKRAVEN :: DUSK`    | Expired                                   |
| `VAMPCOIN :: VAMP`     | Graduated identity block                  |
| `CLEARSKY :: CLEAR`    | Guardian-cleared                          |
| anything else          | Available                                 |

***

## 6. Webhook guide

Register endpoints from the partner console (`antivamp.io/integrations`) or `POST /v1/webhooks`. Events include `reservation.created`, `launch.authorized`, `launch.blocked`, `launch.reported`, `token.bonded`, `milestone.verified`, `identity.extended`, `identity.cleared`.

Every delivery is signed: `X-AntiVamp-Signature: t=<unix>,v1=<hmac-sha256>` over `"<t>.<rawBody>"` with your endpoint secret. Reject events older than your tolerance window (we recommend 5 minutes). Delivery history and replay are available in the console; process by delivery ID for idempotency.

***

## 7. Pricing discussion

Creator reservations are flat and public: $100 / 24h, $250 / 3d, $500 / 7d, $1,500 / 30d — non-refundable, not launch credits.

Creators pay in the **native asset of the chain they reserve on** — **SOL** on Solana, **HYPE** on Hyperliquid — with the USD tier converted at reservation time via a fail-closed oracle. USDC / stablecoin payment (1:1, no oracle) is on the roadmap for Solana and Hyperliquid.

Partner pricing is **not finalized** — design partners help set it. The models under discussion: usage-based validation calls, per-protected-launch, premium historical data access, and chain-specific integration tiers. **Design partners integrate free during the pilot** and receive preferred terms at general availability.

***

## 8. Getting started + technical contact

1. Create a sandbox key: `antivamp.io/integrations` (instant)
2. Integrate `validate` in your launch path (target: one afternoon)
3. Request production access: `antivamp.io/partners`

Contacts:

* Integration / technical support: **<support@antivamp.io>**
* Partnerships / production access / pricing: **<partners@antivamp.io>**
* Responsible disclosure / security: **<security@antivamp.io>**

Partner requests submitted through the site route directly to the team.

***

*AntiVamp — Protect the ticker before copycats arrive.*


---

# 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/partners/antivamp_partner_package.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.