Reference

Preview · MVP under construction · Public roadmap and docs.

Reference

Reference is intentionally dry. Fields, types, validation. No persuasion. No origin story. Field shapes here are subject to change while the system is preview, but the names are stable enough to design against.

For a plain-English overview of the same concepts, see the Plain-English FAQ. For the canonical evidence bundle format that submissions and verdicts hash over, see /reference/evidence-schema.

Bounty object

Field	Type	Required	Description
`id`	string	yes	Unique bounty identifier.
`sponsor`	address	yes	Funding wallet on Base.
`title`	string	yes	Short, human-readable.
`spec`	markdown	yes	Task spec including acceptance criteria.
`payout_max`	uint256	yes	Max USDC payable for accepted work.
`review_window`	duration	yes	Time reviewer has to verdict.
`challenge_window`	duration	yes	Time before settlement is final.
`state`	enum	yes	See escrow state machine.
`evidence_anchor`	hash	no	Hash of offchain evidence bundle.

Submission object

Field	Type	Required	Description
`id`	string	yes	Unique submission identifier.
`bounty_id`	string	yes	Bounty this submission targets.
`submitter`	address	yes	Wallet that signed the submission.
`artifact`	uri + hash	yes	Patch, script, repro, file.
`evidence`	uri + hash	yes	Repro steps, logs, environment.
`submitted_at`	timestamp	yes	Submission time.
`status`	enum	yes	queued, reviewed, accepted, rejected, disputed.

Review decision object

Field	Type	Required	Description
`id`	string	yes	Unique review identifier.
`submission_id`	string	yes	Submission this review applies to.
`reviewer`	address	yes	Admitted reviewer wallet.
`verdict`	enum	yes	accept, reject, dispute.
`citations`	uri + hash[]	yes	Evidence checked.
`signature`	signature	yes	Reviewer signature over the verdict.
`decided_at`	timestamp	yes	When the verdict was signed.

Reviewer profile

Field	Type	Required	Description
`id`	string	yes	Reviewer identifier.
`address`	address	yes	Reviewer wallet on Base.
`admitted_at`	timestamp	yes	Admission timestamp.
`bond`	uint256	yes	BOUNTY bonded.
`category_limits`	map	no	Per-category payout caps.
`history`	list	no	Past verdicts, challenge outcomes.
`status`	enum	yes	active, paused, removed.

Escrow state machine

Figure 2 Escrow state machine

Draft ─▶ Funded ─▶ In review ─▶ Queued ─▶ Settled ─▶ Claimed
                       │             │
                       ▼             ▼
                   Disputed       Refunded

USDC-denominated bounty state. Disputed and Refunded are off the happy path.

Draft — created but not funded.
Funded — USDC locked.
In review — submissions being evaluated.
Queued — verdict signed, challenge window open.
Settled — challenge window passed, payout finalized.
Claimed — USDC transferred to submitter.
Disputed — contested verdict, escalation path engaged.
Refunded — bounty closed without paid submission.

Roles and permissions

Sponsor

Create, fund, cancel before funded, close after refund window.

Submitter

Submit, withdraw before review starts, claim after settle.

Reviewer

Verdict, sign, escalate within review window.

Protocol

Hold escrow, enforce state transitions, expose proof.

Token facts

Symbol

BOUNTY

Network

Base

Address

0x33e167FA22c9D78236b1a21C80E8B712205D1b07

Role

Reviewer bonding. Not a payment unit. Not a governance token by default.

Pool

DEX Screener →

More on the BOUNTY role in /token and /explain.

AgentBounty · pages