Skip to content

Bounties

Bounties give contributors permissionless entry points into active Flare priorities. Each scope ships fast, with explicit reviewers and acceptance signals already defined.

Lifecycle

  • Open — programme leads publish the spec with context, artefact checklist, reviewer, and payout bands.
  • Signal — contributors drop a thread reply linking past proof-of-work and proposed approach; acceptance happens async.
  • Build — work happens in public channels with daily snippets or Loom updates tied to the task ID.
  • Submit — deliverables land in the task board card with links, QA notes, and deployment details.
  • Review — reviewer logs acceptance, requests revisions, or resets the scope with rationale within 48 hours.
  • Payout — operations trigger payouts and recognition entries once acceptance is logged.

Submission checklist

  • Repo or design file with README that maps to acceptance criteria.
  • QA evidence: test output, staging URLs, or user walkthroughs.
  • Retro snippet covering what shipped, blockers, follow-up ideas.
  • Tag reviewer and programme lead in the thread once everything is live.

Communication contract

  • Kick off with a brief outline of planned milestones to avoid parallel work.
  • Surface blockers within 12 hours; mention if you need scope adjustments.
  • Capture decisions in the task thread so later contributors can trace context.

Escalation path

  • If reviews stall past the 48-hour SLA, ping the escalation channel.
  • For scope drift or payout concerns, log an ops ticket referencing the task ID; ops replies within one business day.