AntiVampAntiVamp

How it works

From reservation to enforced protection.

AntiVamp is a shared registry that launchpads check before accepting a launch. Reserve once, and the identity is protected everywhere AntiVamp is integrated.

The lifecycle

Four stages, one registry

1

Reserve

A creator reserves a normalized name + ticker pair for a fixed duration — 24 hours, 3 days, 7 days, or 30 days. The fee is flat, paid in the chain's native asset or a supported stable, and non-refundable. Only one wallet is bound as the authorized launcher.

2

Launch

The authorized wallet launches the reserved pair through any participating launchpad. If another wallet attempts to launch the same normalized identity, the launchpad's pre-flight check blocks it before the transaction is accepted.

3

Extend

Reaching a bonding curve or a verified market-cap milestone (~$1M) extends protection automatically. Reserved launches earn longer locks than unreserved ones — the incentive to reserve compounds as a token gains traction.

4

Enforce

Every integrated launchpad queries the AntiVamp registry before accepting a launch. The longest valid protection window always wins, regardless of which chain or platform holds it.

Normalization rules

Same identity, however it's typed

Copycats rely on cosmetic differences — casing, spacing, near-identical tickers. Normalization removes that loophole before a check ever runs.

Case folding

Names and tickers are upper-cased and whitespace-collapsed before comparison, so “Green Robin” and “GREEN ROBIN” resolve to the same identity.

Length bounds

Names must be 1–64 characters; tickers must be 2–10 characters. Out-of-range pairs are rejected before a reservation is created.

Combined key

Protection is keyed on the name + ticker pair together, not either field alone, matching how traders actually search for and mistake tokens.

Cross-chain identity

The same normalized key is checked across every integrated chain, so a reservation on one network is visible to launchpads on another.

Protection logic

Criteria-based. Time-limited.

New locks never shorten an existing longer lock. Bond locks fire on-chain. Market-cap milestones require authorized verification so fake FDV spikes cannot extend protection.

TriggerDuration
Reserved launch that bonds60 days
Unreserved launch that bonds48 hours
Reserved @ ~$1M market cap90 days
Unreserved @ ~$1M market cap7 days

Full rules in documentation.

Reservation limits

Guardrails that keep the registry honest

Max active reservations per wallet3
Renewal window before expiry12 hours
Reservation feeFlat, non-refundable
Deploys a token?No — reservation only

See the full protection-window table above, or read the documentation for edge cases.

For launchpads

Validate before you launch

Partner launchpads normalize the pair, call AntiVamp, and allow or block.

Developer docs
POST /v1/launches/validate
{
  "chain": "base",
  "name": "GREENROBIN",
  "ticker": "ROBIN",
  "launcher": "0x7a1b…0abc"
}
200 response
{
  "normalizedName": "GREENROBIN",
  "normalizedTicker": "ROBIN",
  "status": "protected",
  "decision": "block",
  "authorizedLauncher": "0x7a1b…0abc",
  "protectedUntil": "2026-09-14T18:00:00Z",
  "reason": "reserved_launch_bonded"
}

Running a launchpad?

Integrate the enforcement check and stop copycats before they ever reach your users.

See launchpad integration