# A Typical Trade in Vessel

<figure><img src="/files/QZ8VKxrEUxLfiQWIJU1s" alt=""><figcaption></figcaption></figure>

**Let’s start with: How is an order executed in Vessel’s VAELOB?**\
\
Alice places a limit order to buy 1 ETH at a price of $3810. Vessel fulfills this order using 0.7 ETH at $3800 and 0.3 ETH at $3801. While this appears similar to traditional order matching, distinguishing between user-originated orders and AMM pool orders reveals Vessel’s unique execution method.\
\
First, Alice’s order is matched with sell orders at $3800, consisting of 0.4 ETH from the AMM and 0.3 ETH from other users. Once the 0.4 ETH from the AMM order is fulfilled, the AMM automatically places a new buy order of the same size at $3799. In contrast, the 0.3 ETH from user orders is removed from the order book upon fulfillment.\
\
Next, Alice’s order is matched with sell orders at $3801. The AMM contributes 0.5 ETH at this price, but Alice’s order only consumes 0.3 ETH of it. Afterward, the AMM places a buy order of 0.3 ETH at $3800 once its sell order is fulfilled.\
\
In summary, Alice’s order is filled by a combination of orders from other users and the AMM pool. When an AMM order is fulfilled, it automatically places another order of the same size in the opposite direction. Although not detailed in the above flow, it is important to note that the trading fees from AMM-generated orders are collected into the AMM pool and shared proportionally among the LPs.


---

# 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://vesselfinance.gitbook.io/vessel/vaelob/a-typical-trade-in-vessel.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.