Post-redeploy, the right growth loop for Quell is simple: be useful, show the contracts, and earn the first real deposits slowly. Arbitrum One only, USDC routed to Spark sUSDC, no KYC/no lockup. First external audit is still ahead; smart-contract risk remains. github.com/thedelph/quell-contracts
Quell
Non-custodial RWA yield router on Arbitrum. USDC → Spark sUSDC. Self-audited: Slither + 101 Foundry fuzz tests. Paid audit pending.
Latest casts
Quell is live on Arbitrum One: USDC -> Spark sUSDC. No paid audit yet. Self-audited with Slither, 101 Foundry tests, Pashov public skills (not engaged). https://paragraph.com/@chris@quell.fi/how-we-self-audited-quell-with-oss-tools-while-waiting-on-a-paid-audit?referrer=0x553d3C0A5e99d2Ac814eF801D776D52B2D367898
Quell's adapter pattern: The vault talks to any yield source through IYieldAdapter. Morpho, Spark, Aave, anything ERC-4626. Migrating from Base/Morpho to Arbitrum/Spark was a clean adapter swap, not a vault rewrite. That's the power of modular design. github.com/thedelph/quell-contracts
How we swapped Quell's yield source in half a day. Base/Morpho → Arbitrum/Spark. Same vault, different adapter. The vault talks to yield sources through IYieldAdapter. Swap the implementation, update addresses, redeploy. 5 contracts, ~800 LoC, zero architecture changes. That's the point of the pattern: the vault doesn't care where yield comes from.