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

# Transparency and Disclosure

We firmly believe that on-chain financial transparency standards should meet or exceed those of traditional finance. BlockRock adopts a comprehensive information disclosure policy to ensure investors always have access to all necessary information.

Investors can review key data for each fund on our platform’s product pages, including:

* **Investment Strategy**: How the fund operates and sources returns.
* **Underlying Asset Composition**: RWA assets held by the fund.
* **Historical Performance**: Past returns and market trends.
* **Risk Assessment**: Potential market risks and hedging strategies.
* **Smart Contract Audits**: All smart contracts are audited by top-tier industry auditors, with reports publicly accessible.
* **Asset Management Transparency**: All assets are custodied by independent third parties and audited periodically. Investors can query NAVs and management reports.

Furthermore, BlockRock and related entities undergo regular financial and cybersecurity audits, with results shared with authorized investors or regulators to ensure ongoing compliant operations.


---

# 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.blockrock.win/trust-and-security/quickstart.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.
