Leaderboard shows five invented players and never calls the contract

[Muyideen-js]

Problem

frontend/pages.js:3 renders a leaders array of five fabricated entries:

[{name:"NovaSignal",address:"GC5D...KSL7",points:1250,accuracy:78,bets:42}, ...]

The names, truncated addresses, points, accuracy percentages, and bet counts are all literals.
leaderboard.html presents them as a "community ranking". No contract call is made on that page.

The leaderboard contract is one of the four deployed contracts and exposes the whole surface:
get_top_players, get_top_player_count, get_points, get_rank, get_stats,
get_player_count, is_banned, get_pending_reward.

Acceptance criteria

• The leaderboard reads real rankings via get_top_players / get_top_player_count
• Points, rank, and stats come from get_points / get_rank / get_stats
• Addresses are real, truncated for display, and link to Stellar Expert
• The connected user's own rank is highlighted when they appear
• Pagination is honoured -- get_top_players is explicitly paginated
• Empty state when no players are ranked yet
• No fabricated player data remains anywhere in the codebase

Why this is critical

Presenting invented users and invented accuracy figures as a community ranking is a credibility
problem, not merely a missing feature.

[Okorie2000-code]

Hi Maintainer, I’ve reviewed the issue and I’m confident I can deliver a solid solution. Kindly assign it to me.

[rupesh-kumar-sah]

Hi everyone,

I can tackle Leaderboard shows five invented players and never calls the contract. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in SPulse-Org/SPulse
• Core Implementation: Implement Leaderboard shows five invented players and never calls the contract with explicit require_auth checks, clean storage layouts, and robust Soroban contract logic.
• Quality Assurance: Add comprehensive unit tests verifying both happy-path invocations and unauthorized revert scenarios.

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