Referral program
> V3 publication draft; not yet published. Economic terms follow the unfrozen specification v2 draft. {{待冻结}} means pending reconciliation with the final frozen specification. This page does not apply to V2 or existing tokens. Available actions depend on the verified release manifest.
Referral rewards come from a reserved share of protocol fees. They do not mint extra tokens or create a multilevel recruitment payout. The project records a referral code at creation; subsequent accruals evaluate its onchain tier.
| Onchain state | Share of referral reserve | Theoretical share of protocol fee |
|---|---|---|
| No code, or code payout equals this project’s creator (self-referral) | 0% {{待冻结}} | 0% {{待冻结}} |
| Active valid code with no bound payout, or payout without a creation record in this release | 40% {{待冻结}} | 4% {{待冻结}} |
| Payout has created a project but has no graduation record | 70% {{待冻结}} | 7% {{待冻结}} |
| Payout has a graduation record | 100% {{待冻结}} | 10% {{待冻结}} |
The reserve itself is 10% of protocol fees {{待冻结}}. The 40 / 70 / 100 tiers {{待冻结}} use the reserve as their denominator, not trade gross. Unearned reserves go to community. Without a payout, accrual still requires valid binding and claim conditions before payment. An inactive nonempty code can reject a trade; it is not always equivalent to no referral.
Authorization checks bind the release, code, operation, nonce, generation and validity period. Service authentication does not replace onchain activation or payout binding. Social verification is not promised as continuously available. Factory’s restricted creation path performs payout binding; third parties cannot arbitrarily change another person’s recipient.
Vault reads the tier at each accrual. Later qualification does not retroactively redistribute earlier ledger entries. Claims pay existing entitlements to the bound beneficiary; knowing a code does not authorize withdrawal. Referral status endorses no project and guarantees no volume or revenue.