> For the complete documentation index, see [llms.txt](https://syncrate-1.gitbook.io/syncrate-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://syncrate-1.gitbook.io/syncrate-docs/introduction-to-syncrate.md). # Introduction to Syncrate Learn about Syncrate, the problem it addresses, and how SGLD brings gold-backed exposure onchain. Gold has long served as a store of value, but accessing and using physical gold can be difficult. Buying bullion often involves intermediaries, storage, insurance, transport, and minimum purchase sizes. Once acquired, gold can also be difficult to transfer or use across digital financial applications. Tokenization can make gold easier to access and use, but only when the digital token is supported by clearly defined reserves and transparent issuance rules. A token that represents gold should make it easier to interact with that asset without obscuring what backs it. ## How SGLD addresses this **SGLD (Syncrate Gold)** brings gold-backed exposure onchain. Each SGLD token is designed to be backed 1:1 by LBMA-standard physical gold held in secure vaults in the UAE. By representing gold on Base, SGLD makes gold-backed exposure available in a digital form that can be held and transferred onchain and integrated with compatible blockchain applications. Users do not need to arrange physical storage or insurance themselves to hold SGLD. Syncrate’s approach combines physical reserves with onchain issuance rules: * **Physical gold backing:** SGLD is backed by LBMA-standard gold held in UAE vaults. * **Independent verification:** The physical reserves are subject to independent audits conducted by Bureau Veritas. * **Onchain supply:** SGLD’s token supply and smart-contract activity can be inspected onchain. * **Controlled issuance:** SGLD is minted through the protocol’s deposit process, which is designed to maintain the relationship between issued tokens and their backing. * **Pricing infrastructure:** Chainlink provides pricing infrastructure used by the protocol. These measures are intended to make the relationship between SGLD and its underlying gold easier to understand and verify. Reserve verification and smart-contract rules serve different purposes: audits provide evidence about physical holdings, while onchain data makes token supply and contract activity visible. ## From gold ownership to productive gold SGLD is the foundation of Syncrate’s broader work to bring real-world assets into onchain finance. It provides gold-backed exposure; it does not itself generate yield. sySGLD is a separate product designed to give eligible SGLD holders access to yield generated through short-term gold-financing with vetted bullion banks and refiners. This separates holding gold-backed exposure through SGLD from choosing to participate in a financing strategy through Prime. ## The principle behind Syncrate Syncrate is built around a simple idea: real-world assets should be easier to access and use onchain, while the assets behind them and the rules governing their tokens remain clear. SGLD is the starting point. The following documentation explains how it works, how its reserves and contracts are structured, and how users and developers can interact with it. --- # 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://syncrate-1.gitbook.io/syncrate-docs/introduction-to-syncrate.md?ask=&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.