From 44c693e4be7f9a8ab9c34f98a4dd352bf06f09b5 Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 13:33:22 -0700 Subject: [PATCH 01/15] Update guides/solving-bounties.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/solving-bounties.mdx | 218 ++++++++++++++++++++++++++++++++++++ 1 file changed, 218 insertions(+) create mode 100644 guides/solving-bounties.mdx diff --git a/guides/solving-bounties.mdx b/guides/solving-bounties.mdx new file mode 100644 index 0000000..68ec0af --- /dev/null +++ b/guides/solving-bounties.mdx @@ -0,0 +1,218 @@ +--- +title: "Solving bounties" +description: "How to find, solve, and get paid for bounties fast" +--- + +## Overview + +Bounty.new lets you earn money solving real problems. Find bounties, submit solutions, get approved, and receive instant payment. Here's how to maximize your efficiency. + +## Before you start + + + + Go to [bounty.new/settings/payments](https://bounty.new/settings/payments) and connect your Stripe account. You must do this before creators can approve your submissions. + + + Check the bounty feed or connect your GitHub/Discord to see bounties in your workflow. + + + +## Finding bounties + +### Where to look + +- **Bounty.new dashboard**: Browse all open bounties +- **GitHub**: Look for issues with bounty labels in repos you follow +- **Discord**: Check servers with the bounty.new bot installed +- **Linear**: Some teams create bounties from Linear issues + +### Filtering for the right bounties + +Look for: + +- **Clear requirements**: Well-defined scope and acceptance criteria +- **Fair reward**: Payment matches the complexity and time required +- **Reasonable deadline**: Enough time to do quality work +- **Responsive creator**: Check if they answer questions quickly + + + Start with smaller bounties ($100-$500) to build reputation, then move to larger ones. + + +## Solving bounties fast + +### 1. Understand the requirements + + + + Read the full description, acceptance criteria, and any linked docs before starting. + + + If anything is unclear, ask immediately. Don't waste time guessing. + + + Look at the codebase, related PRs, and issues to understand context. + + + Make sure you understand exactly what "done" looks like before coding. + + + +### 2. Plan your approach + +- **Break it down**: Split the work into smaller tasks +- **Estimate time**: Be realistic about how long it'll take +- **Check dependencies**: Make sure you have access to everything you need +- **Set up environment**: Get the project running locally first + +### 3. Execute efficiently + + + + Build the main functionality first, polish later. + + + Don't wait until the end to test. Catch issues early. + + + Match the existing code style and conventions. + + + Add comments, update docs, explain your approach. + + + +### 4. Submit quality work + +Your submission should include: + +- **Working code**: Tested and functional +- **Tests**: Unit tests or proof it works +- **Documentation**: README updates, inline comments +- **Clean commits**: Clear commit messages +- **Demo**: Screenshots, video, or live link if applicable + + + Don't submit half-finished work. Creators want solutions they can merge immediately. + + +## Submitting your solution + +### On GitHub + +1. Fork the repository +2. Create a feature branch +3. Make your changes +4. Open a pull request +5. Reference the bounty in your PR description + +### On bounty.new dashboard + +1. Navigate to the bounty +2. Click **Submit solution** +3. Provide your GitHub PR link or deliverable +4. Add notes explaining your approach +5. Click **Submit** + +### What happens next + + + + They'll test your solution and provide feedback. + + + Address any feedback quickly to stay competitive. + + + Once approved, payment processes instantly. + + + Funds hit your Stripe account immediately—no waiting. + + + +## Getting paid + +### Payment timeline + +- **Instant**: Payment processes the moment your submission is approved +- **No fees**: You keep 100% of the bounty amount +- **Direct deposit**: Funds go straight to your connected Stripe account + +### Payout methods + +Connect your Stripe account at [bounty.new/settings/payments](https://bounty.new/settings/payments): + +- **Bank transfer**: Direct deposit to your bank account +- **Instant access**: No waiting periods or holds +- **Secure**: All payments processed through Stripe + + + Make sure your Stripe account is fully verified to avoid payout delays. + + +## Tips for success + +### Maximize your earnings + + + + First quality submission often wins. Speed matters. + + + Keep the creator updated. Show progress, ask questions. + + + Go slightly beyond requirements. Add tests, docs, polish. + + + Deliver consistently to get invited to private bounties. + + + +### Common mistakes to avoid + +- **Starting without clarification**: Always confirm requirements first +- **Submitting incomplete work**: Only submit when it's truly done +- **Ignoring code style**: Match the existing patterns +- **Missing tests**: Include tests unless explicitly not required +- **Poor communication**: Update the creator on your progress + +## Troubleshooting + + + + - Make sure you're using a supported country + - Verify your identity with Stripe + - Contact [grim@bounty.new](mailto:grim@bounty.new) if issues persist + + + - Read the feedback carefully + - Ask specific questions about what needs to change + - Revise and resubmit quickly + - Don't take it personally—iterate and improve + + + - Check that your Stripe account is verified + - Bank transfers can take 1-2 business days + - Verify your bank details are correct + - Contact [grim@bounty.new](mailto:grim@bounty.new) for help + + + - Reach out to the creator to understand why + - If you've done significant work, discuss compensation + - Move on to the next bounty—don't dwell on it + + + +## Next steps + + + + Connect GitHub, Discord, or Linear to find bounties faster. + + + Configure your Stripe account and payout preferences. + + From aa8477d34c770cb90470cbbaf5a9ef7ffa4c4456 Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 13:33:54 -0700 Subject: [PATCH 02/15] Update guides/getting-paid.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/getting-paid.mdx | 160 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 160 insertions(+) create mode 100644 guides/getting-paid.mdx diff --git a/guides/getting-paid.mdx b/guides/getting-paid.mdx new file mode 100644 index 0000000..883c829 --- /dev/null +++ b/guides/getting-paid.mdx @@ -0,0 +1,160 @@ +--- +title: "Getting paid" +description: "How payouts work for bounty solvers" +--- + +## Overview + +Get paid instantly when your work is approved. No waiting periods, no hassle. Connect your Stripe account and receive 100% of the bounty amount directly to your bank. + +## Setting up payouts + + + + Go to [bounty.new/settings/payments](https://bounty.new/settings/payments) and click **Connect Stripe account**. + + + Stripe will ask for basic information to verify your identity. This is required by financial regulations. + + + Link your bank account to receive direct deposits. + + + Once connected, you can receive payments immediately upon approval. + + + + + You must connect your Stripe account before a creator can approve your submission. Set this up first. + + +## How payouts work + +### Payment timeline + + + + You submit your work for a bounty. + + + The bounty creator reviews and tests your submission. + + + Once approved, payment processes instantly. + + + Money hits your Stripe account immediately—no waiting period. + + + +### Payout methods + +- **Direct bank transfer**: Funds deposited directly to your bank account +- **Instant processing**: Payment processes the moment your submission is approved +- **No fees**: You keep 100% of the bounty amount + + + Developers pay zero fees. Creators cover the 5% platform fee, so you receive the full bounty amount. + + +## Payment details + +### What you receive + +For a $500 bounty: + +``` +Bounty amount: $500.00 +Platform fee: $ 0.00 (paid by creator) +Processing fee: $ 0.00 (paid by creator) +───────────────────────────── +You receive: $500.00 +``` + +### Bank transfer timing + +- **Instant to Stripe**: Funds available in your Stripe balance immediately +- **Bank transfer**: 1-2 business days to reach your bank account +- **No holds**: No waiting periods or payment holds + +## Troubleshooting + + + + - Make sure you're in a supported country + - Verify your identity information is correct + - Check that you're using a valid bank account + - Contact [grim@bounty.new](mailto:grim@bounty.new) if issues persist + + + - Check that your Stripe account is fully verified + - Bank transfers take 1-2 business days + - Verify your bank account details are correct + - Check your Stripe dashboard for pending transfers + - Contact [grim@bounty.new](mailto:grim@bounty.new) for help + + + - Double-check all information is accurate + - Ensure your documents are clear and valid + - Contact Stripe support for verification issues + - Reach out to [grim@bounty.new](mailto:grim@bounty.new) if stuck + + + - Check the original bounty amount + - Verify there were no partial payments + - Review your Stripe transaction history + - Contact [grim@bounty.new](mailto:grim@bounty.new) if there's a discrepancy + + + +## Payment security + +### How we protect your money + +- **Escrow system**: Funds are held securely until work is approved +- **Instant release**: Payment processes immediately upon approval +- **Stripe powered**: All payments processed through Stripe's secure infrastructure +- **No chargebacks**: Once approved, payment is final + +### Your protection + +- **Work first, then payment**: Only submit when you're confident in your solution +- **Clear requirements**: Make sure you understand what's expected before starting +- **Communication**: Keep the creator updated to avoid surprises +- **Dispute resolution**: Contact [grim@bounty.new](mailto:grim@bounty.new) if there's an issue + +## Tax information + + + Bounty.new does not withhold taxes. You're responsible for reporting your earnings according to your local tax laws. + + +### What you need to know + +- **Independent contractor**: You're paid as an independent contractor +- **Tax forms**: Stripe may require tax information depending on your country +- **Record keeping**: Keep track of your earnings for tax purposes +- **Consult a professional**: Talk to a tax advisor about your specific situation + +## Maximizing your earnings + + + + The more quality work you deliver, the more you earn. + + + Consistent quality work leads to private bounty invitations. + + + First quality submission often wins. Speed + quality = more earnings. + + + Good communication leads to faster approvals and repeat work. + + + +## Need help? + + + Questions about payouts? We're here to help. + From bfca72223a35835515ed2def44f90e9e7104680b Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 13:34:35 -0700 Subject: [PATCH 03/15] Update guides/payments.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/payments.mdx | 199 +++++++++++++++++++++++++------------------- 1 file changed, 115 insertions(+), 84 deletions(-) diff --git a/guides/payments.mdx b/guides/payments.mdx index 0c7cf6f..5022bc6 100644 --- a/guides/payments.mdx +++ b/guides/payments.mdx @@ -1,81 +1,57 @@ --- -title: "Payments and payouts" -description: "How payments work on bounty.new" +title: "Funding bounties" +description: "How to fund bounties and manage payments as a creator" --- ## Overview -Bounty.new handles all payment processing so you can focus on getting work done. Instant payouts, transparent fees, and multiple payment methods. +Fund your bounties with a credit card and let bounty.new handle the rest. When you approve a submission, the developer gets paid instantly—no manual transfers, no hassle. ## How it works -### For creators - - - Funds are held in our platform account when you publish a bounty. + + Set up your bounty with a clear description and reward amount. - - When you approve a submission, the payout processes instantly, and the winning submission gets paid immediately. + + Pay upfront with a credit card. Funds are held in escrow. - - -### For developers - - - - Submit your solution for a bounty. - - - Creator reviews and approves your submission. + + Developers submit solutions. You review and test their work. - - Funds hit your account immediately—no waiting period. + + When you approve a submission, the developer gets paid instantly. ## Payment methods -### Adding funds (creators) +### Funding bounties - **Credit card**: Visa, Mastercard, American Express -- Instant processing -- 2.9% + \$0.30 processing fee - -### Receiving payouts (developers) - -Connect your Stripe account at [bounty.new/settings/payments](https://bounty.new/settings/payments) to receive payouts. - -- **Stripe Connected Account**: Direct deposit to your bank -- Instant payout upon approval -- No fees +- **Instant processing**: Your bounty goes live immediately +- **Secure**: All payments processed through Stripe - You must connect your Stripe account before a bounty creator can approve your submission. + Bounties must be funded upfront. This ensures developers get paid immediately when their work is approved. -## Fees +## Fees and pricing ### Platform fees -| Role | Fee | When charged | -| --------- | --- | ---------------------- | -| Creator | 5% | When bounty is created | -| Developer | 0% | No fees on payouts | +| Fee type | Amount | When charged | +| ----------------- | ----------- | ---------------------- | +| Platform fee | 5% | When bounty is created | +| Card processing | 2.9% + $0.30| When bounty is created | - Developers keep 100% of the bounty amount. Creators pay a 5% platform fee. + Developers receive 100% of the bounty amount. You pay the platform fee and processing fees upfront. -### Payment processing fees - -Additional fees from payment providers: - -- **Credit card**: 2.9% + \$0.30 - ### Example calculation -For a \$500 bounty: +For a $500 bounty: ``` Bounty amount: $500.00 @@ -87,36 +63,44 @@ Total charged: $540.20 Developer receives: $500.00 ``` -## Payment security +## Managing funded bounties -### How payment protection works +### Approving work -1. **Funds secured**: When you create a bounty, funds are held securely in escrow -2. **Protected**: Neither party can access funds until work is approved -3. **Released**: Funds transfer instantly upon approval -4. **Refunded**: If bounty is cancelled, funds return to creator minus the 5% platform fee +When you approve a submission: -## Refunds and cancellations +1. Developer receives the full bounty amount instantly +2. Bounty is marked as complete +3. You receive a receipt for your records -### Requesting a refund +### Cancelling and refunds -To cancel a funded bounty and request a refund: +#### Unfunded bounties -1. Click **Request cancellation** from the bounty menu -2. Optionally provide a reason -3. Support team processes your refund manually -4. You'll receive the bounty amount minus the 5% platform fee +Delete them directly—no refund needed since they weren't funded. - - You cannot cancel a bounty that has an approved submission. The solver must be paid. The 5% platform fee is non-refundable. - +#### Funded bounties -### What happens during cancellation +To cancel a funded bounty: -- All pending submitters receive a notification email -- Bounty badge changes from "Funded" to "Cancelling" -- Delete button becomes available while waiting for refund -- Once refunded, bounty status changes to "Cancelled" + + + Click **Request cancellation** from the bounty menu. + + + Help us understand why you're cancelling. + + + Our team processes your refund manually. + + + You'll receive the bounty amount minus the 5% platform fee. + + + + + You cannot cancel a bounty that has an approved submission. Once work is approved, the developer must be paid. The 5% platform fee is non-refundable. + ### Refund calculation @@ -129,38 +113,85 @@ Platform fee (5%): $ 25.00 (non-refundable) Refund amount: $475.00 ``` +### What happens during cancellation + +- All pending submitters receive a notification email +- Bounty badge changes from "Funded" to "Cancelling" +- Delete button becomes available while waiting for refund +- Once refunded, bounty status changes to "Cancelled" + +## Payment security + +### Escrow protection + +1. **Funds secured**: When you fund a bounty, money is held in escrow +2. **Protected**: Neither party can access funds until work is approved +3. **Released**: Funds transfer instantly to the developer upon approval +4. **Refunded**: If cancelled, funds return to you (minus platform fee) + ### Dispute resolution -If there's a disagreement: +If there's a disagreement with a developer: -1. **Communicate**: Try to resolve directly with the other party -2. **Request mediation**: Contact [grim@bounty.new](mailto:grim@bounty.new) -3. **Review process**: Our team reviews the work and requirements -4. **Decision**: Funds released based on fair assessment + + + Try to resolve the issue with the developer first. + + + Contact [grim@bounty.new](mailto:grim@bounty.new) for help. + + + Our team reviews the work and original requirements. + + + Funds are released based on a fair assessment. + + Disputes are rare but taken seriously. Provide clear requirements upfront to avoid issues. +## Best practices + + + + Only share your bounty publicly after it's funded. Unfunded bounties can't accept submissions. + + + Pay market rates for the work required. Higher rewards attract better developers. + + + Approve or provide feedback quickly. Developers appreciate fast turnaround. + + + Detailed requirements reduce disputes and lead to better submissions. + + + ## Troubleshooting - Verify card details are correct - - Check with your bank for blocks + - Check with your bank for blocks or limits - Try an alternative payment method - - Contact support if issue persists - - - - Check your payout method is verified - - ACH bank transfers take 1-2 business days - - Verify bank account details are correct - - Contact [grim@bounty.new](mailto:grim@bounty.new) for help + - Contact [grim@bounty.new](mailto:grim@bounty.new) if issue persists - - Review the fee breakdown in your transaction history - - Platform fee (5%) and payment processing fees apply - - Contact support if you believe there's an error + - Review the fee breakdown: bounty amount + 5% platform fee + card processing + - Check your transaction history for details + - Contact [grim@bounty.new](mailto:grim@bounty.new) if you believe there's an error + + + - Refunds are processed manually and may take 3-5 business days + - Check that your cancellation request was submitted + - Contact [grim@bounty.new](mailto:grim@bounty.new) for status updates + + + - Check if there's an approved submission (cannot cancel if approved) + - Make sure the bounty is funded (unfunded bounties can be deleted directly) + - Contact [grim@bounty.new](mailto:grim@bounty.new) for help @@ -168,4 +199,4 @@ If there's a disagreement: Questions about payments? Our team is here to help. - \ No newline at end of file + From 581c7c8b1b90d67b06f0251d56434169a538e684 Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 13:34:46 -0700 Subject: [PATCH 04/15] Update docs.json Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- docs.json | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs.json b/docs.json index 92e1d9b..99ec815 100644 --- a/docs.json +++ b/docs.json @@ -14,12 +14,19 @@ ], "groups": [ { - "group": "Guides", + "group": "For creators", "pages": [ "guides/creating-bounties", "guides/payments" ] }, + { + "group": "For developers", + "pages": [ + "guides/solving-bounties", + "guides/getting-paid" + ] + }, { "group": "Integrations", "pages": [ From 2ed7d0794862399817d0c42a7ad73df4e3a4ad66 Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 13:34:59 -0700 Subject: [PATCH 05/15] Update guides/creating-bounties.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/creating-bounties.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/guides/creating-bounties.mdx b/guides/creating-bounties.mdx index d50254b..0d46b72 100644 --- a/guides/creating-bounties.mdx +++ b/guides/creating-bounties.mdx @@ -225,10 +225,10 @@ For funded bounties, you must request cancellation: ## Next steps - + Connect your favorite platforms. - - Configure payouts and billing. + + Learn about payment methods and fees. \ No newline at end of file From 3dde66b08b39269ec35568fe1a2019465ef6c5aa Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 14:03:55 -0700 Subject: [PATCH 06/15] Update guides/payments.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/payments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/payments.mdx b/guides/payments.mdx index 5022bc6..fec44fc 100644 --- a/guides/payments.mdx +++ b/guides/payments.mdx @@ -14,7 +14,7 @@ Fund your bounties with a credit card and let bounty.new handle the rest. When y Set up your bounty with a clear description and reward amount. - Pay upfront with a credit card. Funds are held in escrow. + Pay upfront with a credit card. Funds are held securely until work is approved. Developers submit solutions. You review and test their work. From e94d579c447754b949a17a0039a2d538cf8a441b Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 14:04:01 -0700 Subject: [PATCH 07/15] Update guides/payments.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/payments.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/payments.mdx b/guides/payments.mdx index fec44fc..9015f40 100644 --- a/guides/payments.mdx +++ b/guides/payments.mdx @@ -122,9 +122,9 @@ Refund amount: $475.00 ## Payment security -### Escrow protection +### How payment protection works -1. **Funds secured**: When you fund a bounty, money is held in escrow +1. **Funds secured**: When you fund a bounty, money is held securely in our platform account 2. **Protected**: Neither party can access funds until work is approved 3. **Released**: Funds transfer instantly to the developer upon approval 4. **Refunded**: If cancelled, funds return to you (minus platform fee) From 746e3e457ce5dbda3cbebd43d7d76ff3466e9219 Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 14:04:54 -0700 Subject: [PATCH 08/15] Update guides/solving-bounties.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/solving-bounties.mdx | 340 +++++++++++++++++++++--------------- 1 file changed, 199 insertions(+), 141 deletions(-) diff --git a/guides/solving-bounties.mdx b/guides/solving-bounties.mdx index 68ec0af..d7139ca 100644 --- a/guides/solving-bounties.mdx +++ b/guides/solving-bounties.mdx @@ -1,218 +1,276 @@ --- title: "Solving bounties" -description: "How to find, solve, and get paid for bounties fast" +description: "How to find, solve, and get paid for bounties as a developer" --- ## Overview -Bounty.new lets you earn money solving real problems. Find bounties, submit solutions, get approved, and receive instant payment. Here's how to maximize your efficiency. +Get paid for solving real problems. Find bounties, submit your solution, and receive instant payment when approved—no waiting periods, no hassle. -## Before you start +## Quick start - - Go to [bounty.new/settings/payments](https://bounty.new/settings/payments) and connect your Stripe account. You must do this before creators can approve your submissions. + + Browse available bounties on bounty.new or through integrated platforms like GitHub, Discord, or Linear. - - Check the bounty feed or connect your GitHub/Discord to see bounties in your workflow. + + Connect your bank account to receive instant payouts (one-time setup). + + + Build and submit your solution following the bounty requirements. + + + Once approved, funds hit your account immediately. ## Finding bounties -### Where to look +### Browse on bounty.new -- **Bounty.new dashboard**: Browse all open bounties -- **GitHub**: Look for issues with bounty labels in repos you follow -- **Discord**: Check servers with the bounty.new bot installed -- **Linear**: Some teams create bounties from Linear issues +Visit [bounty.new](https://bounty.new) to see all available bounties. Filter by: -### Filtering for the right bounties +- **Reward amount**: Find bounties that match your rate +- **Technology**: Filter by languages and frameworks +- **Difficulty**: Choose based on your skill level +- **Deadline**: Pick bounties that fit your schedule -Look for: +### Through integrations -- **Clear requirements**: Well-defined scope and acceptance criteria -- **Fair reward**: Payment matches the complexity and time required -- **Reasonable deadline**: Enough time to do quality work -- **Responsive creator**: Check if they answer questions quickly +Bounties appear where you already work: - - Start with smaller bounties ($100-$500) to build reputation, then move to larger ones. - +- **GitHub**: Look for issues with the bounty.new badge +- **Discord**: Use `/bounty list` to see available bounties +- **Linear**: Bounties sync from connected GitHub repos -## Solving bounties fast +## Setting up payouts -### 1. Understand the requirements +Before you can receive payment, you need to connect your bank account through Stripe Connect. This is a one-time setup that takes about 2 minutes. - - - Read the full description, acceptance criteria, and any linked docs before starting. - - - If anything is unclear, ask immediately. Don't waste time guessing. - - - Look at the codebase, related PRs, and issues to understand context. - - - Make sure you understand exactly what "done" looks like before coding. - - +### Step 1: Click on a bounty -### 2. Plan your approach +When you click on any bounty, you'll see a button to start the payout setup process. -- **Break it down**: Split the work into smaller tasks -- **Estimate time**: Be realistic about how long it'll take -- **Check dependencies**: Make sure you have access to everything you need -- **Set up environment**: Get the project running locally first + + Click on bounty to start setup + -### 3. Execute efficiently + + **Screenshot placeholder**: Shows the bounty card with a clear call-to-action button to begin the Stripe Connect flow. + - - - Build the main functionality first, polish later. - - - Don't wait until the end to test. Catch issues early. - - - Match the existing code style and conventions. - - - Add comments, update docs, explain your approach. - - +### Step 2: Start Stripe Connect setup + +You'll be redirected to Stripe Connect to securely link your bank account. + + + Stripe Connect setup step 1 + + + + **Screenshot placeholder**: Shows the initial Stripe Connect screen where users enter their basic information. + + +### Step 3: Enter your bank details + +Provide your bank account information. Stripe uses this to send your payouts. + + + Enter bank account details + + + + **What to enter**: Use your checking account routing and account numbers. You can find these on a check or in your online banking portal. + + + + **Screenshot placeholder**: Shows the bank details form with annotations pointing to where users should enter routing number and account number. + -### 4. Submit quality work +### Step 4: Complete verification -Your submission should include: +Submit your information and complete any additional verification steps Stripe requires. -- **Working code**: Tested and functional -- **Tests**: Unit tests or proof it works -- **Documentation**: README updates, inline comments -- **Clean commits**: Clear commit messages -- **Demo**: Screenshots, video, or live link if applicable + + Submit and verify + + + + **Screenshot placeholder**: Shows the final submission screen and what users see when verification is complete. + + +### What if you're missing information? + +If you try to submit a solution before completing your payout setup, you'll see a clear message on the bounty page. + + + Missing payout information warning + - Don't submit half-finished work. Creators want solutions they can merge immediately. + You must complete Stripe Connect setup before you can submit solutions or receive payments. + + **Screenshot placeholder**: Shows the warning message that appears on bounty pages when payout information is incomplete, with a button to complete setup. + + ## Submitting your solution -### On GitHub +### Before you start + + + Read the bounty requirements carefully + + + + Check the deadline and make sure you have time + + + + Review any linked documentation or specs + + + + Ask questions if anything is unclear + + +### Building your solution + +Follow these best practices: + +- **Meet all requirements**: Don't skip any listed criteria +- **Write clean code**: Follow the project's style guide +- **Test thoroughly**: Make sure everything works +- **Document your work**: Add comments and update docs if needed + +### Submitting on GitHub + +For GitHub-based bounties: 1. Fork the repository -2. Create a feature branch +2. Create a new branch for your work 3. Make your changes 4. Open a pull request -5. Reference the bounty in your PR description +5. Reference the bounty issue with "Closes #123" or "Fixes #123" + +The bounty.new bot will automatically detect your submission. + +### Submitting on Discord + +For Discord bounties: -### On bounty.new dashboard +``` +/bounty submit [bounty_id] [your_solution_link] +``` -1. Navigate to the bounty +Include a link to your work (GitHub PR, demo, or deliverable). + +### Submitting on bounty.new + +1. Navigate to the bounty page 2. Click **Submit solution** -3. Provide your GitHub PR link or deliverable -4. Add notes explaining your approach +3. Provide a link to your work +4. Add any notes or context 5. Click **Submit** -### What happens next +## Getting paid - - - They'll test your solution and provide feedback. - - - Address any feedback quickly to stay competitive. - - - Once approved, payment processes instantly. - - - Funds hit your Stripe account immediately—no waiting. - - +### Instant payouts -## Getting paid +When the bounty creator approves your submission: -### Payment timeline +- Funds transfer to your bank account immediately +- You receive an email confirmation +- Payment appears in your Stripe dashboard +- Bounty is marked as complete -- **Instant**: Payment processes the moment your submission is approved -- **No fees**: You keep 100% of the bounty amount -- **Direct deposit**: Funds go straight to your connected Stripe account + + **No waiting period**: Unlike other platforms, you get paid the moment your work is approved. No 30-day holds or manual processing. + -### Payout methods +### Payment timeline -Connect your Stripe account at [bounty.new/settings/payments](https://bounty.new/settings/payments): +| Event | Timing | +| ----- | ------ | +| Submission approved | Instant | +| Funds sent to your bank | Instant | +| Funds available in your account | 1-2 business days (standard ACH) | -- **Bank transfer**: Direct deposit to your bank account -- **Instant access**: No waiting periods or holds -- **Secure**: All payments processed through Stripe +### Tracking your earnings - - Make sure your Stripe account is fully verified to avoid payout delays. - +View all your payouts in your bounty.new dashboard: -## Tips for success +- Total earnings +- Pending submissions +- Completed bounties +- Payment history -### Maximize your earnings +## Tips for success - - First quality submission often wins. Speed matters. + + Build your reputation with smaller bounties before tackling complex ones. - - Keep the creator updated. Show progress, ask questions. + + Ask questions upfront to avoid wasted effort on the wrong solution. - - Go slightly beyond requirements. Add tests, docs, polish. + + High-quality submissions lead to more approvals and better reputation. - - Deliver consistently to get invited to private bounties. + + Deliver on time to build trust with bounty creators. -### Common mistakes to avoid +## Common questions -- **Starting without clarification**: Always confirm requirements first -- **Submitting incomplete work**: Only submit when it's truly done -- **Ignoring code style**: Match the existing patterns -- **Missing tests**: Include tests unless explicitly not required -- **Poor communication**: Update the creator on your progress + + + Check the bounty status badge. "Open" means it's accepting submissions. "Completed" means someone already won. + + + Yes! Work on as many bounties as you can handle. Just make sure you can deliver quality work for each. + + + The creator should provide feedback. You can revise and resubmit if the bounty is still open. + + + Payment is instant when approved. Funds typically appear in your bank account within 1-2 business days via ACH. + + + Go to your account settings and update your Stripe Connect information. Changes take effect immediately. + + + Yes, but only one person can submit and receive payment. Coordinate with your team on how to split the reward. + + ## Troubleshooting - - - Make sure you're using a supported country - - Verify your identity with Stripe + + - Verify your Stripe Connect setup is complete + - Check that the bounty is still open + - Make sure you're logged in - Contact [grim@bounty.new](mailto:grim@bounty.new) if issues persist - - - Read the feedback carefully - - Ask specific questions about what needs to change - - Revise and resubmit quickly - - Don't take it personally—iterate and improve - - - Check that your Stripe account is verified - - Bank transfers can take 1-2 business days - - Verify your bank details are correct + - Check your Stripe dashboard for payout status + - Verify your bank account details are correct + - ACH transfers take 1-2 business days - Contact [grim@bounty.new](mailto:grim@bounty.new) for help - - - Reach out to the creator to understand why - - If you've done significant work, discuss compensation - - Move on to the next bounty—don't dwell on it + + - Refresh the bounty page + - Check that you submitted to the correct bounty + - Verify your submission link is accessible + - Contact [grim@bounty.new](mailto:grim@bounty.new) if it's still missing -## Next steps +## Need help? - - - Connect GitHub, Discord, or Linear to find bounties faster. - - - Configure your Stripe account and payout preferences. - - + + Questions about solving bounties or getting paid? We're here to help. + From 4cd919a204b8e925123e1df0075eb1f513e54a7e Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 14:05:34 -0700 Subject: [PATCH 09/15] Update guides/funding-bounties.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/funding-bounties.mdx | 202 ++++++++++++++++++++++++++++++++++++ 1 file changed, 202 insertions(+) create mode 100644 guides/funding-bounties.mdx diff --git a/guides/funding-bounties.mdx b/guides/funding-bounties.mdx new file mode 100644 index 0000000..9015f40 --- /dev/null +++ b/guides/funding-bounties.mdx @@ -0,0 +1,202 @@ +--- +title: "Funding bounties" +description: "How to fund bounties and manage payments as a creator" +--- + +## Overview + +Fund your bounties with a credit card and let bounty.new handle the rest. When you approve a submission, the developer gets paid instantly—no manual transfers, no hassle. + +## How it works + + + + Set up your bounty with a clear description and reward amount. + + + Pay upfront with a credit card. Funds are held securely until work is approved. + + + Developers submit solutions. You review and test their work. + + + When you approve a submission, the developer gets paid instantly. + + + +## Payment methods + +### Funding bounties + +- **Credit card**: Visa, Mastercard, American Express +- **Instant processing**: Your bounty goes live immediately +- **Secure**: All payments processed through Stripe + + + Bounties must be funded upfront. This ensures developers get paid immediately when their work is approved. + + +## Fees and pricing + +### Platform fees + +| Fee type | Amount | When charged | +| ----------------- | ----------- | ---------------------- | +| Platform fee | 5% | When bounty is created | +| Card processing | 2.9% + $0.30| When bounty is created | + + + Developers receive 100% of the bounty amount. You pay the platform fee and processing fees upfront. + + +### Example calculation + +For a $500 bounty: + +``` +Bounty amount: $500.00 +Platform fee (5%): $ 25.00 +Card processing: $ 15.20 +───────────────────────────── +Total charged: $540.20 + +Developer receives: $500.00 +``` + +## Managing funded bounties + +### Approving work + +When you approve a submission: + +1. Developer receives the full bounty amount instantly +2. Bounty is marked as complete +3. You receive a receipt for your records + +### Cancelling and refunds + +#### Unfunded bounties + +Delete them directly—no refund needed since they weren't funded. + +#### Funded bounties + +To cancel a funded bounty: + + + + Click **Request cancellation** from the bounty menu. + + + Help us understand why you're cancelling. + + + Our team processes your refund manually. + + + You'll receive the bounty amount minus the 5% platform fee. + + + + + You cannot cancel a bounty that has an approved submission. Once work is approved, the developer must be paid. The 5% platform fee is non-refundable. + + +### Refund calculation + +For a $500 bounty: + +``` +Original amount: $500.00 +Platform fee (5%): $ 25.00 (non-refundable) +───────────────────────────── +Refund amount: $475.00 +``` + +### What happens during cancellation + +- All pending submitters receive a notification email +- Bounty badge changes from "Funded" to "Cancelling" +- Delete button becomes available while waiting for refund +- Once refunded, bounty status changes to "Cancelled" + +## Payment security + +### How payment protection works + +1. **Funds secured**: When you fund a bounty, money is held securely in our platform account +2. **Protected**: Neither party can access funds until work is approved +3. **Released**: Funds transfer instantly to the developer upon approval +4. **Refunded**: If cancelled, funds return to you (minus platform fee) + +### Dispute resolution + +If there's a disagreement with a developer: + + + + Try to resolve the issue with the developer first. + + + Contact [grim@bounty.new](mailto:grim@bounty.new) for help. + + + Our team reviews the work and original requirements. + + + Funds are released based on a fair assessment. + + + + + Disputes are rare but taken seriously. Provide clear requirements upfront to avoid issues. + + +## Best practices + + + + Only share your bounty publicly after it's funded. Unfunded bounties can't accept submissions. + + + Pay market rates for the work required. Higher rewards attract better developers. + + + Approve or provide feedback quickly. Developers appreciate fast turnaround. + + + Detailed requirements reduce disputes and lead to better submissions. + + + +## Troubleshooting + + + + - Verify card details are correct + - Check with your bank for blocks or limits + - Try an alternative payment method + - Contact [grim@bounty.new](mailto:grim@bounty.new) if issue persists + + + - Review the fee breakdown: bounty amount + 5% platform fee + card processing + - Check your transaction history for details + - Contact [grim@bounty.new](mailto:grim@bounty.new) if you believe there's an error + + + - Refunds are processed manually and may take 3-5 business days + - Check that your cancellation request was submitted + - Contact [grim@bounty.new](mailto:grim@bounty.new) for status updates + + + - Check if there's an approved submission (cannot cancel if approved) + - Make sure the bounty is funded (unfunded bounties can be deleted directly) + - Contact [grim@bounty.new](mailto:grim@bounty.new) for help + + + +## Need help? + + + Questions about payments? Our team is here to help. + From c7684a59bacc2982dfe6d461a40ea049b2751fb3 Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 14:05:38 -0700 Subject: [PATCH 10/15] Delete guides/payments.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/payments.mdx | 202 -------------------------------------------- 1 file changed, 202 deletions(-) delete mode 100644 guides/payments.mdx diff --git a/guides/payments.mdx b/guides/payments.mdx deleted file mode 100644 index 9015f40..0000000 --- a/guides/payments.mdx +++ /dev/null @@ -1,202 +0,0 @@ ---- -title: "Funding bounties" -description: "How to fund bounties and manage payments as a creator" ---- - -## Overview - -Fund your bounties with a credit card and let bounty.new handle the rest. When you approve a submission, the developer gets paid instantly—no manual transfers, no hassle. - -## How it works - - - - Set up your bounty with a clear description and reward amount. - - - Pay upfront with a credit card. Funds are held securely until work is approved. - - - Developers submit solutions. You review and test their work. - - - When you approve a submission, the developer gets paid instantly. - - - -## Payment methods - -### Funding bounties - -- **Credit card**: Visa, Mastercard, American Express -- **Instant processing**: Your bounty goes live immediately -- **Secure**: All payments processed through Stripe - - - Bounties must be funded upfront. This ensures developers get paid immediately when their work is approved. - - -## Fees and pricing - -### Platform fees - -| Fee type | Amount | When charged | -| ----------------- | ----------- | ---------------------- | -| Platform fee | 5% | When bounty is created | -| Card processing | 2.9% + $0.30| When bounty is created | - - - Developers receive 100% of the bounty amount. You pay the platform fee and processing fees upfront. - - -### Example calculation - -For a $500 bounty: - -``` -Bounty amount: $500.00 -Platform fee (5%): $ 25.00 -Card processing: $ 15.20 -───────────────────────────── -Total charged: $540.20 - -Developer receives: $500.00 -``` - -## Managing funded bounties - -### Approving work - -When you approve a submission: - -1. Developer receives the full bounty amount instantly -2. Bounty is marked as complete -3. You receive a receipt for your records - -### Cancelling and refunds - -#### Unfunded bounties - -Delete them directly—no refund needed since they weren't funded. - -#### Funded bounties - -To cancel a funded bounty: - - - - Click **Request cancellation** from the bounty menu. - - - Help us understand why you're cancelling. - - - Our team processes your refund manually. - - - You'll receive the bounty amount minus the 5% platform fee. - - - - - You cannot cancel a bounty that has an approved submission. Once work is approved, the developer must be paid. The 5% platform fee is non-refundable. - - -### Refund calculation - -For a $500 bounty: - -``` -Original amount: $500.00 -Platform fee (5%): $ 25.00 (non-refundable) -───────────────────────────── -Refund amount: $475.00 -``` - -### What happens during cancellation - -- All pending submitters receive a notification email -- Bounty badge changes from "Funded" to "Cancelling" -- Delete button becomes available while waiting for refund -- Once refunded, bounty status changes to "Cancelled" - -## Payment security - -### How payment protection works - -1. **Funds secured**: When you fund a bounty, money is held securely in our platform account -2. **Protected**: Neither party can access funds until work is approved -3. **Released**: Funds transfer instantly to the developer upon approval -4. **Refunded**: If cancelled, funds return to you (minus platform fee) - -### Dispute resolution - -If there's a disagreement with a developer: - - - - Try to resolve the issue with the developer first. - - - Contact [grim@bounty.new](mailto:grim@bounty.new) for help. - - - Our team reviews the work and original requirements. - - - Funds are released based on a fair assessment. - - - - - Disputes are rare but taken seriously. Provide clear requirements upfront to avoid issues. - - -## Best practices - - - - Only share your bounty publicly after it's funded. Unfunded bounties can't accept submissions. - - - Pay market rates for the work required. Higher rewards attract better developers. - - - Approve or provide feedback quickly. Developers appreciate fast turnaround. - - - Detailed requirements reduce disputes and lead to better submissions. - - - -## Troubleshooting - - - - - Verify card details are correct - - Check with your bank for blocks or limits - - Try an alternative payment method - - Contact [grim@bounty.new](mailto:grim@bounty.new) if issue persists - - - - Review the fee breakdown: bounty amount + 5% platform fee + card processing - - Check your transaction history for details - - Contact [grim@bounty.new](mailto:grim@bounty.new) if you believe there's an error - - - - Refunds are processed manually and may take 3-5 business days - - Check that your cancellation request was submitted - - Contact [grim@bounty.new](mailto:grim@bounty.new) for status updates - - - - Check if there's an approved submission (cannot cancel if approved) - - Make sure the bounty is funded (unfunded bounties can be deleted directly) - - Contact [grim@bounty.new](mailto:grim@bounty.new) for help - - - -## Need help? - - - Questions about payments? Our team is here to help. - From ed299098f8ae7776eb87763eb0df1a297e9559da Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 14:05:57 -0700 Subject: [PATCH 11/15] Update docs.json Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- docs.json | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs.json b/docs.json index 99ec815..c1bb7aa 100644 --- a/docs.json +++ b/docs.json @@ -17,14 +17,13 @@ "group": "For creators", "pages": [ "guides/creating-bounties", - "guides/payments" + "guides/funding-bounties" ] }, { "group": "For developers", "pages": [ - "guides/solving-bounties", - "guides/getting-paid" + "guides/solving-bounties" ] }, { From 683bc062afcac881b2014a7155084b379c778edd Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 14:06:03 -0700 Subject: [PATCH 12/15] Update guides/creating-bounties.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/creating-bounties.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/creating-bounties.mdx b/guides/creating-bounties.mdx index 0d46b72..57cb2ba 100644 --- a/guides/creating-bounties.mdx +++ b/guides/creating-bounties.mdx @@ -228,7 +228,7 @@ For funded bounties, you must request cancellation: Connect your favorite platforms. - + Learn about payment methods and fees. \ No newline at end of file From 473830a911c02da370fe91d5eb2c459730a59743 Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 15:15:04 -0700 Subject: [PATCH 13/15] Update index.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- index.mdx | 50 ++++++++++++++++++++++++++++++++++++++------------ 1 file changed, 38 insertions(+), 12 deletions(-) diff --git a/index.mdx b/index.mdx index a89c65a..dbdf96c 100644 --- a/index.mdx +++ b/index.mdx @@ -7,6 +7,44 @@ description: "Bounty.new is the bounty platform where creators post challenges a Bounty.new is the bounty platform where creators post challenges and developers deliver solutions. Instant payouts, seamless integration, zero friction. +## For creators + +Post bounties, fund them upfront, and get solutions fast. + + + + Learn how to post bounties from GitHub, Discord, Linear, or the dashboard. + + + Pay upfront with a credit card. Approve work and developers get paid instantly. + + + Create bounties from issues and PRs with a simple comment. + + + Manage bounties directly from your Discord server. + + + +## For developers + +Find bounties, solve them, and get paid instantly. + + + + Find bounties, submit solutions, and receive instant payouts. + + + Check out all open bounties on bounty.new. + + + Connect your bank account to receive payments immediately. + + + Learn how to build your reputation and maximize earnings. + + + ## Why use bounty.new? @@ -27,18 +65,6 @@ Bounty.new is the bounty platform where creators post challenges and developers -## Who is it for? - -* **Creators and project owners** who need specific features built or bugs fixed without hiring full-time. -* **Developers** who want to earn money solving interesting problems on their own schedule. -* **Open source maintainers** who want to incentivize contributions and reward community members. - **Ship fast. Get paid faster.** We're building the simplest way to connect work with rewards. - -## Ready to get started? - - - Follow our guide to post your first bounty and start getting solutions in minutes. - From deaad8bf8a9325018b2f35c5537e2697e2aa3c4f Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 15:15:50 -0700 Subject: [PATCH 14/15] Update guides/solving-bounties.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/solving-bounties.mdx | 107 +++++++++++++----------------------- 1 file changed, 39 insertions(+), 68 deletions(-) diff --git a/guides/solving-bounties.mdx b/guides/solving-bounties.mdx index d7139ca..cd726d6 100644 --- a/guides/solving-bounties.mdx +++ b/guides/solving-bounties.mdx @@ -11,10 +11,10 @@ Get paid for solving real problems. Find bounties, submit your solution, and rec - Browse available bounties on bounty.new or through integrated platforms like GitHub, Discord, or Linear. + Browse available bounties on [bounty.new](https://bounty.new) or through GitHub, Discord, or Linear. - - Connect your bank account to receive instant payouts (one-time setup). + + Connect your bank account via Stripe Connect to receive instant payouts. Takes 2 minutes. Build and submit your solution following the bounty requirements. @@ -45,76 +45,24 @@ Bounties appear where you already work: ## Setting up payouts -Before you can receive payment, you need to connect your bank account through Stripe Connect. This is a one-time setup that takes about 2 minutes. +Before you can receive payment, connect your bank account through Stripe Connect. This is a one-time setup. -### Step 1: Click on a bounty - -When you click on any bounty, you'll see a button to start the payout setup process. - - - Click on bounty to start setup - - - - **Screenshot placeholder**: Shows the bounty card with a clear call-to-action button to begin the Stripe Connect flow. - - -### Step 2: Start Stripe Connect setup - -You'll be redirected to Stripe Connect to securely link your bank account. - - - Stripe Connect setup step 1 - - - - **Screenshot placeholder**: Shows the initial Stripe Connect screen where users enter their basic information. - - -### Step 3: Enter your bank details - -Provide your bank account information. Stripe uses this to send your payouts. - - - Enter bank account details - + + + You'll see a prompt to set up payouts if you haven't already. + + + Enter your bank account details securely through Stripe. + + + Once verified, you can submit solutions and receive instant payouts. + + - **What to enter**: Use your checking account routing and account numbers. You can find these on a check or in your online banking portal. + **One-time setup**: You only need to do this once. After that, all future payouts are automatic. - - **Screenshot placeholder**: Shows the bank details form with annotations pointing to where users should enter routing number and account number. - - -### Step 4: Complete verification - -Submit your information and complete any additional verification steps Stripe requires. - - - Submit and verify - - - - **Screenshot placeholder**: Shows the final submission screen and what users see when verification is complete. - - -### What if you're missing information? - -If you try to submit a solution before completing your payout setup, you'll see a clear message on the bounty page. - - - Missing payout information warning - - - - You must complete Stripe Connect setup before you can submit solutions or receive payments. - - - - **Screenshot placeholder**: Shows the warning message that appears on bounty pages when payout information is incomplete, with a button to complete setup. - - ## Submitting your solution ### Before you start @@ -223,6 +171,29 @@ View all your payouts in your bounty.new dashboard: +## Speed tips + +Want to solve bounties faster? Here's how: + + + + Have your dev environment ready to go. Clone repos quickly, run tests fast. + + + Spend 5 minutes understanding requirements to save hours of rework. + + + Don't wait. If something's unclear, ask the creator right away. + + + Get feedback on your approach before completing all the work. + + + + + **Pro tip**: Focus on bounties in your tech stack. You'll solve them faster and produce better work. + + ## Common questions From d2ceead46760d9c6f0a79ba49efbe416a2947616 Mon Sep 17 00:00:00 2001 From: grim <75869731+ripgrim@users.noreply.github.com> Date: Tue, 10 Mar 2026 15:30:00 -0700 Subject: [PATCH 15/15] Update guides/solving-bounties.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/solving-bounties.mdx | 267 +++++++++++------------------------- 1 file changed, 77 insertions(+), 190 deletions(-) diff --git a/guides/solving-bounties.mdx b/guides/solving-bounties.mdx index cd726d6..35d26e3 100644 --- a/guides/solving-bounties.mdx +++ b/guides/solving-bounties.mdx @@ -1,247 +1,134 @@ --- title: "Solving bounties" -description: "How to find, solve, and get paid for bounties as a developer" +description: "Find bounties, deliver solutions, and get paid instantly." --- -## Overview +# Solving bounties -Get paid for solving real problems. Find bounties, submit your solution, and receive instant payment when approved—no waiting periods, no hassle. +Get paid for solving real problems. Here's how to find bounties, deliver quality solutions, and maximize your earnings. ## Quick start - Browse available bounties on [bounty.new](https://bounty.new) or through GitHub, Discord, or Linear. + Browse available bounties on bounty.new or get notified through Discord, Slack, or GitHub integrations. - - Connect your bank account via Stripe Connect to receive instant payouts. Takes 2 minutes. - - - Build and submit your solution following the bounty requirements. - - - Once approved, funds hit your account immediately. - - - -## Finding bounties - -### Browse on bounty.new - -Visit [bounty.new](https://bounty.new) to see all available bounties. Filter by: -- **Reward amount**: Find bounties that match your rate -- **Technology**: Filter by languages and frameworks -- **Difficulty**: Choose based on your skill level -- **Deadline**: Pick bounties that fit your schedule - -### Through integrations - -Bounties appear where you already work: - -- **GitHub**: Look for issues with the bounty.new badge -- **Discord**: Use `/bounty list` to see available bounties -- **Linear**: Bounties sync from connected GitHub repos - -## Setting up payouts - -Before you can receive payment, connect your bank account through Stripe Connect. This is a one-time setup. - - - - You'll see a prompt to set up payouts if you haven't already. + + Click **Claim bounty** to let the creator know you're working on it. This prevents duplicate work. - - Enter your bank account details securely through Stripe. + + + Submit your work through the platform. Include clear documentation and testing evidence. - - Once verified, you can submit solutions and receive instant payouts. + + + Once approved, funds hit your account immediately. No waiting periods. - - **One-time setup**: You only need to do this once. After that, all future payouts are automatic. - - -## Submitting your solution - -### Before you start - - - Read the bounty requirements carefully - +## Tips for success - - Check the deadline and make sure you have time - + + + Understand exactly what's needed before claiming. Ask questions early if anything is unclear. + - - Review any linked documentation or specs - + + Keep the creator updated. Quick status updates build trust and prevent miscommunication. + - - Ask questions if anything is unclear - + + Verify your solution works as expected. Include screenshots, videos, or test results with your submission. + -### Building your solution + + Clear documentation makes approval faster. Explain what you built and how to use it. + + -Follow these best practices: +## Finding the right bounties -- **Meet all requirements**: Don't skip any listed criteria -- **Write clean code**: Follow the project's style guide -- **Test thoroughly**: Make sure everything works -- **Document your work**: Add comments and update docs if needed +### Match your skills -### Submitting on GitHub +Focus on bounties that align with your expertise. You'll deliver faster and produce better work. -For GitHub-based bounties: +### Check the requirements -1. Fork the repository -2. Create a new branch for your work -3. Make your changes -4. Open a pull request -5. Reference the bounty issue with "Closes #123" or "Fixes #123" +Look for: +- **Clear scope**: Well-defined requirements are easier to fulfill +- **Fair compensation**: Make sure the payout matches the effort required +- **Reasonable timeline**: Can you realistically deliver within the deadline? -The bounty.new bot will automatically detect your submission. +### Start small -### Submitting on Discord +Build reputation with smaller bounties before tackling complex ones. Creators are more likely to approve work from developers with a track record. -For Discord bounties: +## Delivering quality work -``` -/bounty submit [bounty_id] [your_solution_link] -``` +### Before you submit -Include a link to your work (GitHub PR, demo, or deliverable). +- [ ] Solution meets all stated requirements +- [ ] Code is clean and well-commented +- [ ] Tests pass (if applicable) +- [ ] Documentation is clear +- [ ] You've tested edge cases -### Submitting on bounty.new +### Submission best practices -1. Navigate to the bounty page -2. Click **Submit solution** -3. Provide a link to your work -4. Add any notes or context -5. Click **Submit** +1. **Show your work**: Include screenshots, videos, or live demos +2. **Explain your approach**: Brief overview of how you solved the problem +3. **Highlight key features**: Point out important aspects of your solution +4. **Provide next steps**: If relevant, suggest improvements or future enhancements ## Getting paid -### Instant payouts - -When the bounty creator approves your submission: - -- Funds transfer to your bank account immediately -- You receive an email confirmation -- Payment appears in your Stripe dashboard -- Bounty is marked as complete +### Payout methods - - **No waiting period**: Unlike other platforms, you get paid the moment your work is approved. No 30-day holds or manual processing. - +Set up your payout method in your account settings: +- **Bank account (ACH)**: 1-2 business day transfers +- **Debit card**: Instant payouts -### Payment timeline +### After approval -| Event | Timing | -| ----- | ------ | -| Submission approved | Instant | -| Funds sent to your bank | Instant | -| Funds available in your account | 1-2 business days (standard ACH) | +Funds are released immediately when the creator approves your work. No holds, no delays. -### Tracking your earnings +### If there's an issue -View all your payouts in your bounty.new dashboard: +If a creator requests changes: +1. Review their feedback carefully +2. Make the requested updates +3. Resubmit with notes on what you changed -- Total earnings -- Pending submissions -- Completed bounties -- Payment history - -## Tips for success - - - - Build your reputation with smaller bounties before tackling complex ones. - - - Ask questions upfront to avoid wasted effort on the wrong solution. - - - High-quality submissions lead to more approvals and better reputation. - - - Deliver on time to build trust with bounty creators. - - - -## Speed tips - -Want to solve bounties faster? Here's how: - - - - Have your dev environment ready to go. Clone repos quickly, run tests fast. - - - Spend 5 minutes understanding requirements to save hours of rework. - - - Don't wait. If something's unclear, ask the creator right away. - - - Get feedback on your approach before completing all the work. - - - - - **Pro tip**: Focus on bounties in your tech stack. You'll solve them faster and produce better work. - + + **Pro tip**: Most disputes come from unclear requirements. When in doubt, over-communicate before you start coding. + ## Common questions - - Check the bounty status badge. "Open" means it's accepting submissions. "Completed" means someone already won. - - - Yes! Work on as many bounties as you can handle. Just make sure you can deliver quality work for each. - - - The creator should provide feedback. You can revise and resubmit if the bounty is still open. - - - Payment is instant when approved. Funds typically appear in your bank account within 1-2 business days via ACH. + + Yes! Claim as many as you can handle, but be realistic about your capacity. It's better to deliver one great solution than multiple rushed ones. - - Go to your account settings and update your Stripe Connect information. Changes take effect immediately. - - - Yes, but only one person can submit and receive payment. Coordinate with your team on how to split the reward. - - - -## Troubleshooting - - - - Verify your Stripe Connect setup is complete - - Check that the bounty is still open - - Make sure you're logged in - - Contact [grim@bounty.new](mailto:grim@bounty.new) if issues persist + + Unclaim it as soon as possible so other developers can take it. Your reputation stays intact if you communicate early. - - - Check your Stripe dashboard for payout status - - Verify your bank account details are correct - - ACH transfers take 1-2 business days - - Contact [grim@bounty.new](mailto:grim@bounty.new) for help + + + - Deliver quality work on time + - Communicate clearly and promptly + - Be responsive to feedback + - Start with smaller bounties and work your way up - - - Refresh the bounty page - - Check that you submitted to the correct bounty - - Verify your submission link is accessible - - Contact [grim@bounty.new](mailto:grim@bounty.new) if it's still missing + + + Ask questions before claiming. Use comments or direct messages to clarify scope, expectations, and acceptance criteria. ## Need help? - Questions about solving bounties or getting paid? We're here to help. + Questions about solving bounties? We're here to help.