Quick Start

1. Use the Template (30 seconds)

Click the button below to create your repository from the GitForge template:

1. Choose your organization or personal account
2. Name your repository (e.g., "my-dao")
3. Select "Public" visibility
4. Click "Create repository from template"

2. Enable GitHub Actions (1 minute)

Navigate to your new repository and enable Actions:

1. Click "Settings" in your repository
2. Click "Actions" → "General" in the left sidebar
3. Select "Allow all actions and reusable workflows"
4. Click "Save"

3. Optional: Customize Config (2 minutes)

Edit .github/BOUNTY_CONFIG.json to customize your bounty amounts:

{
  "bounty_levels": {
    "beginner": {
      "emoji": "🟢",
      "amount": "$50-$200",  // ← Change these amounts
      "description": "Basic coding, documentation"
    },
    "intermediate": {
      "emoji": "🟡",
      "amount": "$200-$500",  // ← Change these amounts
      "description": "Features, integrations"
    },
    "advanced": {
      "emoji": "🔴",
      "amount": "$500-$2000",  // ← Change these amounts
      "description": "Protocol work, security"
    }
  },
  "payment_method": "USDC",  // ← or "manual", "equity", etc.
  "auto_payout": false  // ← Set to true when ready for auto-payments
}

Click the "Edit" button (pencil icon) in GitHub, make your changes, and commit.

4. Create Your First Bounty (1.5 minutes)

Let's create a simple bounty to test the system:

1. Go to the "Issues" tab in your repository
2. Click "New issue"
3. Select "Create a Bounty"
4. Fill out the form with these example values:

Title: [BOUNTY] Improve README documentation

Bounty Amount: $50

Difficulty Level: Beginner

Description:
Update the README.md file to include:
- A better project description
- Setup instructions
- Contributing guidelines
- License information

Acceptance Criteria:
- [ ] README has clear project description
- [ ] Setup instructions are complete
- [ ] Contributing section added
- [ ] Proper formatting and grammar

Skills Required: Technical writing, Markdown

Estimated Time: 1-2 hours

5. Click "Submit new issue"

What Happens Next?

1. Contributors Find Your Bounty

Contributors browsing GitHub will see your bounty in the Issues tab. Make sure to:

• Share it on social media (Twitter, Discord, etc.)
• Post in relevant developer communities
• Tag it with appropriate labels

2. Someone Claims It

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

• Review their profile and past work
• Assign them to the issue if they're qualified
• Respond with any clarifications they need

3. They Submit a Pull Request

When work is submitted:

• Review the PR within 2-3 days
• Check if it meets the acceptance criteria
• Provide feedback or approve
• Merge when ready

4. Payment is Processed

After merging:

• Manual: Send payment via your chosen method
• Automatic: GitHub Actions triggers payment
• Confirm payment with the contributor

Next Steps

Additional Resources

Common Questions

Do I need to use cryptocurrency?

No! You can use manual payments (PayPal, Venmo, bank transfer) or equity/shares. Crypto is just one option.

How much should I pay for bounties?

Start with the suggested ranges ($50-$200 for beginners, $200-$500 for intermediate, $500+ for advanced) and adjust based on your budget and the market.

What if no one claims my bounty?

Try:

• Increasing the bounty amount
• Making requirements clearer
• Promoting it more widely
• Breaking it into smaller bounties

Can I use this for private repositories?

Yes! GitForge works with both public and private repositories. Just ensure contributors have access.

How do I handle disputes?

Communicate clearly and refer to the acceptance criteria. If needed, seek community input through GitHub Discussions.