Referral system is fully deployed on chain and entirely absent from the UI

[Muyideen-js]

Problem

referral_registry is one of the four deployed contracts, and the frontend never touches it.
There is no referral link, no registration step, and no earnings view.

Unused contract surface: register_referral, get_referrer, get_referrer_count, get_earnings,
get_display_name, credit.

scripts/deploy-testnet.sh wires the registry into the market contract and grants it minting
rights on pulse_token, so every deploy stands up a referral system that no user can reach.

What to build

• Referral link generation for a connected wallet
• A landing path that captures a referrer from the URL and calls register_referral on the user's
  first interaction
• An earnings view backed by get_earnings and get_referrer_count
• Display-name support via get_display_name

Acceptance criteria

• A connected user can generate and copy their referral link
• Arriving via a referral link registers the referrer on first bet -- once, and never twice
• Self-referral and unregistered-referrer attempts are rejected in the UI before submission,
  matching the contract's own guards
• Referral earnings and referred-user count are visible to the referrer
• The referral depth limit enforced by the contract is reflected in the UI

Why this is critical

Referrals are one of the two token-incentive mechanisms the deploy script already provisions.
Shipping the contract without the interface means the incentive does nothing.

[Iker2522]

I'd like to take this issue on!

I can integrate the deployed referral_registry contract into SPulse-Org / SPulse to unlock the referral incentive program in the UI.

I will implement referral link generation for connected wallets and client-side URL parameter capturing on landing. On a user's first bet attempt, the app will execute register_referral automatically while enforcing UI-level guards to block self-referrals or unregistered referrers before wallet prompts. Additionally, I will create an earnings and referral dashboard querying get_earnings, get_referrer_count, and get_display_name, accurately accounting for contract-enforced referral depth limits.

I will verify the implementation by driving a simulated referral lifecycle end-to-end on testnet—from link sharing and registration to betting and earnings tracking. PR ready in 1 day. Closes #207.

[abojeEdwin]

Hi maintainer, I've gone through the issue and I have a clear understanding of the fix for this issue. I'd love to be assigned to this issue. Thank you

[rupesh-kumar-sah]

Hello! I'd like to work on this issue.

I would like to resolve this issue. Here is my proposed execution plan:

• Implementation: Build Referral system is fully deployed on chain and entirely absent from the UI with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Testing: Add component unit tests and ensure zero TypeScript/ESLint warnings.

I am ready to start immediately—please assign this to me!