> For the complete documentation index, see [llms.txt](https://docs.fbtc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fbtc.com/security/bitcoin-reserve-address.md).

# Bitcoin Reserve Address

### Fixed Address

| Address                                    | Information                                                                |
| ------------------------------------------ | -------------------------------------------------------------------------- |
| bc1q7jgulg69frc8zuzy0ng8d5208kae7t0twyfjwm | <https://mempool.space/address/bc1q7jgulg69frc8zuzy0ng8d5208kae7t0twyfjwm> |
| bc1q6c3c0t3zvnphce37ufr4yz9veaqvew2wg0shwr | <https://mempool.space/address/bc1q6c3c0t3zvnphce37ufr4yz9veaqvew2wg0shwr> |
| 3HjNJWcn2ayFLikzmKRaFtcbLufYChQo3T         | <https://mempool.space/address/3HjNJWcn2ayFLikzmKRaFtcbLufYChQo3T>         |
| 374vhN24WryvNWUUZR2uDAnL4oNP5EW4qR         | <https://mempool.space/address/374vhN24WryvNWUUZR2uDAnL4oNP5EW4qR>         |

### Dynamic Address

The Bitcoin deposit address of each merchant is a dynamic address. These addresses can be queried through the contract as follows.

#### Step 1 : Query FBTC Address of Each Qualified User

1. Open your web browser and go to [this page](https://etherscan.io/address/0xbee335BB44e75C4794a0b9B54E8027b111395943#readProxyContract#F12).
2. Scroll down to find the method `12. getQualifiedUsers` and click to expand it.
3. Click the `Query` button to call the `getQualifiedUsers` method. This will return an array containing all the merchants' FBTC addresses.

<figure><img src="https://4102630944-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSdfKsVfWUlwTQH1ZXZQG%2Fuploads%2FctEn4YbykswKlnobWgss%2Fimage.png?alt=media&amp;token=2c38d669-3d6c-457e-bd12-4366239beffe" alt=""><figcaption></figcaption></figure>

#### Step 2: Query Bitcoin Deposit Address of Each Qualified User

1. On the same page, find the method `11. getQualifiedUserInfo` and click to expand it.
2. In the input field, enter each merchant's FBTC address obtained from Step 1.
3. Click the `Query` button to call the `getQualifiedUserInfo` method. This will return the detailed information for the merchant, including their corresponding BTC deposit address.
4. Repeat steps 2 and 3 for each merchant's BTC deposit address.

<figure><img src="https://4102630944-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSdfKsVfWUlwTQH1ZXZQG%2Fuploads%2FMj48wZ0W2hGm0hBiqhz0%2Fimage.png?alt=media&amp;token=53339f9c-8936-413f-8a2f-cafc2662dc8d" alt=""><figcaption></figcaption></figure>


---

# 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.fbtc.com/security/bitcoin-reserve-address.md?ask=<question>&goal=<user_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.