> ## Documentation Index > Fetch the complete documentation index at: https://docs.writz.xyz/llms.txt > Use this file to discover all available pages before exploring further. # Research: Stellar USDC Liquidity & Blend Ecosystem **Author:** Research **Date:** 2026-06-22 **Status:** Complete *** ## Overview The supply side of Writz Lend - USDC lenders who provide the capital that borrowers draw against - depends on Stellar's existing USDC ecosystem. This document maps the USDC liquidity landscape on Stellar and evaluates how Writz fits into and potentially integrates with existing protocols. *** ## USDC on Stellar - State of Play (2026) | Metric | Value | | - | - | | USDC monthly volume on Stellar | \$500M+ | | USDC issuer | Circle (native issuance - not bridged) | | Largest USDC protocol | Blend (\$80M+ TVL as of early 2026) | | Network operations (Q3 2025) | 1 billion+ | | Typical transaction finality | 3–5 seconds | | Typical transaction fee | \< \$0.001 | **Critical point:** Stellar USDC is natively issued by Circle - not a bridged or wrapped version. This means: * No bridge risk on the USDC side * Regulatory compliance built-in (Circle's USDC is fully regulated) * Stellar USDC is the same USDC used in MoneyGram, payments integrations, and enterprise contexts * Users borrowing USDC from Writz get a real, liquid, institutional-grade asset *** ## Blend Protocol - The Primary Competitor and Reference **Repository:** [blend-capital/blend-contracts-v2](https://github.com/blend-capital/blend-contracts-v2) **TVL:** \$80M+ (early 2026) **Built on:** Soroban ### What Blend is Blend is Stellar's Aave equivalent - a lending protocol primitive that allows anyone to create isolated lending pools. It supports: * Pool creation by anyone (permissionless) * Per-pool interest rates and collateral factors * A unique backstop module (insurance against bad debt) * Auto-compounding vaults built on top ### Blend's limitation: No BTC, No Privacy Blend currently supports Stellar native assets and SAC tokens (Stellar Asset Contract). It does **not** support: * Bitcoin as collateral (no BTC on Stellar today) * Zero-knowledge position privacy **This is the gap Writz fills.** ### Blend as a co-existence opportunity Rather than competing with Blend for USDC liquidity, Writz can potentially co-exist: * **Short term:** Writz operates its own isolated USDC pools (independent from Blend) * **Medium term:** Writz could integrate with Blend pools as a source of USDC liquidity for borrowers, acting as a BTC-collateral gateway * **Long term:** If Blend adds SPV verification support, Writz's open SDK provides the primitive **Why independent pools first:** The ZK privacy requirement means position state must be managed within Writz's own contracts. Blend's architecture doesn't accommodate ZK-private positions without significant modification. *** ## Oracle Integration: SEP-40 **Correction (2026-09-16, on-chain verified):** this section previously claimed "Blend is already integrating RedStone for price feeds." That was wrong - Blend uses **Reflector**, confirmed via Stellar's own oracle-providers documentation. A follow-up correction also turned out to be wrong: Reflector's *Stellar-assets* oracle instance (testnet `CAVLP5...`) has no plain BTC, but its separate *external CEXs & DEXs* instance (testnet `CCYOZJCOPG34LLQQ7N24YXBM7LL62R7ONMZ3G6WZAAYPB5OYKOMJRN63`) does - confirmed by directly calling `assets()`/`lastprice()` on testnet, see `docs/research/oracle-design.md`. Writz can share the same oracle standard, and now plausibly the same specific BTC feed, that Blend's ecosystem already runs on. * Writz should build against the **SEP-40 standard**, the same interface Blend's oracle (Reflector) also speaks - provider-agnostic by design, so this part of the original point holds * Reflector's external-prices instance lists a plain `{"Other":"BTC"}` asset with a live, updating price (confirmed on-chain 2026-09-16: \~\$76,185, 5-minute resolution) - see `docs/research/oracle-design.md` for the full verified recommendation (Pyth primary, Reflector secondary; DIA parked - its documented testnet contract doesn't exist on-chain) * Consistent oracle standards (SEP-40) across the Stellar DeFi ecosystem still reduce the attack surface for oracle manipulation, independent of which specific provider is used *** ## USDC Liquidity Bootstrap Strategy The chicken-and-egg problem: USDC lenders won't supply unless there are BTC borrowers. BTC borrowers won't deposit unless there's USDC to borrow. ### Phase 2 Bootstrap Approaches **1. Protocol-owned liquidity (POL):** Writz can use initial funding (from SDF grants, SCF, or equity) to seed the USDC pool with protocol-owned capital. This provides initial liquidity before organic lender supply. Target seed: $50,000–$100,000 USDC from protocol treasury to bootstrap initial pool. **2. High initial supply APY:** Set initial protocol fee to 0% temporarily, routing 100% of interest to USDC suppliers. This creates above-market yields (e.g., 10–15% APY during bootstrap) that attract USDC lenders. **3. Target Stellar DeFi native users:** Stellar users who already hold USDC are the easiest to convert - they don't need to bridge anything. Target them via Stellar wallet integrations (Lobstr, Freighter), Stellar Discord communities, and integration with Stellar DeFi newsletters. **4. Institutional lenders:** Post-FTX, institutional crypto funds are looking for compliant, audited DeFi yield. Writz's compliance-friendly privacy (ASPs, audit trail available) and Circle's native USDC make it attractive for institutions. Direct outreach to crypto-native family offices and funds. *** ## USDC Pool Architecture in Writz Writz's USDC pools are separate from Blend's pools. Each pool has: | Component | Description | | - | - | | **Pool contract** | Soroban contract managing supply and withdrawal | | **Receipt tokens** | Users receive `wUSDC` (Writz USDC) representing their pool share | | **Interest accrual** | Continuous, per-ledger accrual | | **Withdrawal queue** | If utilization > 95%, withdrawal requests are queued until liquidity frees up | ### Multiple pool tiers (future consideration) For Phase 2+, Writz could offer multiple USDC pool tiers with different risk/reward profiles: | Pool | Collateral ratio | Interest rate | Target user | | - | - | - | - | | **Conservative** | 200% min collateral | Lower rates | Risk-averse lenders | | **Standard** | 150% min collateral | Standard rates | General market | | **Aggressive** | 130% min collateral | Higher rates | Yield-focused lenders | *** ## Key Findings 1. **Stellar USDC is ideal** - native issuance by Circle, \$500M/month volume, real institutional liquidity 2. **Blend is complementary, not a competitor** - Blend has no BTC and no privacy; Writz fills the gap 3. **SEP-40 is the oracle standard** - align with the broader Stellar DeFi ecosystem; see `docs/research/oracle-design.md` for the corrected provider choice (Pyth + Reflector, not RedStone - Blend itself uses Reflector, not RedStone; DIA was parked, not chosen) 4. **Protocol-owned liquidity is the best bootstrap mechanism** - use initial grants to seed the pool 5. **Institutional USDC lenders are a realistic target** - compliance-friendly privacy attracts institutional capital 6. **Independent pools required** - ZK position privacy cannot be retrofitted onto Blend's architecture *** *Last updated: 2026-06-22* *Sources: [Blend Protocol Introduction](https://medium.com/script3/introducing-blend-95aaf66bdf41) · [Blend Contracts v2](https://github.com/blend-capital/blend-contracts-v2) · [Stellar Oracle Providers](https://developers.stellar.org/docs/data/oracles/oracle-providers) · [Stellar DeFi Overview](https://stellar.org/blog/ecosystem/what-the-defi-is-happening-on-stellar)* This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.