# Transparency & Verifiability ### Overview Transparency is a **core requirement** of QUSDC. QUSDC is designed so that **anyone** — users, developers, auditors, or ecosystem participants — can independently verify that the system is operating correctly. There are no hidden balances, discretionary controls, or off-chain promises required to trust QUSDC. *** ### On-Chain First by Design All critical components of QUSDC operate **on-chain**, including: * Token issuance * Token burning * Total supply tracking * Reserve accounting * Net circulation data This means the system does not rely on: * Private databases * Internal reports * Periodic attestations * Manual disclosures Instead, **the blockchain itself is the source of truth**. *** ### Verifiable QUSDC Supply The total supply of QUSDC is: * Public * Queryable * Verifiable at any time Anyone can independently confirm: * How much QUSDC exists * How much has been minted * How much has been burned * How much is currently in circulation There is no scenario where QUSDC supply can increase without being visible on-chain. *** ### Verifiable USDC Reserves Every QUSDC in circulation is backed by **USDC reserves** that are also tracked on-chain. Users can verify: * The total amount of USDC held as backing * That reserves match QUSDC supply * That reserves are locked according to protocol rules This ensures that: > **QUSDC supply always equals USDC reserves.** No trust in third-party statements is required to validate this relationship. *** ### Issuance and Redemption Transparency Minting and burning QUSDC are **explicit on-chain actions**. For every issuance: * USDC is deposited * QUSDC is minted at a 1:1 ratio * Both actions are recorded on-chain For every redemption: * QUSDC is burned * USDC is released * Both actions are visible and traceable This creates a clear, auditable lifecycle for every QUSDC token. *** ### Net Circulation Clarity QUSDC distinguishes between: * Total issued tokens * Tokens currently in circulation * Tokens held but not circulating By tracking **net circulation**, QUSDC provides a more accurate picture of active supply and system health. This data is refreshed regularly and is publicly accessible. *** ### Smart Contracts as the Enforcement Layer Transparency alone is not enough — rules must also be **enforceable**. In QUSDC: * Smart contracts define what actions are allowed * Contracts enforce collateral requirements * Contracts prevent unbacked issuance * Contracts ensure proper burning on redemption There is no ability to override these rules without deploying new contracts under public scrutiny. *** ### No Reliance on Off-Chain Trust Traditional stablecoins often rely on: * Periodic attestations * External audits * Legal assurances While those may provide confidence, they still require **trust in intermediaries**. QUSDC minimizes this dependency by ensuring that: * The most critical guarantees are enforced on-chain * Verification does not depend on timing or reporting cycles * Users can verify system integrity themselves *** ### Transparency for All Participants Transparency in QUSDC benefits: * **Users** — confidence that funds are fully backed * **Developers** — predictable and auditable system behavior * **Exchanges & DeFi protocols** — reliable settlement asset * **Auditors & partners** — clear, inspectable mechanics This openness enables ecosystem-wide trust without centralized control. *** ### Limitations of Transparency (Honest Disclosure) While QUSDC is fully transparent on-chain, it is important to understand: * USDC itself is a fiat-backed asset * Ultimate fiat reserves exist off-chain * QUSDC makes reserve *representation* transparent on-chain QUSDC maximizes transparency **where blockchain technology is strongest**, while being clear about external dependencies. *** ### Summary QUSDC is transparent by design because: * Supply is publicly verifiable * Reserves are on-chain and auditable * Issuance and redemption are fully visible * Smart contracts enforce the rules * No hidden actions are possible This allows users to move from: > **“Trust the issuer” → “Verify the system.”** --- # Agent Instructions: 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: ``` GET https://docs.stable.qie.digital/transparency-and-verifiability.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.