Important: status enum doesn't model finalized-but-unclaimed states

[0xdevcollins]

Severity: Important (UX + indexer)

After the pull-model refactor, status == Completed covers three distinct realities:

1. Finalized; no prizes claimed yet
2. Finalized; some prizes claimed
3. Finalized; claim window expired

Frontend has to query each WinnerRecord to figure out the payout state.

Options

Option A — derived helper (lightweight):

pub enum PayoutState {
    NotFinalized,
    Claimable { unclaimed_count: u32, total_unclaimed: i128 },
    PartiallyClaimed { unclaimed_count: u32, total_unclaimed: i128, claimed_count: u32 },
    FullyClaimed,
    Reclaimable { unclaimed_count: u32, total_unclaimed: i128 },
}

pub fn get_payout_state(env: Env, hackathon_id: u64) -> Result<PayoutState, Error>;

Option B — emit HackathonFullyClaimed event when last claim happens: indexer-friendly, no extra storage.

Recommend both: derived query for one-shot UI loads, event for streaming indexers.

Tests

• Each PayoutState branch covered
• Event fires exactly once on transition to FullyClaimed

[Escelit]

I would like to implement the PayoutState solution for the "Completed" ambiguity issue. My experience includes building payout/claim tracking systems and indexer-friendly event patterns in Solidity/Starknet. I'll implement Option A + Option B as recommended: a get_payout_state derived helper that returns the full enum (NotFinalized, Claimable, PartiallyClaimed, FullyClaimed, Reclaimable) by aggregating winner records, plus a HackathonFullyClaimed event that emits exactly once when the last unclaimed prize transitions to claimed. I'll write tests covering every PayoutState branch, verify the event fires only on the exact transition to FullyClaimed, and ensure zero extra storage overhead beyond the winner records. Ready to PR this with clean, well-documented logic.

[godamongstmen897]

Can you please assign me this issue to fix