All posts

Earn a Monthly Share of Protocol Fees by Introducing Capital to SukukFi

·Shazad Khaninvite-codereferral rewardreferrallpreferrersberachain

Invite code = a referral link that pays you a monthly share of protocol fees when the people you introduce deposit and keep capital deployed.

The SukukFi Invite Code rewards capital referrers: people or entities who refer new depositors to SukukFi vaults. Refer someone who deposits and keeps capital deployed for 30 days, and you earn a monthly share of protocol fees paid in a stablecoin.

Any Berachain wallet can register. No application, no approval, no minimum stake. The reward accrues once the referred LP's capital is active and eligible.

What you earn

5% of the total protocol fee pool each month goes to LP referrers. Your share of that 5% is proportional to how much eligible deployed capital you introduced:

your share = eligible capital you introduced / total eligible deployed capital

If your referred LPs represent 12% of eligible deployed capital, you receive 12% of the 5% pool. The payout arrives in stablecoin directly to your wallet. No claiming step, no manual request. The operator pushes it on-chain.

Why pool-weighted

A per-vault referral reward structure would push referrers toward whichever vault has the highest current yield. That misaligns their incentives with the protocol's: referrers end up marketing one pool at the expense of others, not growing total liquidity.

The pool-weighted model removes that distortion. Your referral reward reflects introduced deployed capital across all vaults. Directing an LP to the PrimeTel vault versus any future vault produces the same result for an equivalent capital amount. Referrers benefit from growing the protocol, not from concentrating it.

Why 30 days instead of a cliff

Most referral programmes use a vesting cliff, typically six months. The cliff aims to ensure the referred LP stays deployed long enough to generate real revenue before the referrer earns anything.

A six-month cliff creates a different problem: it severs the connection between work and reward. Bring a $500,000 LP to the platform in January. That capital starts generating protocol fees in January. The referrer sees nothing until July. By March, with no payout in sight, the referrer has little reason to bring in more capital.

30 days works differently. Capital deployed for one full calendar month counts in the next distribution. Referral reward starts in month 2. The referrer sees a real payout while the LP is still actively deployed, which reinforces the behaviour the protocol needs: bringing in capital that stays.

When an LP withdraws, their capital drops out of the pool weight calculation in the next distribution and referral reward stops. No clawback, no enforcement mechanism. The stop is automatic.

The reward is paid in stablecoin

Referral reward arrives as a stablecoin, straight to your wallet. There is nothing to redeem and no approval to wait for.

SukukFi collects protocol fees from CommTrade participants in trUST and converts them before paying referrers. Referrers do not receive or hold trUST, and that is deliberate rather than incidental: trUST is confined to CommTrade participants settling wholesale telecom traffic between themselves, and paying referral reward in it would put it in wallets outside that set.

Two things control the programme, and both are checkable. Capital has to sit deployed for 30 continuous days before it counts, and your share is a pool weight computed from deployment data the contract records rather than a number SukukFi asserts. What is not on-chain is the payment itself: the operator makes the transfer monthly. Worth saying plainly, because the attribution being trustless does not make the payout trustless.

The on-chain mechanics

Each referrer's code derives from their wallet address:

code = keccak256(abi.encodePacked(referrerAddress, 0))

No server generates this and no database stores it. The same address always produces the same code. Anyone can verify a code's origin on-chain.

Registration calls registerCode(bytes32 code) on the CommissionRegistry contract:

A referral link embeds your code: app.sukuk.fi/?ref=0x...#vault.

When an LP deposits via that link, the app calls linkLP(code) on-chain in the same transaction. The link is permanent. Re-depositing later does not change it. The SukukFi operator then calls recordDeployment(lpAddress) once the LP's capital is active in a vault. This starts the 30-day clock.

At month end, the operator calculates pool weights, converts the corresponding fees to a stablecoin, and transfers it to all qualifying referrers in one transaction. The totalPaid mapping on the CommissionRegistry updates in the same block, so the cumulative record stays current.

How to register

  1. Go to the Invite Code section in the app at app.sukuk.fi/#invite
  2. Connect your wallet and click Register a Referral Code
  3. Copy your referral link and share it

Your referrer dashboard shows a countdown per referred LP, a running LP count, and cumulative referral reward paid to date. You can also read the state directly from the contract: daysUntilEligible(lpAddress) returns the days remaining until a given LP becomes eligible; totalPaid(referrerAddress) returns the cumulative amount paid to you.

The Invite Code documentation covers contract functions, pool weight calculation, and distribution mechanics in full.