# Excluded addresses

### Excluded from limits

If your token has any of the following features:

* **Max amount per wallet**
* **Max transaction limits**
* **Anti-bot cooldown**

Then by default, some addresses are excluded from these limits altogether:

#### Always Excluded:

* **Supply recipient**: The address that receives initial tokens
* **Token smart contract**: Your token's contract address
* **0x0 (burn) address**: The address used for burning tokens

#### Conditionally Excluded:

* **RouterV2 and PairV2 smart contracts**: If you enabled default exchange
* **Wallet tax recipient addresses**: If you have wallet taxes configured

#### What This Means:

Addresses excluded from limits can:

* Hold unlimited tokens
* Make unlimited token transactions
* Will not be temporarily frozen by anti-bot cooldown after buying or selling

### Excluded from trading restriction

If your token has the following feature:

* **EnableTrading function**

Then by default, some addresses are excluded from this restriction:

* **Supply recipient**: The address that receives initial tokens
* **Token smart contract**: Your token's contract address

#### What This Means:

Addresses excluded from trading restrictions can interact with the DEX before trading is enabled for everyone by the owner. These exclusions will have no effect once the owner calls the enableTrading() function.

### Excluded from fees

If your token has any of the following features:

* **Wallet taxes**
* **Auto-burn tax**
* **Liquidity tax**
* **Dividend tax**

Then by default, some addresses are excluded from paying any fees:

#### Always Excluded:

* **Supply recipient**: The address that receives initial tokens
* **Token smart contract**: Your token's contract address

#### Conditionally Excluded:

* **Wallet tax recipient addresses**: If you have wallet taxes configured

#### What This Means:

Addresses excluded from fees can buy, sell, and transfer without being charged any taxes.

{% hint style="info" %}
**Note:** The token smart contract requires both the sender and recipient of each transaction to be included in fee payments in order to charge the fee.
{% endhint %}

### Excluded from dividends

If your token has the following feature:

* **Dividend tax**

Then by default, some addresses are excluded from receiving any dividends for holding tokens:

* **Supply recipient**: The address that receives initial tokens
* **Token smart contract**: Your token's contract address
* **RouterV2 and PairV2 smart contracts**: DEX contract addresses
* **Dividend tracker contract**: The contract that manages dividend distribution

#### What This Means:

Even if an excluded address has enough tokens to meet the criteria (such as the minimum number of tokens required to receive dividends), it will not receive any dividends because the exclusion has higher priority.

### AMM contracts

If your token has the following feature:

* **Default exchange**

Then by default, some addresses are added as AMM contracts (also known as DEX contracts) that your token will recognize for transaction type checking:

* **RouterV2 contract**: The exchange's router contract
* **PairV2 contract**: Your token's liquidity pair contract

#### How AMM Recognition Works:

**Automatic Exclusions**: By adding a contract to this list, your token will automatically exclude it from limits and dividends (if applicable).

**Transaction Type Detection**: Your token uses the AMM list to determine the type of transaction for features that depend on transaction types, such as:

* **Buy**: Trading native coins/tokens for your token
* **Sell**: Trading your token for native coins/other tokens
* **Transfer**: All other token movements

**Internal DEX Transfers**: By marking multiple contracts as AMM contracts of the same DEX, your token will treat transfers between them not as regular transfers, but as internal DEX transfers. This ensures that features like EnableTrading function and Anti-bot cooldown are handled and enforced correctly.

{% hint style="warning" %}
**Important:** Your main liquidity pool (PairV2) and RouterV2 cannot be removed from this list.
{% endhint %}

### Why These Exclusions Exist

These automatic exclusions are designed to:

1. **Prevent system conflicts**: Ensure DEX contracts can function properly
2. **Maintain liquidity**: Allow essential addresses to operate without restrictions
3. **Enable proper fee collection**: Ensure tax systems work as intended
4. **Support project operations**: Allow project addresses to manage tokens effectively

Understanding these exclusions helps you plan your token's behavior and ensures your features work as expected.


---

# Agent Instructions: 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:

```
GET https://docs.20lab.app/features/excluded-addresses.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.