> 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/beta1-overview.md). # ProofNet Overview What is live in the current Sidepit ProofNet release. ProofNet is Sidepit's current live, real-Bitcoin proving stage. It combines the exchange engine, browser trading app, public NNG/protobuf protocol, Python SDK, agent skills, and a complete owner-controlled unlock path. ## Product stages * **Beta — December 2024:** Sidepit opened its original private beta. * **ProofNet — August 10, 2026:** The current live stage began on real mainnet Bitcoin. * **Launch — targeted for Q4 2026:** The planned production launch follows ProofNet. ## Live product surface * Dated Bitcoin-margined USDBTC forwards * DLOB — one-second deterministic auctions * Limit, cancel, cancel/replace, and native immediate-or-cancel market orders * Daily mark-to-market settlement in satoshis * UniSat account signing * Protocol-enforced trading-agent authorization and revocation * Owner-signed explicit or MAX unlock requests * Public market, order, rejection, position, margin, and account-operation data ## The account has one continuous identity Your Native SegWit `bc1q` Bitcoin address is the Sidepit ID used from funding through trading and unlock. The exchange learns that public identity from the LOCK transaction input. Bitcoin unlocked from the account returns only to that same address; there is no destination field. An agent gets a different identity. The owner signs its authorization in UniSat, and the agent then signs orders with its own key while naming the owner's account and its `agent_id`. The protocol rejects attempts by an agent to unlock funds, authorize another agent, or revoke authority. ## Observe, do not infer Submission means a request was received or queued; it does not mean an order filled or an account operation completed. Sidepit publishes named receipts and outcomes so clients can follow the same public operation or order ID to its result. For unlocks, the normal path is: `PENDING → RESERVED → PROCESSING → COMPLETED` The web app and public account view retain those states across restart. Sidepit does not promise how long the lifecycle will take. --- # 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/beta1-overview.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.