Bounties & workflow
3 min read
Browsing the bounty feed
You only see what you're eligible to claim — no scrolling past locked work.
How the feed is built
The feed filters by the three access dimensions — level, skill tier, and trust score. The minimum level to claim a bounty is the highest skill tier among its tags, so a task tagged Next.js + Database gates higher than one tagged HTML/CSS. You can additionally filter by skill tag and budget; filter state lives in the URL so feeds are shareable.
Reading a bounty card
Every card surfaces the task difficulty matrix at a glance:
| Attribute | Example |
|---|---|
| Domain | Frontend |
| Skill tier | 2 (Intermediate) |
| Estimated time | 3 hours |
| Risk level | Low / Medium / High |
| Criticality | Personal / Startup / Production |
| XP reward | 150 XP |
| Budget | ₹800 |
Note
Criticality drives how strictly a submission is reviewed — a Production task on auth or payments routes to stricter risk scoring than a Personal one. See the review pipeline.