Sprinter

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

Sprinter, built by the ChainSafe team, lends pooled capital to cross-chain solvers so they can fill orders without pre-funding, while Stash manages LP capital across chain pools, rebalancing and netting rails and passive lending such as Aave. The solver-credit controls constrain use but do not let the depositor enforce a fixed advisor-approved venue allocation after deposit. That continuing portfolio management is more fundamental than the approximately $1.20M TVL observed on 2026-08-16, so the version-1 delegated-allocation dossier rejects Stash V1 at zero.

Kill criteria: the events that revoke this verdict
• Enforces an immutable client-specific allowlist and limits for solvers, chains, rebalancing rails and passive-yield venues, with debt, losses and allocations independently observable
• Demonstrates a proposed-size stressed redemption for the selected lock term through every active solver and strategy exposure without new subscriptions or manager substitution

The research file

Mechanism applicability

Sprinter Stash LPs deposit USDC on Base and receive spUSDC-LP. The pool supplies usage-constrained, zero-collateral credit to allowlisted cross-chain solvers, while capital can earn base yield through Aave. Sprinter states that liquidity is automatically managed across supported-chain pools using rebalancing and netting protocols. The depositor receives one claim while the system changes credit, venue and chain exposure after deposit, directly satisfying the shared delegated-allocation dossier.

Current observation and lifecycle

The DefiLlama protocol API read on 2026-08-15 classified Sprinter as Yield and reported approximately $1.19M on Base. Sprinter announced the live Stash app in November 2025 and now documents a broader Sprinter Credit V2 alongside Stash Solver Credit V1. This record remains scoped to the Base Stash liquidity measured by DefiLlama, not every destination chain or every newer credit product.

Control and exit applicability

Stash uses MPC validation, allowlisted routers, restricted transaction use and repayment-sink priority to constrain uncollateralized solver credit, but LPs still depend on solver repayment, MPC operation, contracts, Aave and cross-chain execution. Current materials describe no-lock deposits as well as 3-, 6- and 12-month lock choices. Redemption therefore depends on the selected lock and available pool liquidity rather than a guaranteed immediate par exit.

Why the class rule decides

MPC validation, allowlisted routers and repayment priority bound solver actions, but they do not freeze the LP portfolio to mandate-approved venues and caps: the system chooses solver credit, passive yield and cross-chain inventory paths after deposit. The version-1 delegated-allocation dossier therefore controls regardless of size. Reopen only if a named Stash pool enforces an immutable client-specific allowlist and limits, publishes independently verifiable solver, chain, venue, debt and loss exposure, and demonstrates proposed-size exits for every lock choice without new subscriptions; compare with direct approved lending positions.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Sprinter — Stash mechanism · primary · accessed 2026-08-15
  Supports: Base, USDC, spUSDC-LP, zero-collateral solver credit, MPC, Aave
• Sprinter — live Stash deposits and locks · primary · accessed 2026-08-15
  Supports: live app, USDC deposits, no lock, 3 6 12 month locks, solver repayment
• Sprinter — solver-credit controls · primary · accessed 2026-08-15
  Supports: usage constraints, allowlisted routers, repayment sink, MPC, audits
• Sprinter — current documentation lifecycle · primary · accessed 2026-08-15
  Supports: Sprinter Credit V2, Stash Solver Credit V1, current lifecycle, API
• DefiLlama — Sprinter survey record · secondary · accessed 2026-08-15
  Supports: current TVL, Base, Yield category, survey observation

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.