How the CommissionRegistry Works: On-Chain Referrals With No Intermediary

29 June 2026·Shazad Khandefireferral rewardinvite-codeon-chain

The invite referral reward is a share of real protocol fees, computed on-chain, not a flat bounty per signup.

Most referral programs run on a database. You get a code, share it, someone signs up, the company credits your account. The referral reward calculation happens on a server you cannot inspect, paid on a schedule you cannot verify, and revocable at will.

SukukFi's CommissionRegistry runs on Berachain. The code derives from your address. The link registers on-chain. The pool weight calculates from vault state. The payment itself is a stablecoin transfer the operator makes each month, so attribution needs no server intermediary and no approval step, while the transfer does depend on the operator making it.

Here is how it works.

Where the code comes from

Your invite code is a deterministic hash of your Berachain wallet address:

code = keccak256(walletAddress)[0:8]

The contract computes this on-chain. No server generates it, no database stores it. Two wallets will always produce two different codes. Your code exists before you register. Registration is just the act of making yourself findable in the contract's index so referred LPs can link to you.

Your referral link is: https://app.sukuk.fi/?ref=YOUR_CODE

How an LP links to you

When a new LP clicks your referral link and deposits into a SukukFi vault, the app calls linkLP(referrerAddress) on the CommissionRegistry contract. This records the association on-chain: this LP's address is linked to this referrer's address.

The link is permanent. An LP cannot switch to a different referrer after depositing. This prevents someone from introducing capital through one link, then retroactively crediting a different referrer once the deployment is confirmed eligible.

The 30-day deployment requirement

Earning referral reward requires two conditions: the LP must be linked to you, and their capital must have been deployed for at least 30 days.

The clock starts when the SukukFi operator calls recordDeployment(lpAddress) on the contract, not at the LP's deposit time. There is a short lag between when an LP's ERC-7540 async deposit is fulfilled and when the operator confirms the deployment on-chain. The dashboard shows a countdown per referred LP. You can also query daysUntilEligible(lpAddress) directly on the contract. type(uint256).max means no deployment has been recorded yet.

The 30-day minimum serves a specific purpose: it rules out flash deposits and confirms that referred LPs are real capital providers, not single-cycle optimisers. ERC-7540 async vaults are naturally sticky: 15-day invoice settlement cycles make early withdrawal uncommon. The 30-day window simply makes the intent explicit and on-chain verifiable.

How referral reward calculates

Each month, SukukFi takes 5% of the protocol fee pool and distributes it across all eligible referrers, weighted by the proportion of qualifying capital each referrer brought in.

Worked through with real numbers:

Total eligible deployed capital: $2,000,000
Capital you introduced: $200,000
Your pool weight: 10%
Total protocol fees that month: $80,000
Referrer pool (5% of fees): $4,000
Your referral reward: $400, paid in stablecoin

The protocol fee pool is not only the performance fee. It also includes CommTrade settlement fees (0.15% on supplier payments) and telecom transaction fees ($0.00015 per voice, SMS, or data transaction). So the pool still funds referral reward on the Phase 1 vault, where the performance fee is currently waived. If that fee is charged on a future pool, it joins the same pool and the referral reward scales with it.

The reward stops automatically when a referred LP exits the vault. Their capital leaves the pool weight calculation; your share adjusts accordingly for the next distribution. No clawback on past payments, no penalty for the referrer.

What pool-weighted means in practice

The weighting means your referral reward scales with how much capital you introduce, not just how many LPs. Introducing one LP with $1m matters more than introducing ten LPs with $10k each.

This also means referral reward is not a flat percentage of referred deposits. It is a share of a fixed pool: the 5% reward pool. If a large institutional LP enters through another referrer's link, your percentage of the pool shrinks even if your referred capital stays constant. The pool is the same size; you now represent a smaller fraction of it.

For referrers building a referral business: the most valuable thing you can do is bring in capital providers who maintain long-term deployment, not one-time deposits.

One address, one code

Each wallet address maps to exactly one invite code. You cannot register multiple codes from the same address. If you want to track different referral channels separately, register each channel with a different wallet.

An LP's referral link sets on first deposit and cannot be changed. This prevents the referral system from being gamed by switching referrers after capital is deployed. The link that brought the LP in is the one that stays.

Supplementing your yield with two wallets

There is a two-wallet strategy worth knowing. Register an invite code on a second wallet, then deposit into a SukukFi vault from your primary wallet using that second wallet's referral link. Your primary wallet earns LP yield on its deployed capital. Your second wallet earns referral reward on that same capital from the 5% referrer pool. That referral reward is additive to your LP return, not a redirect of it.

Single-wallet self-referral is a wash. Referral reward on your own deposit from the same address is yield you were already receiving as an LP, just routed through an extra step.

Referral reward does not pay immediately on deposit. The 30-day deployment clock means you wait at minimum one month from when your referred LP's capital is confirmed deployed. Referral reward then accrues monthly for as long as the LP stays deployed.

Why this runs on-chain

A server-based referral system has three failure modes: the company changes the referral reward rate, pauses payouts, or disputes whether a referral was valid. All three depend on the company's discretion.

The CommissionRegistry removes that discretion for the mechanics of attribution. The link between an LP and an referrer is on-chain and verifiable. The pool weight calculation reads from vault state, not an internal record you have to trust. The payout is a stablecoin transfer straight to your wallet.

SukukFi still controls the timing of the monthly distribution, and makes the transfer itself. This is not fully trustless and it would be wrong to call it that. But the attribution and the calculation happen on-chain, so the maths is public and auditable even where the payment is not.

For an introducing LP who wants to verify their referral reward is correctly calculated: the contract state, the vault balances, and the linked LP records are all readable on Berachain. No customer service ticket required.