Bounty Hunter
Systematically find and submit bounties, hackathons, and paid opportunities to generate revenue. Optimized for solo operators and AI-assisted teams.
Workflow
Step 1: Discovery
Scan these platforms for active bounties:
Primary sources:
- Superteam Earn (earn.superteam.fun) — Solana ecosystem bounties, content, projects
- Colosseum (colosseum.com) — Solana hackathons, often $50K-$500K prize pools
- GitHub Issues — Bounty-tagged issues on trending repos
- Gitcoin (gitcoin.co) — Web3 grants and bounties
Secondary sources:
- ProductHunt Launch competitions
- DevPost (devpost.com) — Hackathon aggregator
- HackerOne / Bugcrowd — Security bounties (if applicable)
- Replit Bounties — Quick coding tasks
How to scan Superteam Earn:
- Visit earn.superteam.fun
- Filter by: Content, Development, Design (match your strengths)
- Sort by deadline (closest first) or prize (highest first)
- Note: Some bounties are region-locked — check eligibility carefully
Step 2: Evaluate (Kill Bad Ones Fast)
For each bounty, score on these 5 criteria:
| Criteria |
Weight |
Question |
| Prize-to-effort ratio |
30% |
$/hour if you win? Target >$100/hr |
| Win probability |
25% |
How many submissions? How niche? |
| Skill match |
20% |
Can you deliver quality with current capabilities? |
| Eligibility |
15% |
Region restrictions? KYC? Team size? |
| Strategic value |
10% |
Portfolio piece? Networking? Learning? |
Auto-reject if:
- Region-locked to a country you're not in
- Requires video/camera of a specific person (can't fake identity)
- Prize < $50 (not worth the time)
- Deadline < 24 hours AND requires significant build
- Submission count > 100 AND prize < $500
Auto-prioritize if:
- Prize > $1,000 AND < 20 submissions
- Content/writing bounty (fast turnaround)
- Matches something you've already built
- No region lock, global eligibility
Step 3: Research the Bounty
Before writing a single word:
- Read the full brief — not just the title. Every detail matters.
- Study the sponsor — visit their site, understand their product, read their docs
- Check winning submissions from past bounties by same sponsor — learn their taste
- Identify the REAL ask — often different from the surface-level description
- Note evaluation criteria — if stated, optimize for these specifically
Step 4: Draft Submission
For content bounties (threads, articles, videos):
- Research the topic deeply — 30+ minutes minimum
- Find unique angles nobody else will cover
- Include real data, real examples, real insights
- Format for the platform (X threads ≠ blog posts ≠ video scripts)
- Cite sources — judges notice this
For development bounties:
- Build a working prototype (not just mockups)
- Deploy publicly — judges click links
- README with clear setup instructions
- Demo video or screenshots showing it works
- Highlight what makes your submission unique
For design bounties:
- Show process, not just final output
- Include mobile AND desktop
- Use the sponsor's actual brand assets
- Explain design decisions
Step 5: Quality Check Before Submission
Step 6: Submit and Track
- Submit before deadline (aim for 24+ hours early — judges see early submissions)
- Log in tracking file:
| Bounty | Platform | Prize | Submitted | Deadline | Status | Outcome |
- Set reminder to check results
- If you win, document what worked for future pattern matching
- If you lose, study winning submission — what did they do differently?
Bounty Types and Strategies
Content Bounties (Fastest ROI)
X/Twitter Threads:
- 8-12 tweets, strong hook, real data
- Include relevant images/charts
- Tag the sponsor and relevant people
- Post at optimal times (9-11am EST for crypto)
Articles/Blog Posts:
- 1,500-3,000 words
- Clear structure: hook, problem, solution, examples, conclusion
- Original research or unique angle
- SEO-friendly if published on your own blog
Video:
- 2-5 minutes for explainers
- Clean audio is more important than visuals
- Show, don't just tell — screen recordings, demos
- Add captions
Development Bounties (Highest Prizes)
- Always deploy to a public URL
- Include a 60-second demo video/GIF
- Write clear README
- Handle edge cases — judges will try to break it
- Open source your code (unless brief says otherwise)
Design Bounties
- Figma files, not just screenshots
- Show responsive breakpoints
- Include interaction states (hover, active, disabled)
- Use the project's actual branding
Pipeline Management
Maintain a bounty pipeline at all times:
SCOUTING: [bounties being evaluated]
ACTIVE: [bounties being worked on — max 3 at a time]
SUBMITTED: [awaiting results]
WON: [track earnings]
LOST: [track for learning]
Rule: Never have an empty SCOUTING queue. Always have 5+ bounties being evaluated.
Rule: Max 3 active bounties. Quality > quantity. A half-assed submission is worse than no submission.
Earnings Tracking
Track cumulative earnings to measure ROI:
Total Submitted: X
Total Won: Y
Win Rate: Y/X %
Total Earned: $Z
Average $/submission: $Z/X
Average $/win: $Z/Y
Hours invested: H
Effective hourly rate: $Z/H
Target: >$50/hour effective rate. If below this, you're picking wrong bounties.
1---2name: bounty-hunter3description: Find, evaluate, and submit online bounties and hackathons for prize money. Use when user mentions "bounties", "hackathon", "earn money", "Superteam Earn", "prize money", "submissions", "freelance bounties", or asks to find paid opportunities. Covers discovery, eligibility filtering, content drafting, and submission workflows.4---5
6# Bounty Hunter
7
8Systematically find and submit bounties, hackathons, and paid opportunities to generate revenue. Optimized for solo operators and AI-assisted teams.
9
10## Workflow
11
12### Step 1: Discovery
13
14Scan these platforms for active bounties:
15
16**Primary sources:**
17- **Superteam Earn** (earn.superteam.fun) — Solana ecosystem bounties, content, projects
18- **Colosseum** (colosseum.com) — Solana hackathons, often $50K-$500K prize pools
19- **GitHub Issues** — Bounty-tagged issues on trending repos
20- **Gitcoin** (gitcoin.co) — Web3 grants and bounties
21
22**Secondary sources:**
23- **ProductHunt** Launch competitions
24- **DevPost** (devpost.com) — Hackathon aggregator
25- **HackerOne** / **Bugcrowd** — Security bounties (if applicable)
26- **Replit Bounties** — Quick coding tasks
27
28**How to scan Superteam Earn:**
291. Visit earn.superteam.fun
302. Filter by: Content, Development, Design (match your strengths)
313. Sort by deadline (closest first) or prize (highest first)
324. Note: Some bounties are region-locked — check eligibility carefully
33
34### Step 2: Evaluate (Kill Bad Ones Fast)
35
36For each bounty, score on these 5 criteria:
37
38| Criteria | Weight | Question |
39|----------|--------|----------|
40| Prize-to-effort ratio | 30% | $/hour if you win? Target >$100/hr |
41| Win probability | 25% | How many submissions? How niche? |
42| Skill match | 20% | Can you deliver quality with current capabilities? |
43| Eligibility | 15% | Region restrictions? KYC? Team size? |
44| Strategic value | 10% | Portfolio piece? Networking? Learning? |
45
46**Auto-reject if:**
47- Region-locked to a country you're not in
48- Requires video/camera of a specific person (can't fake identity)
49- Prize < $50 (not worth the time)
50- Deadline < 24 hours AND requires significant build
51- Submission count > 100 AND prize < $500
52
53**Auto-prioritize if:**
54- Prize > $1,000 AND < 20 submissions
55- Content/writing bounty (fast turnaround)
56- Matches something you've already built
57- No region lock, global eligibility
58
59### Step 3: Research the Bounty
60
61Before writing a single word:
62
631. **Read the full brief** — not just the title. Every detail matters.
642. **Study the sponsor** — visit their site, understand their product, read their docs
653. **Check winning submissions** from past bounties by same sponsor — learn their taste
664. **Identify the REAL ask** — often different from the surface-level description
675. **Note evaluation criteria** — if stated, optimize for these specifically
68
69### Step 4: Draft Submission
70
71**For content bounties (threads, articles, videos):**
72
731. Research the topic deeply — 30+ minutes minimum
742. Find unique angles nobody else will cover
753. Include real data, real examples, real insights
764. Format for the platform (X threads ≠ blog posts ≠ video scripts)
775. Cite sources — judges notice this
78
79**For development bounties:**
80
811. Build a working prototype (not just mockups)
822. Deploy publicly — judges click links
833. README with clear setup instructions
844. Demo video or screenshots showing it works
855. Highlight what makes your submission unique
86
87**For design bounties:**
88
891. Show process, not just final output
902. Include mobile AND desktop
913. Use the sponsor's actual brand assets
924. Explain design decisions
93
94### Step 5: Quality Check Before Submission
95
96- [ ] Does this EXACTLY match the brief requirements?
97- [ ] Would you be proud to show this to a potential employer?
98- [ ] Is it better than what 80% of submissions will look like?
99- [ ] Are all links working? All images loading?
100- [ ] Proofread for typos, grammar, formatting?
101- [ ] Does it show genuine understanding of the sponsor's product?
102
103### Step 6: Submit and Track
104
1051. Submit before deadline (aim for 24+ hours early — judges see early submissions)
1062. Log in tracking file:
107 ```
108 | Bounty | Platform | Prize | Submitted | Deadline | Status | Outcome |
109 ```
1103. Set reminder to check results
1114. If you win, document what worked for future pattern matching
1125. If you lose, study winning submission — what did they do differently?
113
114## Bounty Types and Strategies
115
116### Content Bounties (Fastest ROI)
117
118**X/Twitter Threads:**
119- 8-12 tweets, strong hook, real data
120- Include relevant images/charts
121- Tag the sponsor and relevant people
122- Post at optimal times (9-11am EST for crypto)
123
124**Articles/Blog Posts:**
125- 1,500-3,000 words
126- Clear structure: hook, problem, solution, examples, conclusion
127- Original research or unique angle
128- SEO-friendly if published on your own blog
129
130**Video:**
131- 2-5 minutes for explainers
132- Clean audio is more important than visuals
133- Show, don't just tell — screen recordings, demos
134- Add captions
135
136### Development Bounties (Highest Prizes)
137
138- Always deploy to a public URL
139- Include a 60-second demo video/GIF
140- Write clear README
141- Handle edge cases — judges will try to break it
142- Open source your code (unless brief says otherwise)
143
144### Design Bounties
145
146- Figma files, not just screenshots
147- Show responsive breakpoints
148- Include interaction states (hover, active, disabled)
149- Use the project's actual branding
150
151## Pipeline Management
152
153Maintain a bounty pipeline at all times:
154
155```
156SCOUTING: [bounties being evaluated]
157ACTIVE: [bounties being worked on — max 3 at a time]
158SUBMITTED: [awaiting results]
159WON: [track earnings]
160LOST: [track for learning]
161```
162
163**Rule: Never have an empty SCOUTING queue.** Always have 5+ bounties being evaluated.
164
165**Rule: Max 3 active bounties.** Quality > quantity. A half-assed submission is worse than no submission.
166
167## Earnings Tracking
168
169Track cumulative earnings to measure ROI:
170
171```
172Total Submitted: X
173Total Won: Y
174Win Rate: Y/X %
175Total Earned: $Z
176Average $/submission: $Z/X
177Average $/win: $Z/Y
178Hours invested: H
179Effective hourly rate: $Z/H
180```
181
182Target: >$50/hour effective rate. If below this, you're picking wrong bounties.