> 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/approvals.md).

# Approvals

An approval lets a specific contract spend a wallet's ERC-20 asset. Use the spender for the operation you are about to submit. Approval does not itself pay the creation fee or execute a trade.

### Choose the spender

| Operation                          | Asset approved                                  | Spender                            |
| ---------------------------------- | ----------------------------------------------- | ---------------------------------- |
| Direct Pro creation                | Creation-fee asset and optional first-buy Quote | V2 Factory                         |
| Creation with revenue distribution | Creation-fee asset and optional first-buy Quote | Revenue Forwarder                  |
| Curve buy                          | The launch's Quote asset                        | That token's Curve                 |
| Curve sell                         | The launch token                                | That token's Curve                 |
| Emergency redemption               | The launch token                                | Its activated EmergencyDistributor |

FeeEscrow and revenue claims pay funds already held by the relevant contracts and require no ERC-20 approval. Network gas remains separate.

### Approve, confirm, then continue

1. Read the operation's required asset amounts and spender. Include the configured creation fee and any first-buy Quote. A revenue-distribution preview returns its funding requirements.
2. Check the connected wallet's allowance for each asset and spender.
3. If needed, submit an ERC-20 approval for the required amount.
4. Wait for a successful approval receipt, refresh the operation preview and prepare the creation, trade or redemption transaction.

Approval sets the **total allowance**, rather than adding the supplied amount to the old allowance. If a token requires resetting an existing allowance, confirm a zero approval before setting the new amount.

### Example

Suppose creation costs 2 units of an asset and the first buy supplies another 10 units of that same asset. Required funding is 12 units, approved to the selected creation spender. If the existing allowance is 5, set the allowance to **12**, not 7.

If creation uses a different fee asset from the first-buy Quote, approve the two assets separately. Display amounts with each asset's actual decimals while retaining raw `bigint` amounts for contract calls.

For a Curve buy, approve the full input you submit. A closing buy can spend less and return unused input, but approval checks must still cover the submitted amount. See [Bonding Curve Trading](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/bonding-curve-trading).

Resolve the Curve from the selected token's Factory record. For redemption, resolve the activated EmergencyDistributor for that token. A Revenue Splitter or Holder strategy is a different contract and is not the emergency-redemption spender. See [Emergency Exit](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/emergency-exit).

Each approval and business transaction has its own receipt and gas cost. A transaction hash or a successful simulation alone does not confirm allowance or payment.


---

# 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/approvals.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.
