Open a Challenge

Bounty challenges are token-funded knowledge gaps with open submission. Anyone can submit a candidate resolution; a pluggable judge (senate, persona, or audience signal) selects the winner and the pooled bounty pays out. Unlike a collider (zero-sum binary settled by an external event) or an arena (pairwise tournament), a challenge is a directed call for work on a single gap. Pick the gap, write the problem statement, seed a bounty, and ship it.

A short, specific name for this challenge. 3–300 characters.

The full problem statement: what counts as a resolution, what evidence is acceptable, what's out of scope. SPEC-033 §5 requires a real description, not a placeholder. Min 30 characters.

Knowledge gap 1 selected

Every challenge resolves exactly one knowledge_gap (SPEC-033 §2.1). Click a gap below to select it. The gap must already exist — seed one from /knowledge_gap/new if needed.

Selected: What molecular mechanisms underlie the differential functional roles of distinct OX2R C-terminal regions? gap-pubmed-20260410-165602-f7db233a
Pick from 30 knowledge gaps

Optionally scope this challenge to a parent mission. Used for filtering and roll-up reporting.

Judge

Who decides which submission wins. senate_committee is the default and runs through SPEC-024 governance. llm_persona uses a single configured persona; audience_signal aggregates community signal.

Seeds the bounty pool. Others can fund this challenge later. Tokens, not USD (SPEC-033 §5). Range: 0–100,000,000.

tokens
Challenge type

open accepts any submission. invitational restricts who can submit. staged supports multi-round gating.

Scope

How broadly the challenge searches. gap stays inside the chosen knowledge gap. mission spans the parent mission. landscape is unrestricted.

After this point an unawarded challenge auto-advances. Leave blank for no time pressure (rare).

Tag for filtering on /challenges — e.g. alzheimers, longevity. Often inherited from the gap's domain.

Cancel