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

# Token Protection

> **Availability: ARC MAINNET + TESTNET**

Token Protection gives an eligible Souless launch temporary protection over its exact **token name + ticker** pair.

Selecting Token Protection while launching is **a request for protection, not immediate protection**. The market must first meet the qualification requirements below. Until Souless finishes that process and activates protection, the pair is not protected.

## What happens after you request it

A protection request moves through a qualification process:

```
Protection requested
        │
        ▼
1-hour contention window
        │
        ▼
Qualification check
        │
        ▼
On-chain activation
        │
        ▼
Protected for 7 days
        │
        ▼
24-hour dormant period
        │
        ▼
Released
```

If more than one launch requests protection for the same exact pair during the contention period, claims are evaluated in canonical on-chain order. An earlier claim still has to qualify; requesting first does not let a market bypass the requirements.

## Qualification requirements

Under the current Souless policy, a launch must satisfy **all** of the following before protection can activate:

| Requirement                  |                        Current threshold |
| ---------------------------- | ---------------------------------------: |
| Token age                    |                          At least 1 hour |
| Qualifying trading volume    |                        At least 100 USDC |
| Holders                      |           At least 5 non-creator holders |
| Market liquidity             |                        At least 500 USDC |
| Largest-holder concentration | No more than 75% of circulating holdings |
| Creator standing             |            Creator must not be suspended |

The holder count excludes the creator and the market pool. Qualifying volume excludes trades made by the creator wallet. The concentration check excludes the pool from circulating holdings.

These thresholds are protocol policy parameters and can change under a future policy version. Souless should show the applicable requirements for the launch you are making.

## What active protection actually does

Protection applies to the normalized **name and ticker together**. It does not separately reserve every use of the name or every use of the ticker.

For example, if `Example Token / EXM` is actively protected, the protection applies to that exact pair after Souless normalizes casing, spacing, and equivalent text formatting.

Protection also **does not block somebody from launching the duplicate**. Instead, an exact duplicate launched while protection is active pays the protected-duplicate launch fee.

Under the current policy:

* standard launch fee: **0.05 USDC**;
* exact duplicate of an actively protected pair: **50 USDC**;
* **80%** of that protected-duplicate fee goes to the creator holding the active protection;
* **20%** goes to the protocol.

The launch review quote is authoritative for the fee and protection policy attached to a specific transaction.

## When protection is not active

A checked box or submitted request is not proof of protection. A market can remain unprotected because it has not reached the evaluation point, has not met one or more qualification thresholds, or has failed the creator-standing check.

If no claim qualifies, the pair returns to an available state. The token and its market continue to exist normally; failing to qualify for Token Protection does not undo the launch.

## Expiry and release

Once activated, the current protection term lasts **7 days**. At expiry, the active on-chain protection ends and the protected-duplicate fee no longer applies. The namespace then goes through a **24-hour dormant period** before it is released for a new protection cycle.

Protection is therefore temporary. It is designed to reward a launch that establishes an eligible market around a name-and-ticker pair, rather than permanently reserving that namespace.

## The important distinction

> **Requested** means the creator opted into the qualification process. **Protected** means the request qualified and protection was activated on-chain.

When checking a market, rely on its current protection status rather than whether Token Protection was selected at launch.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.souless.fun/launching/token-protection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.