> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluton.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Invite and referrals

> Share an invite link or short code, see what it earns you, raise your share with the Discord and voucher-code bonuses, and claim your credits.

Fluton Pool pays the wallet that invited a depositor a share of the fee that deposit will pay. The **Invite** page of the wallet gives the connected wallet its invite link and shows what the link has earned; the bonuses that raise your share live under **Settings** → **Boost your share**. Everything here is per wallet: rewards are credited to, and claimed by, the connected address.

## Your invite link

The link is `/?prt=` followed by your short code, or by your wallet address when you have no code. Copy it with **Copy invite link**, tear the ticket stub, or hand it to the system share sheet with **Share**. The stub shows what the pool currently pays you, as a percentage of the fee.

Opening that link as another account stores the invite in that browser and shows a **Referred by** row on the Shield form, naming the invite and what it does: *Your friend earns … of the platform fee on this amount. The deposit names them on-chain.* The invite stays until the user removes it, and every later shield names it again. A link that names nobody says so (*No one holds this invite code, so this deposit credits no one.*), and your own link earns you nothing (*This is your own invite link: your deposits don't earn you a reward.*).

The pool itself knows nothing of links or codes. A deposit names a **referrer** address in its `ExtData`, and the pool credits that address: it keeps no record of who referred whom.

## Pick a short code

Codes are kept by Fluton's backend API, so a deployment without one simply puts your address in the link: *This deployment runs no referral service, so your link names your wallet address. Short codes need one.*

A code is 3–32 characters of `a-z`, `0-9`, `-` and `_`, starting with a letter or digit, lower-cased, and never something beginning with `0x`, so a link's parameter is never ambiguous between a code and an address. The form says *Use 3–32 letters, digits, - or \_, starting with a letter or digit.*

Claiming one costs no gas: your wallet signs a message naming the code, your address, the chain, the pool and the time it was issued, and the API stores that signature with the record. Clients verify it, and that the record is the one they asked about, before they use the address, so the API can withhold a code but can never point it at an address whose wallet did not sign for it.

The registry's rules:

| Rule | What happens |
| - | - |
| One code per address, one address per code | A new code frees the old one, and links carrying it stop crediting you |
| A code another address holds | Refused: *referral code is taken* |
| An older claim for your address | Refused: *stale claim: this address has a newer one*, so a replayed signature cannot roll a change back |
| A claim signed too long ago | Refused: sign it again |

## What you earn

A referrer is credited a share of the fee the deposit's amount will pay when it is later unshielded. Deployments start at **25%** of that fee, and the pool's owner can raise or lower the base share. The depositor pays nothing extra: the reward comes out of the pool's own fee, not out of the deposit. [Fees and referrals](https://docs.fluton.io/concepts/fees.md) explains the fee itself.

The credit is worked out when the deposit lands, at the rates in force then, and never changes afterwards. It is never more than the whole fee that a withdrawal of that amount pays. A referrer can only be named by a deposit, never by an unshield, so unshields stay as unlinkable as before; a cancelled pending deposit earns nothing.

## Bonuses

Two verified facts raise a referrer's share above the base. Both are checked off-chain by the backend API, which signs an EIP-712 attestation that the referrer submits to the pool; the pool caps a bonus at 5000 basis points of the fee and accepts an attestation only from the signer its owner named.

> [accordion] A bonus role on Fluton's Discord
>
> These roles on Fluton's Discord server raise your share. If you hold several, only the highest counts.
>
> | Role | Bonus |
> | - | - |
> | Moderator | +**2500** basis points |
> | Regional moderator | +**2500** basis points |
> | Encrypted | +**2000** basis points |
> | Fluton creator | +**500** basis points |
> | Fluton apex | +**500** basis points |
>
> A verification is valid **30 days** and renewed by verifying again. Verification is the Discord application's own OAuth2 consent, in two legs so that a consent link can never bind someone else's account to another wallet: the callback only checks which roles you hold and hands your browser a single-use ticket, and a wallet **signature** over that ticket attaches the account. A later check that finds only a lower role lowers your bonus straight away; one that finds a higher role needs that signature first. One Discord account links to one wallet and one wallet to one account. In the wallet this is **Connect Discord**, then *Verified · sign to attach*.

> [accordion] A voucher code
>
> Worth +**500** basis points of the fee, and permanent. Fluton hands out the codes; each is redeemed once, and one wallet can redeem one code. Your wallet signs the redemption, which moves no funds.

Verifying a bonus does not yet change what the pool pays. The panel shows the base share, each bonus and whether it is *Active on-chain* or *Not yet on-chain*, and the referrer activates the attestation with **Activate on-chain**; the wallet verifies the attestation against the pool's own signer first, so a misbehaving API cannot get anything signed into the pool. The pool takes only an attestation issued strictly later than the one it stores, so a replay can never roll a bonus back, while a newer one that grants less (a lapsed role, a downgrade) still lands. A bonus applies to deposits that land after it is set; credits already given never change.

## Claim your credits

**Your rewards** on the Invite page reads your credits straight from the pool, per token, never from the API. Every row with a credit carries two buttons, **Claim** for the TOKEN and **Claim encrypted** for the eTOKEN; either calls `claimReferral(asset, amount, to, format)`, which pays out exactly like an unshield, through a payout obligation, so the **Payout status** panel tracks the claim until the pool has confirmed it. Claims are public, like the deposits that earned them.

A claim can only take what unshield fees have actually paid into the pool in that token. Until they have, the pool reverts with `InsufficientFees`, which the wallet shows as *Not enough platform fees have been paid in this token yet. Try again later.* When only part of a credit is covered, the row says how much is claimable now and that the rest follows as more fees in that token are paid.

## Known limits

* Anyone can refer themselves from a second wallet, which amounts to a rebate of **25%** of the fee, or up to **55%** with the largest bonus the API grants (a 2500-point role and a code).
* Credits are public per referrer address, and so are the link between a deposit and its referrer, and a referrer's bonus.
* A credit that is never claimed stays reserved inside the pool's fees, where the owner cannot collect it.
* A leaked API signing key can raise anyone's share by at most 50 percentage points of the fee, until the owner changes the signer and revokes the grants; the permanent part of a bonus stays until it is revoked.

The rest of the wallet is described in [Using the wallet](https://docs.fluton.io/wallet/using-the-wallet.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.