Creating Bounties

Anatomy of a Good Bounty

A well-crafted bounty should include:

Choosing the Right Bounty Level

🟢 Beginner ($50-$200)

Perfect for first-time contributors and simple tasks:

• Documentation improvements
• Minor bug fixes
• Code formatting and style improvements
• Adding comments and explanations
• Simple UI/UX tweaks
• Test coverage improvements

🟡 Intermediate ($200-$500)

For developers with domain knowledge:

• New feature implementation
• API integrations
• Complex bug fixes
• Performance optimizations
• Database schema changes
• Testing infrastructure

🔴 Advanced ($500-$2,000+)

Expert-level work requiring deep expertise:

• Architecture and design work
• Security audits and fixes
• Protocol development
• Smart contract development
• System-wide refactoring
• Research and prototyping

Creating a Bounty

Step 1: Create an Issue

1. Go to your repository's "Issues" tab
2. Click "New issue"
3. Select the "Bounty" template

Step 2: Fill Out the Template

---
name: Bounty
about: Create a bounty for contributors
title: '[BOUNTY] Add Dark Mode Toggle'
labels: 'bounty, beginner, frontend'
---

## 💰 Bounty Amount
$150 USDC

## 🎯 Description
We need to add a dark mode toggle to the settings page. Users should be able to switch between light and dark themes, and their preference should be saved.

## ✅ Acceptance Criteria
- [ ] Add toggle switch in settings page
- [ ] Implement dark mode color scheme
- [ ] Save preference to localStorage
- [ ] Apply theme on page load
- [ ] All components render correctly in both modes
- [ ] Smooth transition between modes

## 📋 Technical Requirements
- Use CSS variables for theming
- Follow existing design system
- Write tests for theme switching
- Update documentation

## 🔗 Resources
- Design mockups: [link]
- Color palette: [link]
- Related issues: #123

## ⏱️ Estimated Time
2-3 days

## 📝 Notes
This is a beginner-friendly bounty. Feel free to ask questions in comments!

Step 3: Add Labels

Use labels to help contributors find appropriate bounties:

• bounty - Required for all bounties
• beginner, intermediate, or advanced - Difficulty level
• frontend, backend, design, etc. - Category
• good-first-issue - For newcomers

Step 4: Publish and Promote

After creating the bounty:

1. Share on social media (Twitter, Discord, Reddit)
2. Post in relevant developer communities
3. Add to bounty aggregator platforms
4. Announce in your project's communication channels

Best Practices

Be Specific

Vague requirements lead to confusion and poor results. Instead of:

Write something like:

Set Realistic Deadlines

Give contributors enough time to do quality work. Consider:

• Complexity of the task
• Need for research or learning
• Review and iteration time
• Contributors may work part-time

Provide Context

Help contributors understand the bigger picture:

• Why this work matters
• How it fits into the project roadmap
• Who will benefit from this work
• Related issues or PRs

Be Available for Questions

Commit to being responsive:

• Respond to questions within 24 hours
• Provide clarification when needed
• Give feedback on work-in-progress
• Be supportive and encouraging

Managing Bounties

When Someone Claims a Bounty

When a contributor comments "I'll take this bounty":

1. Check their GitHub profile and past contributions
2. Assign them to the issue if they seem qualified
3. Set expectations for communication and timeline
4. Offer to answer questions and provide guidance

During Development

• Check in periodically to see progress
• Provide feedback on draft PRs
• Be flexible if challenges arise
• Extend deadlines if reasonable

Reviewing Submissions

When a PR is submitted:

1. Review within 2-3 business days
2. Check against acceptance criteria
3. Test the implementation
4. Provide constructive feedback
5. Approve and merge if criteria are met

Handling Issues

If work isn't meeting standards:

• Communicate clearly and kindly
• Offer specific suggestions for improvement
• Give reasonable time to address feedback
• Be willing to reassign if necessary

Ready-to-Use Bounty Templates

Bug Fix Bounty

## 💰 Bounty: $100 USDC

## 🐛 Bug Description
[Describe the bug clearly]

## 🔄 Steps to Reproduce
1. Step one
2. Step two
3. Bug occurs

## ✅ Expected Behavior
[What should happen]

## ❌ Actual Behavior
[What actually happens]

## ✅ Acceptance Criteria
- [ ] Bug is fixed
- [ ] Tests added to prevent regression
- [ ] No new bugs introduced
- [ ] Code follows style guidelines

## 📱 Environment
- Browser: [e.g., Chrome 96]
- OS: [e.g., macOS 12]
- Version: [e.g., 1.2.3]

Feature Implementation Bounty

## 💰 Bounty: $300 USDC

## 🎯 Feature Request
[Describe the feature]

## 💡 Why This Matters
[Business value and user impact]

## ✅ Acceptance Criteria
- [ ] Feature works as described
- [ ] Error handling implemented
- [ ] User-friendly error messages
- [ ] Documentation updated
- [ ] Tests cover main scenarios

## 🎨 Design
[Link to designs or mockups]

## 💻 Technical Notes
[API endpoints, database changes, etc.]

## 📚 Resources
- Related issues: #123
- Documentation: [link]

Pro Tips