# Claiming Multiple Bounties: Multi-Bounty PRs

## Claiming Multiple Bounties: Multi-Bounty PRs

You can solve and claim multiple bounties in a single pull request by referencing several issues in your PR description (e.g., `close #6 close #12`).

{% hint style="warning" %}

## :warning: IMPORTANT :warning:

#### You must click "***Claim Reward***" & "***Check***" on each individual issue on Lightning Bounties to receive each bounty reward. 

Claiming is done separately for every issue, even if they were closed together in one PR.

<img src="/files/XP8j8RdbP567K0fumXSa" alt="" data-size="original">
{% endhint %}

***

## How to Claim Multiple Bounties in One PR

1. **Solve multiple issues**
   * Make sure each issue you solve is still open bounty.
2. **Create a single PR referencing all issues**

   * In your PR description, use the closing keywords for each issue you solved:

   <figure><img src="/files/LImZ0sJbYAwKd1eoOTGH" alt="Screenshot of a PR description with multiple close #issue-number references on GitHub"><figcaption><p>A single PR can close multiple issues by listing each with<code>close #issue-number</code> </p></figcaption></figure>

   * This will close all referenced issues when the PR is merged.
3. **Wait for PR approval and merge**
   * Once the PR is merged, GitHub will close all referenced issues.
4. **Claim rewards individually**
   * Go to each issue’s page on Lightning Bounties.
   * Click '***Claim Reward'*** and ***'Check'*** for each bounty you solved.
   * Each bounty reward will be processed separately.

<figure><img src="/files/XP8j8RdbP567K0fumXSa" alt="Screenshot of Lightning Bounties issue page showing the &#x27;Claim Reward&#x27; button."><figcaption><p>You must claim each bounty individually, even if closed in one PR.</p></figcaption></figure>

***

### Common Pitfalls & How to Avoid Them

* **Forgetting to use closing keywords:**\
  Always include `close #issue-number` for each issue in the PR description (not in comments or commits).
* **Not claiming each bounty:**\
  After your PR is merged, visit each issue on Lightning Bounties and click "Claim Reward" separately.
* **Trying to claim after missing a close keyword:**\
  If you forgot to link an issue, create a minimal follow-up PR for that issue, include the correct closing keyword, and reference the original PR.
* **Assuming rewards are automatic:**\
  Rewards are **not** sent automatically when the PR is merged. You must manually claim each one.

***

### Visual Workflow

<div align="center" data-full-width="false"><figure><img src="/files/gc6ZxRiZC0regE8Zqlzq" alt=""><figcaption><p>Visual Workflow</p></figcaption></figure></div>

***

### Best Practices & Troubleshooting

* **Always use closing keywords (`close #issue-number`) in the PR description, not in comments or commits.**
* **You must claim each bounty individually on Lightning Bounties, even if multiple issues were closed in one PR.**
* **If you accidentally missed a bounty, create a minimal follow-up PR to properly close and claim it.**
* **Refresh the PR page after editing links to see updates.**

***

For more details, see [Claim Reward Criteria & Troubleshooting Guide](https://docs.lightningbounties.com/docs/getting-started/solving-a-bounty/claim-reward-criteria-and-troubleshooting-guide) and [GitHub’s guide to linking pull requests to issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue).

For additional assistance, join the Lightning Bounties [Discord](https://discord.gg/zBxj4x4Cbq) community.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lightningbounties.com/docs/getting-started/solving-a-bounty/claiming-multiple-bounties-multi-bounty-prs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.