> 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/staking.md). # staking Earned rewards and staked rewards are separate balances. Staking places eligible rewards into the protocol's distribution accounting; it does not turn them into transferable coins or promise a market value. ## Stake Choose an amount from your earned balance and sign the appropriate Sui transaction. Accrued USDC rewards must be settled against your old stake before your new stake is added. You cannot stake the same earned amount twice. ## Unstake Unstaking reduces your stake and returns that amount to the internal earned balance. The current implementation has no separate cooldown mechanism. Your previous distribution accrual is settled before the stake reduction. Unstaking does not withdraw LP cash or pay your queued trading profits. ## Claim USDC A fee claim pays the user's accrued, backed USDC from the staking reserve and consumes that entitlement. A successful claim cannot be replayed to withdraw the same funds again. Network gas still applies. Staking claims, referral claims and FIFO trader payouts are different claims on different accounting buckets. A UI must show them separately and verify their on-chain receipt. ## Transferability The current code is a nontransferable earned/staked ledger, not a standard REKT Coin. Stake and unstake do not permit wallet-to-wallet transfers. No marketplace, redemption price, listing or guaranteed yield is implied by the token symbol. The GetRekt curve is not yet implemented in that ledger, and there is no verified public deployment. [Staking dividends](broken://pages/7d535b4c73b194b1a3ccd154af1cdc417bbeebb6) explains income sources; [Governance](broken://pages/352822369258b2da16f7a295a15dc1081f8c0021) explains who could change code through an upgrade. --- # 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/staking.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.