> For the complete documentation index, see [llms.txt](https://docs.hermetica.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hermetica.fi/hbtc/risk-disclosures/smart-contract-risk.md).

# Smart Contract Risk

hBTC is implemented through a set of **Clarity smart contracts** deployed on the Stacks blockchain. The core vault architecture follows a **simple, ERC-4626–style vault design**, where user deposits mint proportional shares and withdrawals redeem assets based on net asset value.

Despite this conservative design approach, smart contract risk remains inherent and includes:

* **Code vulnerabilities:** Undiscovered bugs, logic errors, or edge cases in hBTC smart contracts could result in unexpected behavior, loss of funds, or incorrect accounting.
* **Integration risk:** hBTC interacts with external smart contracts (e.g., money markets, yield protocols). Vulnerabilities or failures in integrated contracts may adversely affect protocol operation.
* **Upgrade and configuration risk:** Although governance controls and timelocks are in place, contract upgrades or parameter changes may introduce new risks or unintended consequences.
* **Execution risk:** Smart contracts operate deterministically based on on-chain inputs; oracle failures, unexpected state transitions, or extreme market conditions could impact execution outcomes.

{% hint style="success" %}
To mitigate these risks, hBTC smart contracts have undergone **multiple independent security audits** conducted by experienced third-party firms. 

*For additional details, see the* [*Audits documenatation*](/hbtc/audits.md)*.*
{% endhint %}

{% hint style="info" %}
While audits and conservative design reduce risk, they do not eliminate the possibility of unforeseen vulnerabilities or failures.
{% endhint %}


---

# 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:

```
GET https://docs.hermetica.fi/hbtc/risk-disclosures/smart-contract-risk.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.