> For the complete documentation index, see [llms.txt](https://docs.sidepit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sidepit.com/use-sidepit/beta/trading.md).

# Trading

Trade Sidepit's dated Bitcoin-margined USDBTC forwards.

Sidepit trades dated USDBTC forwards in **DLOB — one-second deterministic auctions**. Prices are integer satoshis per USD, margin and P\&L are in satoshis, and each contract represents the USD exposure published by the active contract.

Before placing an order:

1. Read the active ticker, exchange state, schedule, contract size, price bands, and margins from the exchange. Never reuse a ticker or amount from an old session.
2. Understand the inverse quote: `USD/BTC = 100,000,000 ÷ sats-per-USD`.
3. Review available margin, working orders, current position, and execution fees.
4. Choose limit or market behavior deliberately.

Sidepit charges an **execution fee** of **125 sats per contract per side per execution**. The engine deducts it on every fill and publishes accumulated values in `realized_fees`.

Start with:

* [Contract Specifications](/use-sidepit/beta/trading/contract-specifications.md) for the current ticker, contract size, margins, schedule, price bands, and expiry;
* [USDBTC](/use-sidepit/beta/trading/usdbtc.md) for exposure direction;
* [Buy, Sell, and Cancel](/use-sidepit/beta/trading/buy-sell-cancel.md) for the web workflow;
* [Order Types](/use-sidepit/beta/trading/beta-orders.md) for limit and market behavior; and
* [Margin and Execution Fee](/use-sidepit/beta/trading/margin.md) before choosing size.

{% hint style="warning" %}
A queued order is not a fill. Resolve it through the order and rejection views before repeating or replacing it.
{% endhint %}


---

# 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.sidepit.com/use-sidepit/beta/trading.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.