About
Infrastructure for the launch layer, not another launchpad.
AntiVamp doesn't compete with launchpads — it protects the creators who use them, and gives launchpads a shared way to reject copycats.
Origin
Built out of Novamp
AntiVamp started as an internal need inside Novamp: launches were repeatedly undercut by copycat tokens that reused a successful name and ticker on a different platform, splitting liquidity and confusing traders in the process.
The fix couldn't live inside a single launchpad — copycats launch wherever enforcement is weakest. So the registry was pulled out into a standalone, cross-chain, cross-launchpad service that any platform can query.
Where we are
Phase 1, shipping toward Phase 3
Novamp protection is live today: on-chain reservations, copycat locks, and a public identity check. The cross-chain identity index and partner launchpad network are actively being built.
We'd rather ship a working registry for one launchpad than promise a perfect standard for all of them — see the changelog for what's actually shipped.
Principles
How the registry behaves
Criteria-based, not discretionary
Protection is granted and enforced by fixed rules — reservation status, bond events, verified milestones. No manual overrides on who gets protected.
Time-limited by design
Every lock has an expiration. Identities return to public availability once protection lapses and no other valid lock applies.
Transparent and verifiable
Reservations and locks are recorded on-chain or in a public registry. Anyone can check an identity's status without trusting AntiVamp's word for it.
Non-custodial
AntiVamp never holds a creator's token, treasury, or liquidity. It holds a registry entry — a name, a ticker, an authorized wallet, and an expiry.
See the roadmap
Directional phases toward a shared, industry-wide identity standard.