> For the complete documentation index, see [llms.txt](https://docs.acre.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acre.fi/~/revisions/nx8vZBscxS1DgbAO0Urh/technical-architecture.md).

# Technical Architecture

This diagram below visualizes Acre's core architecture:

* Users deposit BTC through the Acre dApp, which auto-bridges native BTC to tBTC (ETH L1) and interfaces with the **tBTC Depositor** (manages deposits) and **tBTC Redeemer** (manages withdrawals) contracts at the **tBTC Bridge Integration Layer**
* Deposited tBTC is converted to the **acreBTC** deposit token and flows through the **Acre Dispatcher**, which dispatches tBTC to **Acre Vaults** approved by the **Acre Security Council**. 
* tBTC rewards generated by the vaults are then routed back to the acreBTC vault and reinvested.

(To view a diagram of the first Acre vault (**Vault "A" below**), check out [macreBTC1 Architecture](https://docs.acre.fi/~/revisions/nx8vZBscxS1DgbAO0Urh/technical-architecture/macrebtc1-architecture).)

<figure><img src="/files/vQayjygxyAoeJAMQw2Rr" 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 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.acre.fi/~/revisions/nx8vZBscxS1DgbAO0Urh/technical-architecture.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.