> For the complete documentation index, see [llms.txt](https://docs.peach.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/tax-and-pool-protection.md).

# Tax and Pool Protection

Creators choose separate buy/sell tax rates and a pool protection period when creating a token. The platform maintains protection rules; each token fixes its own selected duration and resulting address list at creation.

### Creator Tax

`creatorBuyTaxBps` applies to buys and `creatorSellTaxBps` to sells, on both the Curve and the official V4 pool. Values use basis points: `100 = 1%`. Read current configuration limits before creating or quoting.

With a 1% base fee, 1% buy tax, 3% sell tax and no Snipe Tax:

| Operation                      | Fees                                   | Result                   |
| ------------------------------ | -------------------------------------- | ------------------------ |
| Curve buy with 100 Quote       | 1 Quote base fee + 1 Quote Creator Tax | 98 Quote enters pricing  |
| Curve sell for gross 100 Quote | 1 Quote base fee + 3 Quote Creator Tax | Seller receives 96 Quote |

Each fee rounds down separately in raw units. A closing buy may partially fill and refund unused input. V4 Exact Input deducts fees from output; Exact Output adds fees to input. Use the buy rate when the launch token is output and the sell rate when it is input. See [Hook fees](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/uniswap-v4-hooks/hook-behavior-and-fees) and [Fees and Claims](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/fees-and-claims).

### Choose protection days

| `protectionDays` | Effect                                                             |
| ---------------- | ------------------------------------------------------------------ |
| `0`              | Protection off; default choice                                     |
| Integer `1–365`  | Selected number of days after successful official V4 pool creation |

Pass **days**, not seconds. `protectionDays=7` selects seven days. Token `protectionDuration()` returns seconds, so that token reports `604800`.

**The current testnet rules are empty.** A nonzero period is accepted and stored, but the restricted list is empty and transfers are not blocked. Show this in the creation review. Adding rules later does not change tokens that have already been created.

Creators cannot edit the platform rules or change a token's duration after creation. When a list is nonempty, transfers **into** its listed addresses are blocked during protection; transfers out are allowed. The list can contain derived pools and configured fixed addresses, so describe the actual list rather than promising protection against every alternative pool.

### Lifecycle and reads

| State                                           | Transfer restriction                             |
| ----------------------------------------------- | ------------------------------------------------ |
| Zero days or empty list                         | No restricted destination                        |
| Nonempty list, before official V4 pool creation | Transfers into listed addresses are blocked      |
| Official V4 pool created                        | Countdown runs for the token's selected duration |
| Countdown ends                                  | Transfers into listed addresses are allowed      |
| Emergency exit successfully activated           | Protection is permanently released               |

A Curve buy, sweep or failed pool-creation attempt does not start the countdown.

* `restrictedPools()` returns the fixed list; `isRestrictedPool(address)` checks membership.
* `isTransferRestricted(address)` answers whether a transfer into that address is blocked now.
* `protectionDuration()` returns the chosen duration in seconds.
* `protectionEndsAt()` is `0` initially for zero duration, the maximum `uint256` while waiting for V4 creation, or an end timestamp after finalization. Read actual restrictions even when a duration is nonzero, because the list can be empty.

### Preview, confirm and create

Use the SDK's V7 request and matching [contract addresses](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/contract-address). The request carries `protectionDays` through direct creation, revenue creation, previews and address prediction.

1. Read the current ConfigRegistry rules hash and launch terms; build the request with the selected days and accepted limits.
2. Use `previewLaunchpadV2Launch` for direct creation or `previewLaunchpadProRevenueLaunch` for [Revenue Distribution](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/revenue-distribution). A zero hash is allowed only for discovery previews; review the returned nonzero rules hash and economics.
3. Show the final request, fees, predicted addresses and restrictions to the user. Approve funding to the correct spender, then prepare and submit the reviewed request.
4. Confirm the receipt and read the launch state.

Even zero-day creation requires `expectedPoolProtectionHash` from the new ConfigRegistry. The hash commits to the rules, while duration is committed separately in the request. Changing days changes request hashes and address predictions. If `PoolProtectionHashMismatch` occurs, refresh the preview and get renewed confirmation.

### Configuration and indexing

ConfigRegistry stores the Resolver and rules data. It has no platform-wide protection duration. Management calls are `setPoolProtection(rules)` and `setPoolProtectionResolver(resolver, data)`; `snapshot` also omits the former duration field.

Decode **`PoolProtectionConfigured(bytes32 configurationHash)`** with the current ABI and refresh cached rules. Per-token `PoolProtectionInitialized` records actual seconds and the fixed list; `PoolProtectionFinalized` records lifecycle completion. Global changes apply only to future tokens.

Integrations calculating hashes or CREATE2 addresses locally must use the V7 request and complete preview context. The request domain is `ARC_MAINNET_V2_CREATION_REQUEST_V7` and Deployer interface is `ARC_LAUNCH_DEPLOYER_V2_7`. Prefer SDK preview and prediction helpers over manual encoding.


---

# 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.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/tax-and-pool-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.
