CONTRACT: Player Registry Contract

[PoulavBhowmick03]

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

---

[mubarak23]

Batch registration can only happen via a loop and executing a write operation , loop is not really good on the contract, this can be handle Frontend

Can you explain salary cap validation,

I will love to give this a go

[PoulavBhowmick03]

Batch registration can only happen via a loop and executing a write operation , loop is not really good on the contract, this can be handle Frontend

Can you explain salary cap validation,

I will love to give this a go

Sure!
The salary cap validation depends on a number of factors. for now, you can have something like a balance for each player which will be their salary cap, that they can't go beyong that amound