> For the complete documentation index, see [llms.txt](https://docs.premia.blue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premia.blue/the-premia-protocol/concepts/orderbook-and-request-for-quote-rfq.md).

# Orderbook & Request-for-Quote (RFQ)

## <mark style="color:blue;">Arbitrum One vs. Arbitrum Nova</mark>

The Orderbook architecture is unique in that *two* separate chains are utilized. The primary chain is [Arbitrum One](https://arbitrum.io/). Just like the v3 protocol, it's the primary chain where all orders are filled, cancelled, and positions settled/exercised.   This functionality can be accessed using the `IPool` interface, which resides on Arbitrum One, or via the Premia Blue app. Users of the Orderbook must have a valid address on Arbitrum One. All collateral and approvals to transfer collateral must be on Arbitrum One.&#x20;

{% hint style="info" %}
Why Arbitrum Nova? To be a true decentralized tokens options exchange, Premia believes the order book should also be decentralized so that all parties can ensure their orders are not being front ran or censored. A centralized off-chain order book may be subject to unwanted behaviors; thus, Premia decided to use Arbitrum Nova due to its low cost and fast transaction speeds to reflect the order book on-chain.
{% endhint %}

Providing *quotes* for the order book are done through [Arbitrum Nova](https://nova.arbitrum.io/).  Quotes are nothing more than emitted events of order details that are signed by the maker of a transaction that will ultimately process on Arbitrum One.   There are two primary ways to emit quotes to the order book:

1. Directly through the `IOrderbookStream` interface using `add`.  This contract resides on Arbitrum Nova and requires a maker to have an account with an ETH balance to pay for gas fees. &#x20;
2. Using the [Premia Orderbook API](https://docs.premia.blue/developer-center/apis/orderbook-api.md),  Premia will publish the quote on Arbitrum Nova on the maker's behalf.   This is a rate-limited / tiered feature.

{% hint style="info" %}
These orders do **not** earn maker rebates or liquidity mining rewards, ensuring concentrated liquidity and vaults stay competitive long-term.
{% endhint %}

The order book can be accessed directly via the Premia Blue app, [API](https://docs.premia.blue/developer-center/apis/orderbook-api.md), or the [SDK](broken://pages/3n1ds7vUC0e0NZlG3fOk). &#x20;


---

# 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.premia.blue/the-premia-protocol/concepts/orderbook-and-request-for-quote-rfq.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.
