> 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/managing-your-bounty/user-balances-overview.md).
# User Balances Overview
In this section, you can see an overview of a user's balances on the Lightning Bounties platform. Each user has two key balances that manage their available and reserved rewards for GitHub issues.
## Available Balance
The **available balance** represents the amount of satoshis (sats) a user currently holds and can use to post new rewards on GitHub issues. This balance is also withdrawable, allowing the user to transfer their available sats to a personal Lightning Network wallet at any time.
## Reserved Balance
The **reserved balance** consists of the sats that are allocated to already posted rewards on GitHub issues. When a user posts a reward, the corresponding amount of sats is locked in this balance, ensuring that the reward is paid out once the issue is resolved.
By tracking these balances, users can easily manage their available funds and reserved rewards while contributing to the open-source community.
---
# 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/managing-your-bounty/user-balances-overview.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.
