Shonen-Labs/Roster-Rumble

BACKEND: Contest Join Flow with PrizePool Integration

Open

#12 opened on Apr 23, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (11 forks)auto 404
Backend/APIODHack 14featurehelp wanted

Repository metrics

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

Description

Description
Handle contest entry by interacting with StarkNet's PrizePool contract.

Acceptance Criteria

  • POST /contests/:id/join
    1. Verify JWT and contest exists
    2. Call PrizePool.lock_funds(entryFee) via StarkNet.js
    3. Store transaction hash in participations table
    4. Increment contest participant count
  • Handles transaction errors (e.g., insufficient funds)
  • Returns { txHash: string } on success

Technical Details

const contract = new Contract(PrizePoolABI, PRIZE_POOL_ADDRESS, provider);
const { transaction_hash } = await contract.lock_funds(
  userAddress,
  entryFee
);

Notes

  • Use StarkNet.js v5.0+
  • Implement transaction status polling (ACCEPTED_ON_L2)

Contributor guide

Research direction
Study the PrizePool contract interface and StarkNet.js v5.0+ API. Understand how to construct the contract object, call lock funds, and poll for transaction status. Review existing backend structure for route handling and database interactions.
Tech stack
typescript
Domain
backendapi
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JWTTypeScriptStarkNet.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60