> 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.md).

# Start Here

Start using the live Sidepit ProofNet exchange.

Sidepit ProofNet is live on mainnet Bitcoin. Access remains beta-code gated, and every amount you fund or trade is real.

The complete customer journey is:

1. Request beta access at [app.sidepit.com](https://app.sidepit.com).
2. Connect a UniSat **Native SegWit** address beginning `bc1q`. This public address becomes your Sidepit ID.
3. Fund that Sidepit ID first, then use **LOCK** to move its confirmed balance into the exchange.
4. Trade in the web app, or authorize a separate trading-only agent.
5. The account owner can request an unlock back to the same Sidepit ID.

{% hint style="danger" %}
Never send Bitcoin from an external wallet or exchange directly to Sidepit's deposit/lock address. First send it to your own connected Sidepit ID, then use LOCK. This is how the exchange identifies the account to credit.
{% endhint %}

Before funding, read the [risk disclosure](/legal/risk-disclosure-statement.md), the current [contract specifications](/use-sidepit/beta/trading/contract-specifications.md), and the [margin and execution fee guide](/use-sidepit/beta/trading/margin.md).

If you are using an AI agent, keep the human account key and seed words out of the agent, chat, terminal, logs, and support messages. Follow [Authorize a Trading Agent](/use-sidepit/beta/onboarding/authorize-agent.md).


---

# 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.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.