Skip to content

Epic: Bounty completion (Operate -> Decide -> Payout -> Wrap -> Disputes) #638

Description

@0xdevcollins

Context

Organizer completion UI in v1 boundless: the per-bounty management surface that takes a published bounty through Operate -> Decide -> Payout -> Wrap -> Disputes. Mirrors the hackathon organizer management pages (submissions / judging / rewards) under /organizations/[id]/bounties/[bountyId]/*. Reuses the shared escrow runner (organizer scope), wallet kit, and funding modals.

Depends on the backend gaps: boundlessfi/boundless-nestjs milestone Bounty Operate to Payout (#337-#340). Payout (select-winners) + cancel already exist on the backend.

Organizer journey by mode (entryType x claimType)

Mode Decide Payout
OPEN + SINGLE_CLAIM review the submission select_winners (1)
OPEN + COMPETITION review all submissions at deadline select_winners (1-3)
APPLICATION_* + SINGLE_CLAIM select 1 applicant -> they submit -> review select_winners (1)
APPLICATION_* + COMPETITION shortlist N -> they submit -> review select_winners (1-3)

On payout settle the bounty becomes COMPLETED automatically and rewards are pushed on-chain.

Blueprint to mirror

  • Overview + tabbed mgmt: app/(landing)/organizations/[id]/hackathons/[hackathonId]/page.tsx + submissions/judging/rewards/settings
  • Winners + payout: rewards page (PublishWinnersWizard / AnnouncementStep / PreviewStep), hooks/use-hackathon-publish.ts, features/hackathons/api/use-escrow.ts (useEscrowOpRunner organizer scope), funding modals

Tasks

Out of scope

Configure (host/publish, shipped); the participant/builder UI (separate milestone). The v2 boundless-platform organizer UI (this lives in v1, alongside Configure).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions