> For the complete documentation index, see [llms.txt](https://takes.gitbook.io/takes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://takes.gitbook.io/takes-docs/referrals.md). # Referrals and rebates Open **Referrals** in the app, connect your wallet and sign in to create a referral link, see the people you referred and request reward payouts. Rewards are recorded off-chain in USDC. Activity on supported source chains can qualify; payouts use HyperEVM. ## Create and share your link Under **Your referral link**, choose a permanent code and select **Create link**. Codes contain 3–32 letters, numbers, underscores or hyphens, are normalized to lowercase and must be unique. You can create one code per wallet; it cannot be changed. Use **Copy referral link** to share the resulting `/r/yourcode` URL. A referral attaches when a new wallet completes its first successful signed login; it is then **pending**. It **qualifies** and counts as your referral once that wallet completes its first settled deposit or withdrawal on any supported chain. Requests that are still pending or were cancelled do not qualify. Qualification waits for the same chain-finality checks as rewards, so it can take several minutes to appear after a trade settles. Connecting a wallet or visiting a link alone does not register a referral. Existing users can refer others, but cannot acquire a referrer later. Each wallet has one permanent referrer; self-referrals are excluded. The browser keeps the first valid referral link for 30 days. Later links do not replace it during that period. Attribution depends on that browser retaining the link until sign-in; if browser storage is unavailable, it is retained only in the current tab. Invalid codes do not block registration. If checking a link fails, retry or choose **Continue without this referral link**. ## Eligible fees and reward availability The referral share is 10% of the referred user's eligible settled percentage fees: the whole 0.1% fee, before creator and frontend shares. The platform pays it from its share. A separate fee rebate goes to the referred user at the configured rebate rate. Both referral earnings and rebates accrue only when Takes has explicitly configured that rate; there is no default rebate percentage. Referral registration, qualification and volume tracking remain available when reward accrual is disabled. Do not assume that a qualified referral or displayed volume has earned a reward. Eligible fees come from supported settled buy and sell requests accepted after referral attribution. Wallet gas, bridge costs and settlement charges do not count. Earnings depend on actual platform fees, not deposit size or the pool's leveraged trading volume. Cancelled or unsettled requests earn no rewards. Settlement and chain-finality checks can delay credits, so displayed referral volume can update before earnings. For example, 1 USDC in eligible percentage fees earns the referrer 0.10 USDC. The referred user's rebate is 1 USDC multiplied by the configured rebate rate. Historical activity does not create retroactive referral entitlement. ## Read your dashboard **Your referral link** shows your referral count and who referred you, when applicable. The count includes only qualified referrals; wallets that signed in through your link but have not traded yet are shown separately as pending referrals. **People you referred** lists your directly referred qualified wallets, signup dates and completed gross buy and sell volume since referral signup, across supported chains, with a combined total. Pending referrals appear separately with their signup dates until their first settled trade. Volume is before fees and measures user deposits and withdrawals, rather than underlying perpetual trades. This list can remain available while reward accrual is disabled. **Referral earnings** and **Fee rebates** each show: * **Lifetime earned:** all credited earnings, including amounts reserved or paid out. * **Available to claim:** earnings remaining after pending and completed payouts. * **Pending payout:** earnings reserved for a payout request under review. * **Claimed:** completed payouts. The page refreshes every 30 seconds. Sign in with the wallet whose referrals and rewards you want to view. ## Request a payout Each category has its own 10 USDC minimum. Referral earnings and rebates cannot be combined to meet it. Only one payout request per wallet and category can be pending at a time. 1. Choose **Request earnings payout** or **Request rebate payout** when that category is eligible. 2. Review the exact amount, wallet and HyperEVM chain in the confirmation. 3. Choose **Confirm payout request**. This reserves the category's entire available balance for review; it does not send an immediate transfer or submit a contract claim. Payouts are reviewed and sent manually to the signed-in wallet on the displayed HyperEVM chain: 999 on mainnet or 998 on testnet. Earnings from other source chains are still paid there. No automatic payout deadline is specified. New credits remain separately available while a request is pending, but another request for that category must wait. **Payout history** shows the category, amount, request date and status: * **pending:** reserved and awaiting review or payout. * **rejected:** unpaid; the reservation is released back to available balance. * **claimed:** recorded as paid, with payout date and transaction evidence when available. Use **Copy payout transaction** or **View transaction** to inspect a completed payout. Lifetime earned does not reset after payment. Referral payout requests are separate from the [contract claims for pool shares and sale proceeds](/takes-docs/holders/claim-tokens-or-usdc.md#claim-tokens-or-usdc), which follow different rules. --- # 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://takes.gitbook.io/takes-docs/referrals.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.