> For the complete documentation index, see [llms.txt](https://docs.lightningbounties.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lightningbounties.com/docs/getting-started/posting-a-bounty.md).
# POSTING A BOUNTY
Simple Workflow on How to Post a Bounty on Lightning Bounties
{% stepper %}
{% step %}
### Visit [app.lightningbounties.com](#visit-app.lightningbounties.com) & Click on Login with GitHub
*Located on the Top Right*
{% endstep %}
{% step %}
### Copy/Paste Your GitHub Issue URL
{% endstep %}
{% step %}
### Set the amount in Sats for the Bounty Reward
*For this example we will use 21000 sats.*
{% endstep %}
{% step %}
### Click the Advanced Settings Toggle
{% endstep %}
{% step %}
### Click on the Dropdown Toggle & Set the Duration
*We recommend two weeks as a standard lock time, to give your hunters time to submit a PR, but also a short enough time to iterate on your bounty postings and format.*
{% endstep %}
{% step %}
### Click on Submit New Reward
*For this example we will set the bounty for 2 weeks.*
{% endstep %}
{% endstepper %}
#### :tada: Congrats! You just posted your first bounty!
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.lightningbounties.com/docs/getting-started/posting-a-bounty.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.