> 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/token.md). # token $REKT is GetRekt's loss-earned reward. The launch design starts with no premint and distributes rewards through eligible trading losses rather than a VC or team token allocation. A failed trade does not recover its value simply because it earns rewards. ## Earn by losing At the start, each 1 USDC of realized eligible loss earns 10,000 $REKT. Every additional 10,000,000 USDC of platform-wide cumulative eligible losses halves the rate. Cash losses and debt-collateral losses both qualify; referral rewards only arise from cash losses. The loss basis is the trader's gross realized loss, before protocol fees and referrals. The same basis advances the global halving counter. A 100 USDC loss in the first epoch therefore earns 1,000,000 $REKT whether the cash allocation has a referrer or no referrer. [Emissions](broken://pages/af415c261799018d5354ee742284d48baa28670b). ## Supply The new infinite-precision curve approaches 200,000,000,000 $REKT in total. This is a mathematical upper limit of the specified loss-emission curve, not a currently deployed hard cap and not a 21-million-token supply. No separate team mint, minimum perpetual emissions rate, resettable epoch or premine is specified. Integer rounding and any future upgrade must be disclosed and validated. [Mint curve](broken://pages/924b816ae9e73e9b9573ea8c2a455bcd1e3b9187). ## Staking Staked rewards participate in backed USDC fee distributions and eligible LP overflow. These are variable protocol receipts, not a fixed yield. Rewards earned but not staked do not automatically share distributions. [Staking and claims](broken://pages/d34724d318b8ff7fb45b099092814929dbd9fc59). ## Transferability and control The current Move implementation is an internal earned/staked ledger with six decimal places. It has no wallet-to-wallet reward transfer and does not issue a standard transferable REKT Coin. A symbol change does not create token liquidity, exchange listings or a market price. Current reward issuance is restricted to protocol loss settlement; there is no general administrator mint function. However, package upgrade authority can alter future rules, including issuance or transferability if new code introduces them. The governance and upgrade controls must be evaluated alongside the mint function. [Governance](broken://pages/352822369258b2da16f7a295a15dc1081f8c0021). The current code still uses the old reward curve. The new $REKT schedule and symbol in this book are launch specifications, not evidence of deployed issuance. [Implementation status](broken://pages/c7eabe8af8c3f2ae7c1c1dce69dad717e5d1ac7a). --- # 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/token.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.