Skip to content

FE: Submit work flow (on-chain anchor) + withdraw submission #625

Closed

Description

@0xdevcollins

Context

Part of the Bounty Builder Lifecycle milestone (v1 boundless). After entry (claim/join/selection), the builder submits their work, which is anchored on-chain.

Blueprint to mirror

  • components/hackathons/submissions/SubmissionForm.tsx + SubmissionAnchorProgress.tsx
  • features/hackathons/api/use-submission-anchor.ts (participant anchor via the runner)

Tasks

  • Submission form: contentUri (PR / repo / writeup / demo link per the bounty's deliverable) -> submit escrow op (useEscrowOpRunner, participant, default MANAGED) + an anchor progress dialog (draft -> on-chain -> confirmed) with tx hash.
  • Withdraw submission (withdraw-submission escrow op) before the deadline.
  • Guard by bounty status + submission deadline + entry eligibility (claimed/joined/selected/shortlisted).

Acceptance criteria

  • Submit anchors on-chain and reaches confirmed; withdraw works; flows are correctly guarded.

Depends on

  • Bounty data layer; apply/join/claim flow.

Activity

  1. linear commented on Jun 24, 2026

    @linear
  2. coderabbitai commented on Jun 24, 2026

    @coderabbitai
    🔗 Related PRs

    #451 - UI fixes [merged]
    #547 - fix(submissions): improve link validation UX, banner display, and error toasts [merged]
    #555 - feat(hackathons): add "hidden until results" submission visibility mode [merged]
    #582 - fix(rewards): match track winners by submissionId, not participantId [merged]
    #586 - fix(submissions): unbreak submission detail page + publish hackathon recap [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  3. Ojas2095 commented on Jun 24, 2026

    @Ojas2095

    /claim

    I'd like to take this on! Reviewing the repository right now and will submit a PR shortly.

  4. added 2 commits that reference this issue on Jun 25, 2026
    61ff642
    c76b521
  5. Benjtalkshow commented on Jun 25, 2026

    @Benjtalkshow
    Collaborator

    Done in #649 (merged into feat/t-replace). Closing manually since auto-close only fires on merges to the default branch.

  6. added 2 commits that reference this issue on Jun 27, 2026
    ef423a2
    7f6857a
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