MindBlockLabs/mindBlock_app

Implement Sorted Leaderboard with Persistent Player Index

Open

#292 opened on Mar 18, 2026

View on GitHub
 (4 comments) (0 reactions) (0 assignees)TypeScript (78 forks)auto 404
enhancementgood first issuesoroban

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (PR metrics pending)

Description

Description:

The get_leaderboard() function currently returns an empty vector and serves as a placeholder. This needs to be fully implemented to support the game's social competition features.

Current Behavior:

get_leaderboard() accepts a limit: u32 parameter but always returns an empty Vec regardless of registered players or their XP. Expected Behavior: The function should return the top N players (where N = limit) sorted by XP in descending order.

Requirements:

  • Maintain a registry of all player addresses whenever a new player registers
  • The leaderboard query should respect the limit parameter
  • Players should be ranked by their current XP value
  • The implementation must work within Soroban's storage constraints — note that iterating all storage keys directly is not supported on Soroban; a separate index structure must be maintained

Acceptance Criteria:

  • get_leaderboard(5) returns the top 5 players by XP
  • Results are sorted highest XP first
  • A new player registration updates the player index
  • A test covering leaderboard ordering is included

Contributor guide

Research direction
Implement a persistent index (e.g., a vector of player addresses or a separate storage map) to track all registered players. When get leaderboard(limit) is called, iterate over the index, fetch each player's XP, sort by XP descending, and return the top 'limit' players. Ensure the index is updated on player registration.
Tech stack
rust
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustSoroban
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60