SpringX
SpringX automates yield and liquidity management on Plasma and Monad. DefiLlama measured $35,135 on 2026-08-16, only 0.04% of the size floor. It remains below that floor, so we do not open the individual review until it clears it. That review would cover strategy control, venue look-through, LP loss, valuation, and exits.
- TVL sustained above the retired TVL threshold for 30 days
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.
The research file
Materiality mechanism, applied
The size floor reflects capacity, not quality. A $2 million household with a 5-10% crypto sleeve and a 10-40% venue weight implies roughly $10,000 to $80,000 here. Across 100 similar clients, one practice can direct $1 million to $8 million to one venue based on the same research. Below the protocol TVL size floor, that book can overwhelm exits. TVL also overstates capacity because it does not promise an executable withdrawal: utilization, queues, unbonding, bridge depth, and token liquidity can leave less available than the headline figure suggests. Small size does not itself show weak governance or team quality. The class rule makes no such judgment. The problem is that strong controls cannot fix inadequate capacity for this distribution channel. We do not open the individual review until the protocol clears the size floor.
Mechanism applicability
SpringX markets one-click yield through automated liquidity management. Depositors therefore use a wrapper whose return depends on the selected downstream liquidity venues and their inventory, fees, tokens, and contract risks, rather than on a fixed protocol payment.
Control and assurance applicability
Strategy rules and supported venues control allocation and rebalancing. A published Shieldify review gives evidence about the code it covered. Public materials, however, do not give depositors control over downstream exposures, upgrades, pauses, or strategy changes.
Exit applicability
Redemption capacity depends on idle assets and successful exits from the underlying liquidity positions on the relevant chain. Aggregate TVL is not executable depth for a specific vault. Automated management does not guarantee an exit at par during an imbalance.
Why the dossier still applies
DefiLlama measured $35,135 across Plasma and Monad on 2026-08-16, 0.04% of the size floor. Reopen after TVL stays above the size floor for 30 days. Then map strategies, venues, privileged roles, NAV and loss rules, audits and incidents, and withdrawals at the proposed size.
Research status
This is a capacity-unproven record for SpringX, not a quality rejection or approval. Reported TVL says how big the venue is, not what the client owns, who can change the rules, or how a position exits at a proposed size. The individual review opens when the protocol clears the size floor.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- SpringX — official product site · primary · accessed 2026-08-16
Supports: automated liquidity management, yield product identity, current lifecycle - SpringX — live application · primary · accessed 2026-08-16
Supports: live vault interface, deposit perimeter, product availability - Shieldify — SpringX security review · primary · accessed 2026-08-16
Supports: security-review scope, published assurance record, code limitations - SpringX — official communications · primary · accessed 2026-08-16
Supports: Plasma and Monad lifecycle, official announcements, product changes - DefiLlama — SpringX survey record · secondary · accessed 2026-08-16
Supports: $35,135 TVL, Plasma and Monad perimeter, yield category
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| Plasma | Rejected | Issuer can freeze | the production validator committee is permissioned and the public docs still describe decentralization as a phased future rollout with no fixed access timeline. |
| Monad | Approved with limits | Governed, no freeze | the L1 has a public validator path, but its short production record, single initial client lineage, and Foundation-directed delegation keep stake and operations concentrated. |