PULSE token balances and reward claiming are invisible in the app

[Muyideen-js]

Problem

PULSE is the project's reward token. The frontend never reads it and never claims it.

• frontend/wallet.js displays only native XLM, from Horizon (loadBalance)
• No call to pulse_token's balance, total_supply, symbol, or decimals
• No call to the leaderboard's get_pending_reward or claim_pending_rewards

A user earns PULSE by betting and by referring, and has no way to see the balance or collect queued
rewards. scripts/deploy-testnet.sh explicitly grants the market, referral, and leaderboard
contracts minter rights on the token, so rewards are being minted into a balance nobody can see.

Acceptance criteria

• A connected wallet shows its PULSE balance alongside XLM, with decimals read from the contract
• Pending rewards are surfaced via get_pending_reward
• A Claim rewards action calls claim_pending_rewards with the standard
  simulate -> sign -> submit -> poll flow
• Token metadata (name, symbol, decimals) is read from the contract, not hardcoded
• The token contract address is read from frontend/contracts.json, never inlined

Why this is critical

The reward token is the economic core of the product and currently has no user-facing existence.

[guptakumarranjeet150]

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

I can tackle PULSE token balances and reward claiming are invisible in the app. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in SPulse-Org/SPulse
• Implementation: Deliver a clean, modular solution for PULSE token balances and reward claiming are invisible in the app strictly following SPulse-Org/SPulse conventions.
• Testing: Cover changes with automated tests ensuring CI passes smoothly.
• PR: Atomic commit with clean git hygiene and passing CI

Happy to pick this up today—please assign to me!

[Iker2522]

I'd like to take this issue on!

I can bring full visibility and interaction to the PULSE reward token within SPulse-Org / SPulse.

I will update frontend/wallet.js to dynamically load pulse_token metadata (symbol, decimals, name) and account balances using the contract address specified in frontend/contracts.json. I will also integrate live pending reward tracking via leaderboard.get_pending_reward and implement the complete "Claim Rewards" action leveraging claim_pending_rewards across standard Soroban simulation, signing, and polling steps.

I will verify the workflow on testnet by accruing rewards through bets and referrals, confirming that pending rewards surface correctly and claim transactions accurately update wallet PULSE balances. PR ready in 1 day. Closes #208.

[guptakumarranjeet150]

Hello! I would like to work on this issue.

I would love to take this on. My planned approach:

• Provide a structured solution for PULSE token balances and reward claiming are invisible in the app addressing all stated requirements.
• Ensure the change passes all existing lint, format, and CI verification pipelines.

Happy to pick this up today—please assign to me!