Loopscale: How Order-Book Lending Changes Solana Rates
Loopscale replaced the liquidity pool with an on-chain order book. Fixed rates, isolated risk, and $100M in deposits later, it is reshaping how Solana users think about lending yields.
The Problem with Pooled Lending
Every major lending protocol on Solana uses the same basic design: a shared liquidity pool. Depositors put assets in, borrowers take them out, and an algorithm sets interest rates based on utilization. Kamino, Jupiter Lend, Save, MarginFi. Same architecture, different parameters.
The model works, but it has structural trade-offs. Rates are variable. When utilization spikes, your borrowing cost can double in an hour. When it drops, lender yields crater. Neither side gets predictability. And because all depositors share one pool, a bad collateral type or a liquidation cascade can affect everyone, even if your own position was conservative.
Loopscale takes a different approach. Instead of pooling liquidity, it runs an on-chain order book that matches individual lenders with individual borrowers at fixed rates for fixed durations. The model is closer to how bond markets work in TradFi than to how Aave or Kamino operate.
How Order-Book Lending Works
The mechanics are straightforward. Lenders post offers specifying three things: the rate they want, the duration (1 day, 1 week, 1 month, or 3 months), and which collateral types they will accept. Borrowers browse available offers and take the best match for their needs.
Once matched, both sides lock in. The lender earns a fixed rate for the full term. The borrower pays a fixed cost. No utilization curves, no surprise rate swings at 3 AM.
This changes the economics in two ways.
First, it removes the lender-borrower spread that pool-based systems create. In a shared pool, the protocol sets rates using a curve that necessarily sits between what lenders earn and what borrowers pay. The gap is the protocol's margin plus inefficiency. In an order book, the two sides negotiate directly, and the spread compresses.
Second, risk is isolated per loan. If a borrower posts JLP tokens as collateral and that position goes bad, only the lender who accepted JLP collateral takes the hit. Other lenders who required SOL or USDC collateral are unaffected. In a pooled system, bad debt from any loan can socialize across the entire pool.
What Loopscale Offers Today
Loopscale launched on Solana in April 2025, originally incubated as Bridgesplit before pivoting to lending. By early 2026, the protocol had crossed $100M in total deposits and processed over $1B in cumulative borrowing volume. It is backed by CoinFund, Solana Ventures, Coinbase Ventures, and Jump Capital.
The product stack has four layers.
Vaults. Managed strategies where users deposit a base asset (USDC, SOL, JLP) and a vault curator handles allocation into Loopscale's lending markets. The flagship USDC vault delivers 10%+ APY by combining fixed-rate lending with idle-capital optimization through partner protocols. The OnRe USDC Vault has run as high as 12.56% APY by integrating ONyc (a tokenized RWA product).
Loops. One-click leveraged yield strategies. A user deposits collateral, the protocol borrows against it, redeposits, and repeats, all in a single atomic transaction. Loops can reach up to 4x leverage. LST loops (stSOL, jitoSOL) are popular because the underlying yield covers most of the borrowing cost, making leverage cheaper. Some loops have delivered 20%+ annualized, though with proportionally higher risk.
Fixed-rate borrowing. The core product. Borrow against SOL, LSTs, LP tokens, memecoins, or RWA tokens at a known rate for a known duration. Risk is isolated per loan, so posting volatile collateral does not affect other borrowers.
Advanced Lend. For users who want granular control. Set your own rate, pick acceptable collateral types, choose duration. The order book matches you when a borrower meets your terms.
The Rate Comparison
Here is where Loopscale sits relative to pool-based alternatives for USDC lending:
| Protocol | Model | USDC Rate | Rate Type | TVL |
|---|---|---|---|---|
| Loopscale Vault | Order book | 10-12% | Variable (managed) | ~$100M total |
| Loopscale Advanced | Order book | 3-11% | Fixed per loan | Included above |
| Kamino | Pool | 8.2% | Variable | $3B+ |
| Jupiter Lend | Pool | 3.8% | Variable | $750M+ |
| Save | Pool | 2.1% | Variable | $200M+ |
| Lulo (aggregator) | Multi-pool | 7.8% | Variable | $150M+ |
The headline rates on Loopscale vaults are higher than most pool-based alternatives. Part of that comes from the order-book efficiency. Part comes from the points program incentivizing deposits (an active airdrop farming campaign is running). And part comes from vault strategies that layer leverage and partner protocol rewards on top of base lending yield.
Strip away the incentives and the base fixed-rate lending on Loopscale sits in the 3-11% range depending on duration and collateral type. That is competitive with Kamino and above Jupiter Lend on the same asset.
The April 2025 Exploit
Two weeks after launch, Loopscale lost $5.8M (5.7M USDC + 1,200 SOL) to an oracle manipulation attack. The exploit targeted the RateX PT token pricing feed: the attacker inflated the token's price on a low-liquidity pair, tricked Loopscale's oracle into reporting the manipulated price, and took out undercollateralized loans against it.
The damage was roughly 12% of TVL at the time. The team identified the root cause within hours, offered the attacker a 10% white-hat bounty, and recovered all funds within 72 hours. Vault withdrawals reopened on May 8, 2025.
The incident matters for two reasons. First, the oracle vulnerability was in pricing an exotic collateral type, not in the core order-book engine. The risk isolation model actually contained the damage: only users in the affected vaults lost funds temporarily. Second, the recovery was fast and complete, which is unusual in DeFi exploits.
Pre-launch, OShield audited Loopscale and flagged three critical, one high, and one medium severity issue, all resolved before deployment. The oracle manipulation vector was not caught by the audit because it depended on external market conditions rather than code logic. Post-incident, Loopscale added borrow and supply caps, enhanced oracle validation, and committed to mandatory third-party audits for all future updates.
Who Should Care About Order-Book Lending
The fixed-rate model solves a real problem for three user types.
Leveraged yield farmers. If you are looping jitoSOL at 3x leverage, knowing your borrow cost upfront changes the math entirely. In a variable-rate system, your strategy can go from profitable to underwater in a single utilization spike. Fixed rates let you model the trade before you enter it.
Institutional or semi-institutional capital. Funds and treasuries that need predictable cash flows cannot tolerate variable DeFi rates. Fixed-term, fixed-rate lending is the product they have been waiting for. Loopscale's isolated risk model also means they can pick exactly which collateral exposures they are comfortable underwriting.
Long-tail collateral holders. If you hold LP tokens from Meteora, JLP from Jupiter Perps, or LSTs from smaller validators, most pool-based protocols will not accept them as collateral (or will haircut them heavily). Loopscale's order book lets individual lenders decide whether they are comfortable with that collateral, expanding the borrowable universe.
What Loopscale Does Not Solve
The order-book model is not strictly better than pooled lending. There are trade-offs.
Liquidity depth. A pooled system always has liquidity available (until utilization hits 100%). An order book can have gaps. If no lender is posting offers at the rate and duration you want, you wait. During low-activity periods, matching can be slow.
Complexity. Choosing rates, durations, and collateral types requires more sophistication than depositing into a Kamino vault. The vault product abstracts this away, but users who go direct need to understand what they are doing.
Track record. Loopscale is 14 months old, had a significant exploit in its first month, and carries roughly $100M in TVL. Kamino has $3B+ and years of operation. Jupiter Lend has the backing of the largest Solana ecosystem. Scale and time are their own form of security.
Idle capital. Funds sitting in the order book waiting for a match earn nothing from Loopscale itself. The protocol routes idle vault capital to partner protocols (like MarginFi or Adrena) to mitigate this, but the underlying issue remains: order books are only efficient when there is sufficient two-sided flow.
yieldwire's Take
Loopscale is the most architecturally distinct lending protocol on Solana right now. The order-book model is not new in TradFi, but deploying it on-chain with fixed rates, isolated risk, and composable leverage is a genuine product innovation.
The yields are real but layered. The 10-12% vault numbers include strategy alpha and incentive programs. The base fixed-rate lending sits closer to 5-8% for stablecoins, which is still competitive.
The exploit history is a flag but not a disqualifier. Full recovery within 72 hours, transparent communication, and structural improvements post-incident are the right response. The oracle vulnerability was in exotic collateral pricing, not in the lending engine.
We rate Loopscale's security score as pending a full reassessment. The pre-launch OShield audit covered code but missed the oracle vector. Additional audits are in progress. Until those complete, position sizing matters more than usual.
For yield seekers: Loopscale is worth monitoring for its fixed-rate products and vault strategies. For builders: the order-book primitive opens design space that pool-based lending cannot reach. For everyone: this is still a young protocol with meaningful risk. Size accordingly.
See the live Loopscale profile: yieldwire.xyz/protocol/loopscale.
Methodology
TVL and deposit figures sourced from DeFiLlama and Loopscale's public documentation as of June 1, 2026. USDC rates for Kamino, Jupiter Lend, Save, and Lulo sourced from yieldwire's direct API integrations. Loopscale vault APYs sourced from Loopscale's app interface and Nansen Research. Exploit details sourced from Blockworks, AuditOne, and Loopscale's official X account (@Loopscale). Audit information from OShield's published report on GitHub. Comparison rates are snapshots and will fluctuate.
This is not financial advice. Loopscale is a relatively young protocol (launched April 2025) that experienced a $5.8M exploit in its first month. All funds were recovered, but the incident underscores the risks of DeFi lending. Past yields are not indicative of future returns. Always conduct your own due diligence before depositing funds into any DeFi protocol.
Track all Solana yields in real time
Compare APYs across lending, LP, and liquid staking protocols on the YieldWire dashboard.
Open Dashboard →