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

# Emergency Exit

On the current testnet deployment, emergency activation and redemption passed fork tests. The public Testnet waiting period and activation have not been completed.

Emergency Exit lets holders redeem a Pro token whose Curve reserves have been swept but whose official V4 pool has not been created. Activation changes Swept to EmergencyExited, burns the graduation token reserve and funds an EmergencyDistributor with the graduation Quote reserve.

### Activate redemption

Call `Factory.emergencyExit(token)` while the status is still Swept:

<table data-header-hidden><thead><tr><th width="290.46875"></th><th></th></tr></thead><tbody><tr><td>Caller</td><td>Required time since successful <code>sweptAt</code></td></tr><tr><td>Current Factory Owner</td><td>24 hours</td></tr><tr><td>Any other address, including Creator Controller or token holder</td><td>7 days</td></tr></tbody></table>

Failed pool-creation retries do not reset the timer. Once PoolCreated is reached, this redemption path is unavailable.

### Redeem your tokens

Locate the instance through `GraduationCoordinator.emergencyBinding(token)` and verify its launch token, Quote and activated state. Quote is the launch's configured ERC20 payment asset.

1. Read `activated`, `remainingQuote` and the launch token's current `totalSupply()`.
2. Approve the launch token to that EmergencyDistributor.
3. Call `redeem(tokenIn, recipient)` from the address supplying the tokens. The recipient receives Quote and may be another address.
4. Confirm the `Redeemed` event and actual Quote transfer.

Redemption burns the supplied tokens. The payout is:

`floor(tokenIn × remainingQuote / liveSupplyBeforeRedemption)`

The holder redeeming all remaining supply receives all remaining tracked Quote. Already burned tokens affect the live-supply denominator; the initial issuance is not a fixed denominator.

For example, with 900 raw Quote remaining and live supply 90, redeeming 10 pays 100. Supply becomes 80 and Quote becomes 800. If another 20 tokens are subsequently burned, the next redemption of 10 pays `floor(10 × 800 / 60) = 133` raw Quote.

Direct token transfers to the instance are donations, not redemption requests: those tokens are burned without paying the sender. Quote donations do not automatically increase tracked `remainingQuote`. Use `redeem` for a payout.

EmergencyDistributor holds graduation reserves. Revenue Splitters and buyback/vesting strategies hold separate revenue and entitlements; their recovery flows remain separate. See [Buyback and Vesting](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/buyback-and-vesting) for strategy funds and [Graduation](https://docs.peach.ag/documentation/arc/launchpad/launchpad-pro/core-features/graduation) for lifecycle states.


---

# 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/emergency-exit.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.
