> For the complete documentation index, see [llms.txt](https://docs.volven.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.volven.io/strategies/twap-arbtirage.md). # TWAP Arbtirage TARB <\> ## What is the Volven TARB? TARB, short for TWAP Arbitrage, is an algorithmic trading strategy with dynamic take profit and stop loss. The strategy opens and closes the positions with the Volven TWAP strategy. The strategy holds the discretion to partially enter and exit the market. Meaning that during the course of its duration you could be entering and taking profits multiple times at different levels. The TARB makes a profit by generating a net positive spread between its two child TWAPs. TARB's Take Profit and Stop Loss is based on the percentage of returns that you are making. They are not set to fixed levels since the strategy is dynamic and continously enters and exits the market. ### How to place a Volven TARB? <\> ### Optional parameters
ParameterPurpose
Price LimitUpper barrier for buying, or lower barrier for selling. Prevents your strategy from buying at an unfavorable price.
Stop LossIf your return on investment is below your stop loss, the strategy will exit the remaining position and stop trading.
Trigger PriceDetermines the price where the strategy will start. Meaning the strategy will be waiting until the market crosses the trigger price.
--- # 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.volven.io/strategies/twap-arbtirage.md?ask=&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.