vamp guard

live on mainnet

A vamp is when someone watches a coin start working, ships the identical ticker, and takes the buyers with it. Every launchpad allows this because a ticker is a string in a metadata file. Nothing stops a thousand $PEPEs.

Vamp guard makes the ticker an account instead of a string. Claiming one derives a program address from the ticker itself, and an address can only be created once, so the second claim is rejected by the runtime rather than by a rule we promise to keep.

program: ↗
ticker rules: 2-10 characters, a-z and 0-9, case-insensitive

how a ticker becomes an address

The registry account for a ticker is derived from the ticker itself, so anyone can compute it and check a claim without trusting this site:

find_program_address(
  [b"ticker", b"vampy"],
  6WPwJF51FVLq2E6ssTRFDBiu5aTMGHyUZhPB7vinQ1f,
)
→ 4GhVq7zitxA3YUvfBtgLNeyfHuc6Z85hbtyP93vdBhjx

instructions

claim_ticker

Creates the registry PDA seeded by the lowercased ticker and writes the mint into it. Fails with TickerTaken if the account already exists.

deploy

CPIs into the curve program to mint. Rejects unless the ticker claim is in the same transaction.

bind_launch

Writes the launch record: mint, ticker, deployer, slot. This is what the site reads to prove a coin came through vamp guard.

errors

TickerTaken	the registry PDA for this ticker already exists
TickerMalformed	not 2-10 alphanumeric characters
ClaimNotAtomic	the ticker claim was not in the same transaction as the mint

Nothing here is financial advice. A guarded ticker is not a guarantee that a coin is good.