Lightning Bounties Documentation
Need Help? Join Our Discord!
  • 📖Lightning Bounties | Docs
  • Getting started
    • FIRST TIME ONBORDING
      • GitHub Auth & Lightning Bounties
    • SOLVING A BOUNTY
      • Finding Bounties to Solve
      • Working on a Bounty
      • Claiming Multiple Bounties: Multi-Bounty PRs
      • Claim Reward Criteria & Troubleshooting Guide
      • Withdrawing Funds
      • Working on Opensource Frontend: lb-next
      • How to Convert Sats into Local Currencies
    • POSTING A BOUNTY
      • Deposit Funds
      • Create a GitHub issue and Submit a new reward
    • MANAGING YOUR BOUNTY
      • Issue Lock Time
      • Add Reward to an Existing Bounty
      • Detach Issues from Pull Requests
      • Expire or Reclaim a Bounty Reward
      • User Balances Overview
  • ABOUT LIGHTNING BOUNTIES
    • Mission
    • Goals
    • Values
    • Features
    • Why Choose Lightning Bounties?
    • Lightning Bounties Team
  • Resources
    • Frequently Asked Questions
      • Lightning Bounties FAQ's
      • Lightning Network FAQ's
    • Glossary of Terms
      • Bitcoin & Lightning Terms
      • Lightning Bounties Terms
      • GitHub Terms
    • Social Media Channels
      • Website
      • Bounty Platform
      • Docs
      • Blog
      • Discord
      • GitHub
      • Twitter
      • Nostr
      • LinkedIn
      • YouTube
    • External resources
      • Satoshi in Bitcoin: What It Is and How Much It Is Worth
      • Use Lightning Network
      • GitHub issues
  • Contributing
  • LICENSE.md
  • CODE_OF_CONDUCT
