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

# FAQ

## What is goldUSD?

goldUSD is being developed as a yield-generating, dollar-denominated onchain asset whose initial yield engine focuses on market-neutral opportunities in gold and gold derivatives.

## Is goldUSD the same as tokenized gold?

No. goldUSD is intended to use a USD-denominated unit of account. Its strategy may use gold-related instruments, but the token is not intended simply to track the spot price of gold.

## Does goldUSD require gold prices to rise to generate yield?

The strategy is designed to generate returns primarily from relative-value, basis and financing opportunities while hedging much of the outright gold-price exposure. Hedging is imperfect, however, and losses remain possible.

## Is the yield fixed?

No. Yield is expected to vary with market conditions, strategy performance, costs and the final distribution mechanism.

## What is the target yield?

The project may communicate an indicative target range in approved product materials, but no target is guaranteed. The final public target and calculation methodology will be added here when approved.

## What backs goldUSD?

The final reserve and legal structure is still being finalized. Detailed reserve composition, liquidity arrangements and relevant counterparties will be published before production launch.

## Can I redeem goldUSD for dollars?

A redemption mechanism is intended for eligible participants. Exact eligibility, minimums, fees, payout assets and settlement times are **TBD**.

## Which blockchain will goldUSD use?

The initial network has not yet been finalized in this documentation. Official networks and verified contract addresses will be published before launch.

## Who manages the strategy?

The final production roles and legal entities responsible for issuance, asset management, custody and other functions will be disclosed once the operating structure is finalized.

## Has goldUSD been audited?

Production smart-contract and reserve/financial assurance information will be published in the [Audits](/goldusd-docs/transparency/transparency/audits.md) section when available.

## What are the main risks?

Key risks include market/basis, leverage, liquidity, counterparty, custody, smart-contract, operational and regulatory risks. See [Risk Management](/goldusd-docs/risk/risk.md) and [Risk Disclosure](/goldusd-docs/legal/legal/risk-disclosure.md).

## Where can I find the official contract address?

Only use addresses published in [Smart Contract Addresses](/goldusd-docs/developers/developers/smart-contract-addresses.md). No production address is listed at this pre-launch stage.


---

# 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://goldusd.gitbook.io/goldusd-docs/legal/faq.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.