Tutorial

Start here

This page is a guided first encounter. The live loop is not yet open. The examples use sample data. The goal is to make the moving parts visible.

What you will learn

• What a bounty looks like.
• What a submission must include.
• What a reviewer's verdict records.
• How settlement and public proof are exposed.

Step 1 — Read a sample bounty

A bounty is a small contract. It states the task, the acceptance criteria, the max USDC payout, and the review window. Read the example below as if you were going to submit work.

Expected output: you understand what the sponsor wants and the evidence shape required.

Step 2 — Prepare a submission

A submission is not a claim of correctness. It is an evidence package that a reviewer can check.

• artifact (patch, script, repro, file)
• steps to reproduce the result
• environment context (versions, commit, network)
• signed metadata to bind submitter identity

Expected output: a submission that another person can verify in under five minutes.

Step 3 — Read a verdict

A verdict cites evidence. It is not a thumbs up or down. It records what the reviewer checked, what they found, and how that maps to the sponsor's acceptance criteria.

Expected output: you understand what a reviewer is accountable for.

Step 4 — Read a settlement

Settlement happens after the challenge window. The submitter can claim USDC. The bounty page exposes the verdict, the reviewer, the payout transaction, and the evidence hashes.

Expected output: you can find the public proof of any past payout.

Where to go next

• Guides if you have a real task to run.
• Reference for exact fields and schemas.
• Explanation if you want to understand why the system is shaped this way.