> 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/general-access-products.md).

# General-Access Products

## **Overview**

BlockRock is a Real-World Assets (RWA) tokenization platform dedicated to bringing traditional financial assets onto the blockchain, enabling more efficient, transparent, and decentralized investment methods. As a gateway for global investors, BlockRock integrates blockchain technology, smart contracts, and institutional-grade financial assets to deliver innovative RWA investment products.

The first product in the BlockRock ecosystem, QQQAI, is an enhanced equity ETF based on the **Nasdaq 100 Index (NDX100)**, optimizing returns through options strategies while providing downside protection, offering global investors a more robust and optimized asset allocation choice.

In the future, BlockRock will launch additional general-access products covering fixed income, equity ETFs, bonds, commodities, and more, while deeply integrating with DeFi protocols to enable investors to engage in lending, staking, yield optimization, and other operations through on-chain protocols, expanding the application scope of RWAs in the Web3 ecosystem.


---

# 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/general-access-products.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.
