# Seats

## What is a Seat?

A Seat is an account that tracks the ability for a trader to place limit orders on a Phoenix Legacy market. A Seat must be created and its status must be Approved in order to place a limit order on a Phoenix Legacy Market. Each Phoenix Legacy Market requires a separate Seat Account for each trader.

## Seat Status

A Seat, once created, can have three statuses:

* Approved: This means the trader who owns that Seat can place limit orders on the market which the Seat corresponds to.
* Not Approved: This means the trader who owns that Seat cannot place limit orders on the market which the Seat corresponds to.
* Retired: This means the trader who owns the Seat can never place orders on the market which the Seat corresponds to. Retiring a Seat is an action that can only be performed by the Market Authority.

## How to get a Seat

You can claim a Seat on any [Market whose authority is the Phoenix Legacy Seat Manager Program](/phoenix-dex/tRIkEFlLUzWK9uKO3W2V/getting-started/technical-overview/market-addresses.md), such as SOL / USDC, through the Phoenix Legacy Seat Manager program. Claiming seats and placing limit orders are permissionless and can be performed atomically. See[ here for how to claim a seat on a Market whose authority is Phoenix Legacy Seat Manager.](/phoenix-dex/tRIkEFlLUzWK9uKO3W2V/getting-started/technical-overview/seats/phoenix-seat-manager-program.md)

For markets whose authority is not the Phoenix Legacy Seat Manager:

* Create a Seat with the `RequestSeat` [instruction](/phoenix-dex/tRIkEFlLUzWK9uKO3W2V/getting-started/technical-overview/instructions.md).
* Request the Market Authority to change the Seat's status to Approved. Only the Market Authority can create a Seat with an approved status or change the status of an existing Seat.

## FAQ:

### Why do I need a Seat?

Each Phoenix Legacy Market contains information on outstanding limit orders, such as the amount of base and quote tokens locked in active orders, as well as the trader who placed the order. After a limit order is matched, the Phoenix Legacy program can then debit or credit the base or quote tokens to the appropriate trader record. A trader's seat ensures that the trader has a record on the market. A trader can withdraw settled tokens thereafter.

As a result, Phoenix Legacy does not require a crank to function, since the token accounts of the counterparty do not need to be known at the time of matching. This significantly improves user experience and performance.

### I claimed a Seat and successfully placed a limit order. But why are my new limit orders now failing?

If you do not have any open orders on the Market and the Market's trader state is at capacity, your Seat may be evicted from the Market's trader state in favor of active traders with new orders. This can cause new limit orders to fail. If this happens, you can simply claim a new seat following the above instructions and proceed to place limit orders.


---

# 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://ellipsis-labs.gitbook.io/phoenix-dex/tRIkEFlLUzWK9uKO3W2V/getting-started/technical-overview/seats.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.