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

# introduction

GetRekt is a zero-VC, fair-launched, fully on-chain perpetuals exchange built on Sui, with several unique features:

* 2000× leverage
* Up to 30% referral fee
* Faster decrease in $REKT token minting
* One-click Buy/Sell, no orderbook
* Zero slippage
* No funding costs
* Self-bootstrapping LP
* No spread

{% hint style="info" %}
Launch design, not an announcement of a completed launch. These features describe the intended product. Zero-VC and fair launch are launch commitments; no financing verification or completed token launch is asserted here. “Fully on-chain” refers to custody, positions and settlement: pricing still depends on a Lighter relay and Pyth. See [Implementation status](broken://pages/c7eabe8af8c3f2ae7c1c1dce69dad717e5d1ac7a).
{% endhint %}

## Pick a side. Set your margin. Trade.

Choose Buy or Sell, enter USDC margin, and select leverage up to the permitted limit. GetRekt creates an isolated position on Sui using an accepted Lighter reference price. There is no orderbook to navigate inside GetRekt and no matching order placed for you on Lighter.

2000× is the product ceiling. Price quality and market limits can require lower leverage or prevent execution. One-click describes the interface; wallet approval and Sui gas still apply.

## A pool that builds itself

The LP starts with zero capital. Realized cash losses fund it; realized profits are paid from available LP cash. If that cash is insufficient, the unpaid amount becomes a FIFO claim. Claims can also be used as collateral, with the same risk of losing their value.

Referrals add a new participation path to this bootstrapping model. An eligible cash loss first pays the 2% protocol fee. The remaining amount is split 30% to the referrer and 70% to the LP. [See the full referral rules](broken://pages/4ae98f6aa1e3c0a457110b4f9eefb1d3448a99a6).

## Lose a trade. Earn $REKT.

The initial reward is 10,000 $REKT per 1 USDC of realized eligible loss. Every additional 10,000,000 USDC of cumulative platform losses halves the rate. Cash and debt-collateral losses both qualify; debt losses do not generate referral payments. [Explore emissions](broken://pages/af415c261799018d5354ee742284d48baa28670b).

## Know the costs

GetRekt adds no order-size slippage, artificial execution spread, or time-based funding charge. Your displayed quote can still move before execution. Profits are subject to a deadband, asymmetric adjustment and a 2% profit fee. Network and bridge fees can also apply. “Zero slippage” does not remove these costs. [Read the pricing rules](broken://pages/ff0bee99a927ff20ef1e924a6b4131f14dfb165a).


---

# 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.getrekt.trade/introduction.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.