> For the complete documentation index, see [llms.txt](https://docs.xym.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xym.network/transparency-and-source-code.md).

# Transparency and Source Code

Xym Network is built on the principle that real security requires transparency. The core system, including the sandbox, encryption layer, and recovery logic, will be released as **open-source software** for public review and independent auditing.

All cryptography follows open standards and verified hardware APIs such as Secure Enclave and StrongBox. Each major update will undergo an **external security audit**, with full reports published for users to verify.

Network components, including the VPN and DNS shield, will run on **signed, reproducible builds**, and every update will be **cryptographically signed**.

Xym Network is designed so users never have to rely on trust alone, every part of it can be **verified, inspected, and proven secure.**


---

# 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.xym.network/transparency-and-source-code.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.