> For the complete documentation index, see [llms.txt](https://docs.architect.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.architect.co/algos-book/percent-of-volume-pov.md).

# Percent of volume (POV)

The Percent of Volume (POV) algo attempts to spread out an order based on targeting a specified proportion of the overall market volume. An execution using the POV algo can reduce implementation costs by minimizing impact using a carefully managed, constant participation rate. 

<figure><img src="/files/zeSs9tddAv6J6rH4tzmG" alt=""><figcaption><p>In this POV example, the algo will target 2% of the ETH perpetual futures volume on Deribit. Between now and 04/01/2024 9:53 AM, the algo will buy as much as 500 ETH worth of perpetual futures, sending order at least 1 ETH size, 1 basis point above the offer in the futures market. The algo estimates a total cost of ~$1.7 million.</p></figcaption></figure>

We can choose the parameters based on the trading goals.&#x20;

<table><thead><tr><th width="213">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Buy/Sell</td><td>Direction of the order</td></tr><tr><td>Market</td><td>The symbol &#x26; price currency of the market, and the exchange</td></tr><tr><td>Min Order Quantity</td><td>The smallest size order the algo will attempt to send</td></tr><tr><td>Max Quantity</td><td>The maximum quantity that will execute, measured in token units or contracts. Given enough time and market volume, this can also be thought of as the total quantity.</td></tr><tr><td>Take Through Fraction</td><td>At what price to send the order, relative to the opposite side market.  For example on a buy order, a take through fraction of 0 would send bids at a price equal to the best offer at the time, and a take through fraction of 0.0005 would send bids 0.05% (5 basis points) above the current offer. Increasing this parameter above 0 reduces the chance of missing out on trades in a fast moving market, but has a higher risk of price slippage. </td></tr><tr><td>Order Lockout</td><td>The minimum amount of time to wait between orders</td></tr><tr><td>Reject Lockout</td><td>If an order is rejected, wait this amount of time before trying again</td></tr><tr><td>Time</td><td>The end time of the algo, in your local timezone</td></tr></tbody></table>

If there's an insufficient volume of trading in the market, the algo is not guaranteed to fill its full size by the end time, and will cancel any remainder size. The algo can also conclude prior to the end time if the max quantity is reached.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.architect.co/algos-book/percent-of-volume-pov.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.