> 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/goldusd-token/token/token-mechanics.md). # Token Mechanics ## Supply The intended model uses controlled issuance: new tokens enter circulation through authorized minting and leave circulation through redemption/burning or an equivalent supply-control process. ## Value reference goldUSD is designed around a USD-denominated unit of account. The mechanisms supporting secondary-market price stability will depend on mint/redemption access, liquidity and market structure. ## Yield treatment The exact mechanism by which economic yield reaches users is **TBD**. Possible implementation choices can differ materially — for example, an appreciating token value, rebasing balance, separate rewards mechanism or another structure — so no specific mechanism should be assumed until finalized. ## Permissions Any administrative or compliance permissions embedded in the token contracts will be documented transparently before production launch. --- # 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/goldusd-token/token/token-mechanics.md?ask=&goal= ``` `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.