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

# About 1v1.trade

## What is 1v1.trade?

1v1.trade is the first competitive perpetual futures trading platform where traders compete real-time matches, with real stakes and trading balances. Two traders stake equal amounts, trade for a set duration, and the highest PnL takes the combined stakes.

**Technical overview**

1v1.trade is built on Hyperliquid's Layer 1 blockchain, utilizing their agent system for trade execution and their fully onchain order books for all trading activity.

Matches operate with strict PnL tracking isolated to trading activity only - deposits and withdrawals during matches do not affect the competitive outcome. Every trade executes with one-block finality inherited from Hyperliquid's HyperBFT consensus.


---

# 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.1v1.trade/about-1v1.trade.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.