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

# Security

### **What are Hubble's Security Practices?**

Hubble is obsessed with security. There are way more lines of code for testing than actual smart contract functionality. Code reviews are extremely strict and security audits are performed regularly, with five having been completed thus far. Hubble works with the "Move slow and don't break things" attitude, as the smart contracts involve users' funds.

* Integration tests
* Stress tests
* Security tests&#x20;
* The Soteria audit tool&#x20;
* Property based tests, fuzzing&#x20;
* Asset-based Deposit caps
* Withdrawal flow caps

### **What is the plan for managing regulatory risk?**

Since USDH is not fiat-backed, regulatory risks should not affect the viability of the token. As regulations begin to be drawn for DeFi, Hubble plans to align itself with a regulatory framework that should increase the mainstream adoption of DeFi as well as Hubble's services.&#x20;


---

# 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.hubbleprotocol.io/faq/security.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.
