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

# Settlement and Optional Yield

How SUSD supports settlement while elective Yield remains separate from protected customer gold.

### Settlement Without Using the Gold

SUSD is Solari's separately reserve-backed settlement unit. It connects eligible funding, purchases, Gold Pool subscriptions, sales, balance movements, and account workflows, and its backing framework is designed around two strict boundaries:

**Treasuries and cash.** SUSD is backed entirely by Treasuries and cash under its own independent reserve, safeguarding, issuance, redemption, and reporting framework — separate from Solari's operating capital and separate from any other platform balance.

**Separation from gold.** SUSD is explicitly not backed by customer gold, nor does it represent a claim on physical gold. Solari's "Green Box" architecture ensures that customer bullion held in the Trust Engine is never lent, rehypothecated, or used as a reserve asset to support SUSD.

Reserve composition, custodial arrangements, and the applicable attestation cadence will be finalized and disclosed ahead of production launch.

Customers may fund through supported fiat or cryptocurrency methods as available. Cleared funding, SUSD balances, gold holdings, pool reservations, and Yield allocations remain distinguishable inside the account so that the holder can understand what is owned, what is reserved, and what is participating in an elective pathway.

**Elective SUSD Yield**

Eligible participants may choose to allocate SUSD — not gold — to the separate Yield Engine. Returns are not guaranteed. A performance fee applies only to positive net results. At maturity or exit, the resulting proceeds return to the customer's SUSD balance, where they may support eligible purchases, subscriptions, transfers, or withdrawal pathways.

DGBs, sXAU, GoldNotes, custody gold, and VARA principal remain outside the Yield Engine. A customer can own gold without participating in Yield, and participation in Yield does not give the Yield Engine access to the customer's protected bullion. Full Yield strategy parameters, risk disclosures, and eligibility requirements will be published before Yield participation opens to customers.

**Clear separation:** Gold provides the ownership foundation. SUSD provides settlement, backed by its own Treasuries-and-cash reserve. VARA is membership. Elective Yield uses only the SUSD the customer chooses to allocate.

### Protected Gold and Optional Yield Remain Separate

![visual-4-separation-gold-yield](https://content.gitbook.com/content/foyvsiE4j1HR210JM2nP/blobs/MSmeCgF5i2xTHcA9EAo8/assets/visual-4-separation-gold-yield.svg)

***


---

# 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://solari-finance.gitbook.io/solari.finance-docs/settlement-and-optional-yield.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.
