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

# Audits

Vultisig security practices and audits. Independent assessments and responsible disclosure.

Open-source threshold signatures, an audited signing library, and responsible disclosure.

There is no public bug bounty program today. Report a vulnerability through [GitHub](https://github.com/vultisig) or [Discord](https://discord.gg/Cugw9T2NrP).

***

## Security model

Vultisig uses threshold signature schemes (TSS). There is no complete private key in normal operation:

* Vault shares create signatures together
* Compromising one device does not move funds
* All app code is on [GitHub](https://github.com/vultisig)

For the protocol, see [Security & Technology](/security-and-technology/overview.md).

***

## Audits

### DKLS23 protocol library

The DKLS23 implementation Vultisig uses is from Silence Laboratories. Trail of Bits audited that **library**, not the Vultisig apps:

| Auditor       | Date | Scope                   | Report                                                                                          |
| ------------- | ---- | ----------------------- | ----------------------------------------------------------------------------------------------- |
| Trail of Bits | 2024 | DKLS23 protocol library | [View report](https://github.com/silence-laboratories/dkls23?tab=readme-ov-file#security-audit) |

### Application audits

Mobile and desktop application audit reports will be linked here when they are published.

***

## For users

1. Backup vault shares to separate, offline storage
2. Verify addresses before signing
3. Keep the apps updated
4. Use a Secure Vault for significant holdings
5. Never share vault shares or backup files

### What Vultisig cannot do

* Access your funds
* Recover lost vault shares
* Reverse blockchain transactions
* View your private keys (they never exist)

***

## Related

* [Security & Technology](/security-and-technology/overview.md)
* [Emergency Recovery](/security-and-technology/emergency-recovery.md)
* [Privacy Policy](/help-and-legal/privacy.md)


---

# 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.vultisig.com/help-and-legal/security.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.