> For the complete documentation index, see [llms.txt](https://takes.gitbook.io/takes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://takes.gitbook.io/takes-docs/holders/redeem-tokens.md).

# Sell pool shares

Selling reduces or closes your exposure by exchanging pool shares for a share of the trading account’s USDC. The protocol calls this a **redemption request**; the app calls it **Sell**. It settles asynchronously, so submitting a sell request does not immediately deliver USDC or end your market exposure.

Connect the wallet holding the shares on the pool’s network. Keep enough gas for the request and a manual claim if needed.

1. Choose **Sell** in a Portfolio pool row or the pool page’s **Your position** card, or select pool shares and USDC in [Trade](/takes-docs/trade.md#buy-or-sell-pool-shares).
2. In **Sell pool shares**, enter **Shares to sell**, or choose **Sell all** to fill your available wallet share balance. Sell all only fills the amount; it does not submit a request. Shares locked in another request or awaiting delivery are not included.
3. Check **Estimated USDC received** and total fees, which appear automatically. Expand fee details if needed.
4. Choose **Sell shares**, then confirm the transaction in your wallet. No separate approval is needed for your own shares. If a refreshed estimate changes, check it and choose Sell shares again.

Your shares lock when the transaction succeeds on-chain. An accepted sell request can return its shares through `cancelRedemption(requestId)` before execution starts; once execution starts, cancellation is unavailable. Settlement time varies with account operations, network confirmations, and transfers. Market moves and execution costs during processing can still change the proceeds; submission does not lock a sale price.

Takes prepares the account, returns USDC, and settles your request. Net proceeds are delivered automatically, with a [manual fallback](/takes-docs/holders/claim-tokens-or-usdc.md#claim-tokens-or-usdc).

If 10 shares have a displayed NAV of 2 USDC, the gross estimate is 20 USDC. Market moves, trading costs, and selling fees can change the final amount. The accepted settlement fee stays fixed; the percentage fee uses actual gross proceeds. Charges are capped at proceeds, so selling all your shares can return zero USDC.

Track the request through **View requests** in Portfolio or **My requests** on the pool page. **Selling** means the accepted request is processing. **Delivering USDC** means settlement is complete but delivery remains outstanding. Request identifiers are available under **Request details**.

Buy and Sell are available for supported pools. New requests require live activation. Previous deployments and historical batch pools are outside this fresh rollout. See [Fees and limits](/takes-docs/reference/fees-and-limits.md#fees-and-limits) and [Request status](/takes-docs/reference/status-reference.md#request-status).


---

# 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://takes.gitbook.io/takes-docs/holders/redeem-tokens.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.