Mystic Finance Lending
Mystic Finance Lending is not on the current firm shelf because its structure falls within the rejected-chain policy class. This is a firm policy decision, not a negative quality rating or a client trade instruction. The facts about its mechanism, control, loss, and exit remain below.
- Plume Mainnet passes independent review and is admitted to the supported settlement-chain set, and Mystic remains live on the reviewed deployment
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
Mechanism and chain applicability
Mystic’s current documentation describes core lending pools, curated vaults, tokenized-RWA collateral, and flash-loan leverage. Its core-pool materials place the product on Plume, and its oracle documentation identifies Plume contract feeds. These facts show that the application operates and settles on Plume Mainnet, a chain absent from the reviewed ChainId set. The rejected-chain rule therefore applies before we consider the quality of the lending protocol itself.
Current observation
The DefiLlama protocol API read on 2026-08-15 reported approximately $4.7M of Mystic Finance Lending TVL. It attributed the live balance to Plume Mainnet, not the stale Flare label in earlier research. Mystic’s current site continued to advertise supply, borrow, leverage, and vault curation. This observation proves only that the product is current and runs on that chain. It does not validate reserves, oracle marks, borrower credit, or executable liquidity.
Control and exit applicability
Mystic documents supply and withdrawal actions, pool caps, isolation mode, curator-managed vault allocation, Stork and eOracle price feeds, and liquidations when health factor reaches one. It also offers one-click leveraged RWA exposure through flash borrowing and DEX swaps. These controls and exits rely on Plume execution, contracts, oracles, and liquidity. They cannot be separated from the unreviewed settlement-chain dependency.
Why the class rule decides
The shared v1 rejected-chain dossier governs while Mystic’s live product settles on Plume Mainnet. Reopen only after an independent review admits Plume to the chain set and Mystic remains live there. The individual review must then cover curators and governance, pool assets and legal claims, oracles, caps and liquidations, contracts and audits, incidents, fees, leverage paths, withdrawal liquidity, and stressed RWA collateral realization.
Class rule
The rejected chain class is outside the approved structures, so every protocol in it is not approved until the rule changes. The rule is about the structure, not an adverse finding about this protocol, and it is not a client instruction. The events that would reopen it are listed with the memo.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Mystic Finance Docs — current protocol components · primary · accessed 2026-08-15
Supports: curated vaults, RWA lending, leverage strategies, Plume ecosystem, liquid staking - Mystic Finance Docs — core pools on Plume · primary · accessed 2026-08-15
Supports: Plume deployment, core lending pools, isolation mode, supply caps, borrow caps - Mystic Finance Docs — supply, withdrawal and liquidation tutorials · primary · accessed 2026-08-15
Supports: Plume contracts, supply, withdrawal, borrow, liquidation, curator controls - DefiLlama — Mystic Finance Lending survey record · secondary · accessed 2026-08-15
Supports: current TVL, Plume Mainnet, lending category, survey perimeter
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 |
|---|