Shonen-Labs/Roster-Rumble

CONTRACT: Player Registry Contract

Open

#26 opened on Apr 23, 2025

View on GitHub
 (2 comments) (0 reactions) (1 assignee)TypeScript (11 forks)auto 404
ODHack 14contractgood first issue

Repository metrics

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

Description

Title: On-Chain Player Metadata Management
Description
Create contract to store player profiles with IPFS metadata.

Acceptance Criteria:

  • Stores player attributes:
    • Position
    • Base salary
    • Metadata CID
  • Allows admin updates
  • Emits PlayerUpdated events

Technical Details:

#[starknet::contract]
mod PlayerRegistry {
    #[storage]
    struct Storage {
        players: LegacyMap<felt252, Player>,
        admin: felt252
    }

    #[derive(Drop, Serde)]
    struct Player {
        position: u8,
        base_salary: u64,
        metadata_cid: felt252
    }

    #[external(v0)]
    fn register_player(
        ref self: ContractState,
        id: felt252,
        position: u8,
        salary: u64,
        cid: felt252
    ) {
        assert(get_caller_address() == self.admin.read(), 'Unauthorized');
        self.players.write(id, Player { position, base_salary: salary, metadata_cid });
    }
}

Notes:

  • Add versioning for metadata updates
  • Implement batch registration
  • Add salary cap validation

Contributor guide

Research direction
Implement the PlayerRegistry contract following the provided template, including storage, admin checks, event emission, and additional features like versioning, batch registration, and salary cap validation.
Tech stack
rust
Domain
blockchain
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-3 hours
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
Cairo/StarknetSmart contract development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65