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

# Protected-by-AntiVamp Badge

The badge marks an identity that AntiVamp is actively protecting — a quick, verifiable signal for traders and creators.

{% hint style="info" %}
The badge is about **identity**, not endorsement. It means "this `Name + Ticker` is held or locked by AntiVamp," not "this token is safe or a good investment."
{% endhint %}

## Overview

The "Protected by AntiVamp" badge appears next to protected identities across the network. It's backed by on-chain state, so anyone can verify it — there's no trust-us claim behind it. The badge reflects a live status, and it disappears when protection lapses.

## How it works

```mermaid
flowchart LR
  A[Identity key] --> B[Check registries]
  B --> C{Reserved or locked?}
  C -- yes --> D[Show Protected badge + until]
  C -- no --> E[No badge]
```

1. The badge reads the same on-chain status as the [Identity Checker](/identity-protection/identity-checker.md).
2. If the identity has an active reservation or a post-launch lock, the badge shows as protected — often with the window end.
3. When the reservation or lock lapses, the status flips back to available and the badge clears.

## How to use it

* **Traders** — treat the badge as "this is the recognized identity," then still verify the contract and do your own research.
* **Creators** — a reserved or protected identity surfaces the badge automatically; nothing extra to enable.
* **Integrators** — read status programmatically:
  * Badge asset: `GET /api/badge`
  * Identity status: `GET /api/v1/identity/status?key=NAME::TICKER`

## Important details

| The badge **does** mean                                      | The badge **does not** mean                  |
| ------------------------------------------------------------ | -------------------------------------------- |
| The `Name + Ticker` is reserved or under a post-launch lock  | The token is safe, audited, or legitimate    |
| Copycats of this identity are blocked across AntiVamp chains | The team, price, or liquidity is vouched for |
| The status is verifiable on-chain                            | Protection is permanent (it's time-limited)  |

Status values driving the badge: `available`, `reserved`, `protected`, `expiring`, `expired`, `conflict`, `pending`, `failed`.

## What happens next?

* An `expiring` state warns that a reservation or lock ends soon — renew or launch before it lapses.
* Once a lock or reservation lapses, the badge clears and the identity can be claimed again.
* A manual **guardian block** on an abusive identity is the only non-time-limited state — see [Post-Launch Protection](/identity-protection/post-launch-protection.md).

## Troubleshooting

| Symptom                       | What it means                                                          |
| ----------------------------- | ---------------------------------------------------------------------- |
| Badge disappeared             | The reservation or lock lapsed — the identity is available again.      |
| Badge shows "expiring"        | The window ends within days — act before it lapses.                    |
| Badge on a token you distrust | The badge protects identity, not value — verify the contract yourself. |

{% hint style="warning" %}
A badge is not a safety rating. AntiVamp reduces `Name + Ticker` copycats; it does not guarantee any token is legitimate. See [Risk Disclosure](/legal-and-safety/risk-disclosure.md).
{% endhint %}

## Continue exploring

* [✅ Identity Checker](/identity-protection/identity-checker.md)
* [🎓 Post-Launch Protection](/identity-protection/post-launch-protection.md)
* [🛡️ What Is AntiVamp?](/identity-protection/what-is-antivamp.md)
* [📡 AntiVamp API Reference](https://antivamp.io/api)


---

# 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.novamp.io/identity-protection/protected-badge.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.