# Core Design Principles ### Overview QUSDC is designed around a small set of **clear, non-negotiable principles**.\ These principles define how QUSDC behaves, how risk is managed, and why users can rely on it as a stable on-chain dollar. Every component of QUSDC — from issuance to redemption — follows these rules. *** ### 1. 100% Reserve Backing QUSDC is **fully reserved at all times**. * Every QUSDC is backed **1:1 by USDC** * Tokens are minted only when reserves are locked * Tokens are burned when reserves are released There are: * No fractional reserves * No rehypothecation * No hidden leverage This ensures that QUSDC supply always matches real USDC value. *** ### 2. Stability Without Algorithms QUSDC does not rely on: * Price oracles * Supply rebalancing mechanisms * Incentive-based stabilization * Market-driven peg maintenance Instead, stability is enforced through a simple rule: > **QUSDC can only exist when USDC exists as backing.** This eliminates the failure modes commonly associated with algorithmic stablecoins and ensures predictable value. *** ### 3. Trust-Minimized Issuance QUSDC issuance is **not controlled by people or organizations**. All core actions are enforced by **deterministic smart contracts**, including: * Minting * Burning * Supply tracking * Reserve accounting There is: * No discretionary minting * No manual intervention * No privileged operator with special access The protocol enforces the rules automatically and transparently. *** ### 4. Native Layer-1 Issuance QUSDC is issued **directly on the QIE blockchain**. This means: * QUSDC is not bridged from another network * QUSDC is not a wrapped asset * Issuance logic lives entirely on QIE Native issuance provides: * Lower systemic risk * Faster settlement * Lower transaction fees * Simpler integrations for developers *** ### 5. On-Chain Transparency Transparency is a core requirement of QUSDC. All critical data is publicly verifiable on-chain, including: * Total QUSDC supply * USDC reserve balances * Issuance and redemption activity * Net circulation metrics Users do not need to rely on off-chain reports or third-party attestations to verify the system. *** ### 6. No Liquidation Risk QUSDC is not a lending position or a leveraged instrument. Because: * QUSDC is backed 1:1 by a stable asset (USDC) * There is no price volatility in the collateral * There is no over-collateralization requirement There is **no liquidation mechanism** and **no risk of forced position closure**. This makes QUSDC suitable for users who want simplicity and capital safety. *** ### 7. Ecosystem-First Design QUSDC is designed specifically for the **QIE ecosystem**. It is built to integrate seamlessly with: * Wallets * Exchanges * DeFi protocols * Payment platforms * Developer tools By acting as a common stable unit of account, QUSDC enables ecosystem-wide composability and growth. *** ### 8. Conservative by Design QUSDC prioritizes: * Predictability over experimentation * Safety over complexity * Transparency over optimization Every design choice is made to reduce risk and increase user confidence, especially for long-term usage. *** ### Summary The core principles of QUSDC ensure that it is: * Fully backed * Predictable * Transparent * Decentralized by design * Native to the QIE blockchain These principles form the foundation of QUSDC as a **reliable on-chain dollar**. --- # 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/core-design-principles.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.