> For the complete documentation index, see [llms.txt](https://docs.relicsprotocol.com/relics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.relicsprotocol.com/relics/learn-more/faqs.md).

# FAQs

<details>

<summary>Wen launch?</summary>

The plan is to launch the first relics indexer in February 2025. An initial implementation of the relics indexer was already launched by [Bones Protocol](https://twitter.com/bonesprotocol) and is running on Dogecoin.

</details>

<details>

<summary>Relics vs. Generic Smart Contracts on Bitcoin?</summary>

Our feature ideas will not make relics generally programmable and we're not aiming for smart contract functionality.

</details>

<details>

<summary>Will there be a frontend for the swaps?</summary>

We are working on a swap interface with an embedded BTC wallet. The swap interface will also be open source and any company or individual can host it for others. We will not run any (paid) services.

</details>

<details>

<summary>Swapping against BTC?</summary>

On-chain liquidity pools with BTC don't work with Bitcoin's current functionality. That's why a [base relic](/relics/core-features/mbtc.md) is needed to swap against.&#x20;

However, with the AMM pools it will be possible to swap against wrapped BTC relics (like "WBTC") with a centralized reserve.

The same would work for stable coins like e.g. USDC.

</details>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.relicsprotocol.com/relics/learn-more/faqs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.