Powered by GitBook
On this page
  • Claim Reward Criteria
  • 1. Register and Log In with GitHub
  • 2. Find an Issue
  • 3. Fix the Issue
  • 4. Create a Pull Request (PR) Targeting Main/Master
  • 5. Wait for Maintainer to Merge the PR
  • 6. Claim Reward Process
  • Complete Claim Process Visualization
  • Troubleshooting
  • Issue Not Linked to PR
  • Solutions:
  • 1. Edit PR Description
  • 2. Ask Repository Owner (If you can't edit the PR)
  • 3. Create a Follow-up PR (If original PR was already merged)
  • 4. Request an Override via Discord
  • Best Practices

Was this helpful?

Edit on GitHub
Export as PDF
  1. Getting started
  2. SOLVING A BOUNTY

Claim Reward Criteria & Troubleshooting Guide

This guide outlines the complete process for claiming rewards and provides troubleshooting steps for developers working on the Lightning Bounties Platform.

PreviousClaiming Multiple Bounties: Multi-Bounty PRsNextWithdrawing Funds

Last updated 9 days ago

Was this helpful?

Claim Reward Criteria

To successfully claim a reward for a bounty, follow these steps:

1. Register and Log In with GitHub

VERY Important

It’s essential to register and log in to Lightning Bounties using your GitHub account before submitting your PR and clicking "Claim Reward."

  • This ensures your reward is properly linked to your account and that you’re eligible to claim the bounty.

    • See FIRST TIME ONBORDING For Detailed Instructions.

2. Find an Issue

  • Browse available bounties on the feed

  • Review the issue details, requirements, and reward amount

  • Check if the bounty is still available (not claimed by someone else)

    • See Finding Bounties to Solve For Detailed Instructions.

3. Fix the Issue

  • Fork the repository to your GitHub account

  • Clone your fork locally and create a branch for your work

  • Implement the fix according to the issue requirements

  • Test your changes thoroughly to ensure they meet all acceptance criteria

  • Push your changes to your fork

    • See Working on a Bounty For Detailed Instructions.

4. Create a Pull Request (PR) Targeting Main/Master

  • Go to the original repository on GitHub.

  • Click "Compare & pull request" for your branch.

In the PR description, include close #issue-number or closes #issue-number to link the PR to the issue.

GitHub only recognizes linked issues when the PR targets the repository's default branch (usually main or master).

  • Provide a clear explanation of your changes and how they address the issue.

  • You can include as much additional information as needed in your PR description.

  • Submit the PR for review

Screenshot Example:

You may need to refresh the GitHub page to see the issue show up as linked.

5. Wait for Maintainer to Merge the PR

  • The repository maintainer will review your PR.

    • Once it is approved and merged, the issue will be closed automatically if you used the correct closesyntax.

      • See Working on a Bounty For Detailed Instructions.

6. Claim Reward Process

  • Manually claim your reward:

    • Click the "Claim Reward" button

    • Click the "Check" button to verify your eligibility

The reward process will not start automatically.

Once your PR is merged and your eligibility is verified, the reward will be deposited directly into your Lightning Bounties balance.


Complete Claim Process Visualization


Troubleshooting

If you encounter issues claiming your Lightning Bounty reward, use this guide to diagnose and resolve common problems.


Issue Not Linked to PR

Problem Indicators:

  • The PR does not show the linked issue in the GitHub interface.

  • The issue remains open after your PR is merged.

  • The reward does not process automatically.

Solutions:

1. Edit PR Description

If your PR is still open, you can update the PR description to add the correct closing keyword (e.g., close #issue-number).

  • Navigate to your pull request on GitHub.

  • Near the top of the PR page, locate the description section (below the title).

  • Hover over the description area and click the "Edit" (... or pencil) icon.

  • Add the close #issue-numberkeyword at the top of the PR description (not in a comment or commit message, as only the PR body triggers the automation for Lightning Bounties and GitHub).

2. Ask Repository Owner (If you can't edit the PR)

  • Contact the repository owner or maintainer

  • Ask them to edit the PR description to add the closing keyword

3. Create a Follow-up PR (If original PR was already merged)

  • Create a new PR with a minimal change (e.g., update documentation, add a comment, or fix a typo).

  • In the PR description, include the appropriate closing keyword (e.g., close #42).

  • Reference your original PR:

    close #42  
    This PR references the work completed in #123 (original PR).
  • Notify the repository owner about this follow-up PR and explain its purpose.

  • Once merged, return to Lightning Bounties and click "Claim Reward" and "Check."

4. Request an Override via Discord

  • Add a comment to the PR, tagging the maintainer (e.g., @maintainer) and include the Lightning Bounties issue URL.

  • Ask the maintainer to respond in the PR thread confirming that the PR qualifies for the bounty.

The maintainer must write a clear comment confirming the qualification (an emoji or reaction is not sufficient as proof).

Payment Not Received

Verification Steps:

  1. Confirm the issue is marked as "closed" on GitHub

  2. Verify the PR that closed it has been merged

  3. Check that you clicked "Claim Reward" on Lightning Bounties

Solutions:

  • Verify Wallet Setup: Make sure your Lightning Network wallet is correctly configured

Common Errors and Solutions

Error
Description
Solution

Missing link syntax

PR doesn't include close #issue-number

Edit PR description or create follow-up PR

Wrong issue number

PR references incorrect issue

Edit PR or create new PR with correct number

Not claiming reward

Forgot to click "Claim Reward" button

Go to Lightning Bounties app and click button

Issue already claimed

Another dev claimed the bounty first

Check issue status before working on it

Best Practices

  • Always double-check the issue number when adding close #issue-number syntax

  • Communicate clearly with repository maintainers about your bounty claim

  • Keep PRs focused on addressing the specific issue

  • Don't forget to manually click "Claim Reward" on Lightning Bounties platform


The Lightning Bounties system requires both proper GitHub issue linking through the close #issue-number syntax AND manual claiming through the Lightning Bounties platform.

Both steps are essential for successful reward processing

CRITICAL STEP

Why?

INFO

Visit and find the Bounty you solved

IMPORTANT

You must manually complete the claim steps on after your PR is merged.

Complete

For more details, see the and .

If your original PR has already been merged without the correct closing keyword:

Example of a follow-up PR created to properly link the issue for Lightning Bounty payment

If you are unable to resolve the issue through the above steps, join the and request an override from the LB team.

Important

For more details on linking PRs to issues, see .

Check User Balance: Ensure your account balance is updated on

Contact Support: If issues persist, reach out to the Lightning Bounties for assistance

Remember

For additional assistance, join the Lightning Bounties community.

⚠️
⚠️
ℹ️
ℹ️
ℹ️
⚠️
⚠️
🏁
🏁
🔽
⚠️
⚠️
ℹ️
ℹ️
⚠️
⚠️
app.lightningbounties.com
Learn more about linking PRs to issues.
app.lightningbounties.com
app.lightningbounties.com
Lightning Bounties Troubleshooting Guide
GitHub’s official documentation on linking pull requests to issues
Lightning Bounties Discord
GitHub’s guide on linking pull requests to issues
app.lightningbounties.com
Discord
Discord
(see below)
What the Workflow Looks Like
Example: PR description with correct close syntax and branch targeting.
Example: PR description with correct close syntax and branch targeting.
Complete Claim Process
Complete Claim Process
Simplified Workflow
Simplified Workflow
Example: PR without the required "close #issue-number" syntax
Example: PR without the required "close #issue-number" syntax
Example: A minimal follow-up PR correctly referencing both the issue and original PR
Claim Reward & Check Interface on Lightning Bounties
Claim Reward & Check Interface on
app.lightningbounties.com