Morpho vs Fluid (Instadapp) Morpho leads by 5 points.
Morpho scores 5 points above Fluid (Instadapp), led by oracle liquidation price, blast radius, and rate authorship. Morpho ranks #3 and Fluid (Instadapp) #7 of 8 published lending & borrowing. Every term of the gap is on the ledger below; the inputs are on the audit receipt.
Morpho78
vs
Fluid (Instadapp)73
Scores are out of 100; published scores fall within 41–99 · ranks #3 and #7 of 8
Morpho scores 5 points above Fluid (Instadapp), led by oracle liquidation price, blast radius, and rate authorship.
Morpho #3 of 878
Fluid (Instadapp) #7 of 873
Scores are out of 100; published scores fall within 41–99; a bar is empty at 41 and full at 99.
Why, term by termMorpho leads on 3 of 4 published criteria; Fluid (Instadapp) on 0. The terms sum to the gap.
TermMorphoFluid (Instadapp)WeightPoints
Oracle liquidation price7/106/107.7+2.0for Morpho+1.0 of 32
Blast radius9/108/105.8+1.5for Morpho+0.8 of 32
Rate authorship9/108/105.8+1.5for Morpho+0.8 of 32
Net of the terms+5.0
Criteria roundingThe criteria block is rounded to whole points before it is spread−0.1
Reproduced gap+4.9
Published gapAfter score rounding and bounds — see the note below7873+5.0
Weight is in points of the 86-point weighted total. Points are score points of the gap between the two.
MorphoScore 78A permissionless isolated-market primitive deployed on 14 chains where the oracle, the interest-rate model and the liquidation LLTV are chosen once at market creation and can never be changed — so Morpho publishes no deviation threshold and no heartbeat anywhere, but does publish, per market and continuously, the exact oracle contract that liquidates you, a documented degraded-state regime for when that oracle reverts, and the exact dollar figure of bad debt sitting in each market.Strength: Rate authorship — 9/10Watch-out: Before you supply, run Morpho's own bad-debt query with the listed filter OFF — and note that the filter, not the risk, is what changes. Morpho publishes a per-market outstanding bad-debt figure through https://api.morpho.org/graphql, which is more than most of this category does, but the curated view lies by omission: across the 590 markets Morpho marks listed, outstanding bad debt on 2026-08-17 was $0.00 against $4.42bn of borrows; drop that one flag and the same API at the same moment reports 27 markets carrying $255,015,878.47, every single one of them listed=false — $88.2M in wstUSR/USDC on Ethereum, $86.9M in xUSD/USDC on Arbitrum One, $28.8M in RLP/USDC and $23.0M in sdeUSD/USDC on World Chain, a chain on which Morpho has no listed markets at all. Morpho has published no post-mortem for any of it; its own newsletter for the month those losses formed (https://morpho.org/blog/morpho-effect-november-2025, 01 Dec 2025) does not contain the words 'bad debt', 'loss', 'deficit' or 'incident' once (fourteen such terms were checked, each zero times) and instead reports that "Curators are generating $300,000 in fees per week". The mechanism that produced those numbers is the one you are buying: Morpho does not choose oracles — "Market curators (not Morpho) are responsible for selecting and implementing appropriate oracles for their markets." — and it explicitly supports "Fixed-Price Oracles" that report a constant, so a collateral token can be marked at $1 in the contract while trading at five cents. Morpho documents exactly what happens if that feed REVERTS (borrow and liquidate stop, lenders and repaying borrowers can still exit) at https://docs.morpho.org/curate/concepts/security-considerations, but nothing at all catches a feed that keeps answering with the wrong number, and the kill switch that would is something the same page tells the CURATOR to build. Two smaller things to check before signing: if your vault was minted by the MetaMorpho Factory V1.1 it "do[es] not realize bad debt", so its share price will look clean while a loss sits inside it and the first person out is paid at your expense; and on three of the four largest Ethereum Vault V2s — which share one curator address and one owner address and held ~$1.05bn between them on 2026-09-28 — setPerformanceFee and setManagementFee carry a 0-second timelock, so the 50%-of-yield and 5%-of-assets caps can be reached with no notice at all, whatever the docs say about "a window to exit".Fluid (Instadapp)Score 73Shared-liquidity money market where collateral and debt can sit inside a Fluid DEX position; publishes per-vault oracle contract, LTV, liquidation threshold, penalty and absorbed bad debt live via its own API, and disclosed a ~$21M Resolv-driven shortfall (incident 22 Mar 2026) on its governance forum in amounts its own marketing recap then restates as $9.7M and attributes to the wrong payer.Strength: Rate authorship — 8/10Watch-out: Read the Resolv post-mortem on the governance forum, not the recap on the blog — they do not agree, and each omits what the other has. https://gov.fluid.io/t/post-mortem-treasury-actions-and-forward-strategy-following-resolv-incident/1774 (11 May 2026) states 'Fluid incurred ~$21M in bad debt due to the Resolv incident' and splits the remaining ~$19.3M as ~$9.7M Resolv / ~$8.2M Fluid governance treasury / ~$1.5M team, but never dates the event. The H1 2026 recap on fluid.io (5 Aug 2026) dates it — 'On March 22nd, a malicious actor gained unauthorized access to Resolv's signing infrastructure, minting approximately $80M of uncollateralized USR' — then restates the loss as 'The resulting shortfall — about $9.7M, or roughly 10% of total exposure — was covered directly from the DAO treasury.' That figure is Resolv's share presented as the whole loss and attributed to the wrong payer, at under half the number Fluid gave its own DAO. The mechanism that produced it is still the one you are underwriting: Fluid's own risk page says the oracle takes a Uniswap TWAP, runs a 'difference check' against Chainlink and falls back 'If the TWAP is within parameters' without ever stating what those parameters are; 'heartbeat' appears on none of the 46 pages of Fluid's buyer-facing GitBook and only as an unvalued rebalance condition in its autogenerated contract docs; and the one numeric deviation figure Fluid has published — 'revert all operates if deviation > 2%' — is by its own wording operate-only and therefore does not constrain the price that liquidates you.
Quick facts
At a glance
3 of 4 rows read the same for both.
FactMorphoFluid (Instadapp)
PricingSnapshotA Morpho depositor's cost is the vault curator's fee. The Vault V2 page (https://docs.morpho.org/learn/concepts/vault-v2/, fetched 28 September 2026) caps it: "Supports both a performance fee (up to 50% on yield) and a management fee (up to 5% on total assets)." Live values are API fields, not page text: https://api.morpho.org/graphql on 28 September 2026 returned performanceFee 0 and managementFee 0.009999999973584 on Paypal USD Main, 0.1 and 0 on Sentora RLUSD Main, and 0.15 and 0 on Sentora PRIME Main - three of the four largest Ethereum Vault V2s. On all three the setPerformanceFee and setManagementFee timelocks read 0 seconds, so the curator can change the fee without notice. Supply rates float with each market's AdaptiveCurveIRM, so no fixed APY is quoted.Fluid's guides publish no fee schedule for lenders or borrowers; the costs are the floating rate and, if liquidated, a per-vault liquidation penalty. The Liquidity Layer page (https://fluid.guides.instadapp.io/liquidity-layer/unifying-liquidity, fetched 28 September 2026) states: "Fluid boasts the most advanced liquidation mechanisms, with penalties as low as 0.1%." The live penalties and rates are API fields, not page text: https://api.fluid.instadapp.io/v2/borrowing/1/vaults on 28 September 2026 returned liquidationPenalty 10 basis points (the 0.1% floor) on the wstETH/ETH vault (id 13) and 100 basis points on the ETH/USDC (id 11) and ETH/USDT (id 12) vaults, with borrow rates of 243, 584 and 567 basis points and a vault feeRate of 0 on all three. Rates float with utilisation, so no fixed APY is quoted.
Asset coverageEditorial——
Region fitSnapshotglobalglobal
Custody modelEditorialNon-custodial: no company holds the coinsNon-custodial: no company holds the coins
From the published criteria
Which should you pick?
Morpho
78#3 of 8
Leads
Pick it when
Pick Morpho if oracle liquidation price matters most — it scores 7/10 to Fluid (Instadapp)'s 6/10 there (weight 32).
Strength
Rate authorship — 9/10
Tradeoff
Before you supply, run Morpho's own bad-debt query with the listed filter OFF — and note that the filter, not the risk, is what changes. Morpho publishes a per-market outstanding bad-debt figure through https://api.morpho.org/graphql, which is more than most of this category does, but the curated view lies by omission: across the 590 markets Morpho marks listed, outstanding bad debt on 2026-08-17 was $0.00 against $4.42bn of borrows; drop that one flag and the same API at the same moment reports 27 markets carrying $255,015,878.47, every single one of them listed=false — $88.2M in wstUSR/USDC on Ethereum, $86.9M in xUSD/USDC on Arbitrum One, $28.8M in RLP/USDC and $23.0M in sdeUSD/USDC on World Chain, a chain on which Morpho has no listed markets at all. Morpho has published no post-mortem for any of it; its own newsletter for the month those losses formed (https://morpho.org/blog/morpho-effect-november-2025, 01 Dec 2025) does not contain the words 'bad debt', 'loss', 'deficit' or 'incident' once (fourteen such terms were checked, each zero times) and instead reports that "Curators are generating $300,000 in fees per week". The mechanism that produced those numbers is the one you are buying: Morpho does not choose oracles — "Market curators (not Morpho) are responsible for selecting and implementing appropriate oracles for their markets." — and it explicitly supports "Fixed-Price Oracles" that report a constant, so a collateral token can be marked at $1 in the contract while trading at five cents. Morpho documents exactly what happens if that feed REVERTS (borrow and liquidate stop, lenders and repaying borrowers can still exit) at https://docs.morpho.org/curate/concepts/security-considerations, but nothing at all catches a feed that keeps answering with the wrong number, and the kill switch that would is something the same page tells the CURATOR to build. Two smaller things to check before signing: if your vault was minted by the MetaMorpho Factory V1.1 it "do[es] not realize bad debt", so its share price will look clean while a loss sits inside it and the first person out is paid at your expense; and on three of the four largest Ethereum Vault V2s — which share one curator address and one owner address and held ~$1.05bn between them on 2026-09-28 — setPerformanceFee and setManagementFee carry a 0-second timelock, so the 50%-of-yield and 5%-of-assets caps can be reached with no notice at all, whatever the docs say about "a window to exit".
Fluid (Instadapp)
73#7 of 8
Pick it when
Fluid (Instadapp) leads Morpho on no published criterion and no score dimension — pick it only if a fact outside the score (country, funding rail, custody) decides for you.
Strength
Rate authorship — 8/10
Tradeoff
Read the Resolv post-mortem on the governance forum, not the recap on the blog — they do not agree, and each omits what the other has. https://gov.fluid.io/t/post-mortem-treasury-actions-and-forward-strategy-following-resolv-incident/1774 (11 May 2026) states 'Fluid incurred ~$21M in bad debt due to the Resolv incident' and splits the remaining ~$19.3M as ~$9.7M Resolv / ~$8.2M Fluid governance treasury / ~$1.5M team, but never dates the event. The H1 2026 recap on fluid.io (5 Aug 2026) dates it — 'On March 22nd, a malicious actor gained unauthorized access to Resolv's signing infrastructure, minting approximately $80M of uncollateralized USR' — then restates the loss as 'The resulting shortfall — about $9.7M, or roughly 10% of total exposure — was covered directly from the DAO treasury.' That figure is Resolv's share presented as the whole loss and attributed to the wrong payer, at under half the number Fluid gave its own DAO. The mechanism that produced it is still the one you are underwriting: Fluid's own risk page says the oracle takes a Uniswap TWAP, runs a 'difference check' against Chainlink and falls back 'If the TWAP is within parameters' without ever stating what those parameters are; 'heartbeat' appears on none of the 46 pages of Fluid's buyer-facing GitBook and only as an unvalued rebalance condition in its autogenerated contract docs; and the one numeric deviation figure Fluid has published — 'revert all operates if deviation > 2%' — is by its own wording operate-only and therefore does not constrain the price that liquidates you.
Self-identify in 10 seconds
Which one is actually for you?
MorphoLeads
Choose Morpho if oracle liquidation price matters most
Oracle liquidation price: 7/10 against 6/10 for Fluid (Instadapp) (weight 32)
Rate authorship: 9/10 against 8/10 for Fluid (Instadapp) (weight 24)
Blast radius: 9/10 against 8/10 for Fluid (Instadapp) (weight 24)
MorphoScore 78A permissionless isolated-market primitive deployed on 14 chains where the oracle, the interest-rate model and the liquidation LLTV are chosen once at market creation and can never be changed — so Morpho publishes no deviation threshold and no heartbeat anywhere, but does publish, per market and continuously, the exact oracle contract that liquidates you, a documented degraded-state regime for when that oracle reverts, and the exact dollar figure of bad debt sitting in each market.Strength: Rate authorship — 9/10Watch-out: Before you supply, run Morpho's own bad-debt query with the listed filter OFF — and note that the filter, not the risk, is what changes. Morpho publishes a per-market outstanding bad-debt figure through https://api.morpho.org/graphql, which is more than most of this category does, but the curated view lies by omission: across the 590 markets Morpho marks listed, outstanding bad debt on 2026-08-17 was $0.00 against $4.42bn of borrows; drop that one flag and the same API at the same moment reports 27 markets carrying $255,015,878.47, every single one of them listed=false — $88.2M in wstUSR/USDC on Ethereum, $86.9M in xUSD/USDC on Arbitrum One, $28.8M in RLP/USDC and $23.0M in sdeUSD/USDC on World Chain, a chain on which Morpho has no listed markets at all. Morpho has published no post-mortem for any of it; its own newsletter for the month those losses formed (https://morpho.org/blog/morpho-effect-november-2025, 01 Dec 2025) does not contain the words 'bad debt', 'loss', 'deficit' or 'incident' once (fourteen such terms were checked, each zero times) and instead reports that "Curators are generating $300,000 in fees per week". The mechanism that produced those numbers is the one you are buying: Morpho does not choose oracles — "Market curators (not Morpho) are responsible for selecting and implementing appropriate oracles for their markets." — and it explicitly supports "Fixed-Price Oracles" that report a constant, so a collateral token can be marked at $1 in the contract while trading at five cents. Morpho documents exactly what happens if that feed REVERTS (borrow and liquidate stop, lenders and repaying borrowers can still exit) at https://docs.morpho.org/curate/concepts/security-considerations, but nothing at all catches a feed that keeps answering with the wrong number, and the kill switch that would is something the same page tells the CURATOR to build. Two smaller things to check before signing: if your vault was minted by the MetaMorpho Factory V1.1 it "do[es] not realize bad debt", so its share price will look clean while a loss sits inside it and the first person out is paid at your expense; and on three of the four largest Ethereum Vault V2s — which share one curator address and one owner address and held ~$1.05bn between them on 2026-09-28 — setPerformanceFee and setManagementFee carry a 0-second timelock, so the 50%-of-yield and 5%-of-assets caps can be reached with no notice at all, whatever the docs say about "a window to exit".
Fluid (Instadapp)
Fluid (Instadapp) leads Morpho on no published criterion
Choose it only if something outside the published criteria decides for you — your country, a funding rail, or custody.
Fluid (Instadapp)Score 73Shared-liquidity money market where collateral and debt can sit inside a Fluid DEX position; publishes per-vault oracle contract, LTV, liquidation threshold, penalty and absorbed bad debt live via its own API, and disclosed a ~$21M Resolv-driven shortfall (incident 22 Mar 2026) on its governance forum in amounts its own marketing recap then restates as $9.7M and attributes to the wrong payer.Strength: Rate authorship — 8/10Watch-out: Read the Resolv post-mortem on the governance forum, not the recap on the blog — they do not agree, and each omits what the other has. https://gov.fluid.io/t/post-mortem-treasury-actions-and-forward-strategy-following-resolv-incident/1774 (11 May 2026) states 'Fluid incurred ~$21M in bad debt due to the Resolv incident' and splits the remaining ~$19.3M as ~$9.7M Resolv / ~$8.2M Fluid governance treasury / ~$1.5M team, but never dates the event. The H1 2026 recap on fluid.io (5 Aug 2026) dates it — 'On March 22nd, a malicious actor gained unauthorized access to Resolv's signing infrastructure, minting approximately $80M of uncollateralized USR' — then restates the loss as 'The resulting shortfall — about $9.7M, or roughly 10% of total exposure — was covered directly from the DAO treasury.' That figure is Resolv's share presented as the whole loss and attributed to the wrong payer, at under half the number Fluid gave its own DAO. The mechanism that produced it is still the one you are underwriting: Fluid's own risk page says the oracle takes a Uniswap TWAP, runs a 'difference check' against Chainlink and falls back 'If the TWAP is within parameters' without ever stating what those parameters are; 'heartbeat' appears on none of the 46 pages of Fluid's buyer-facing GitBook and only as an unvalued rebalance condition in its autogenerated contract docs; and the one numeric deviation figure Fluid has published — 'revert all operates if deviation > 2%' — is by its own wording operate-only and therefore does not constrain the price that liquidates you.
Criterion by criterion
Scorecard
Published criteria · weight in points of 868 of 8 cells scored. Strength is read from the evidence file; the weight is the published one. Methodology
Oracle liquidation price
by 1 of 10weight 7.7 of 86Morpho leads
Morpho7/10 out of 10
Fluid (Instadapp)6/10 out of 10
Rate authorship
by 1 of 10weight 5.8 of 86Morpho leads
Morpho9/10 out of 10
Fluid (Instadapp)8/10 out of 10
Blast radius
by 1 of 10weight 5.8 of 86Morpho leads
Morpho9/10 out of 10
Fluid (Instadapp)8/10 out of 10
Shortfall record
weight 4.8 of 86Tie
Morpho7/10 out of 10
Fluid (Instadapp)7/10 out of 10
Score dimensions
weights sum to 86
The published score is five dimensions, each weighted for the category. "Published criteria" is the criteria block above; the other four are the engine's own terms — availability, friction, trust record, measured data. Each bar is one side's points out of that dimension's maximum; the weight beside the name is its points of the 86-point weighted total. The published criteria above can fill 24 of the block’s 30. A weight marked “constant here” belongs to a dimension every ranked product in the category holds at the same value: it still counts in the total, and it orders nothing here.
Availabilityweight 20 of 86 · constant here
Morpho14/20Fluid (Instadapp)14/20
Tie
Published criteriaweight 30 of 86
Morpho19.1/30Fluid (Instadapp)17.2/30
Morpho leads
Frictionweight 10 of 86 · constant here
Morpho2.7/10Fluid (Instadapp)2.7/10
Tie
Trust recordweight 8 of 86 · constant here
Morpho3.2/8Fluid (Instadapp)3.2/8
Tie
Measured dataweight 18 of 86 · constant here
Morpho8.3/18Fluid (Instadapp)8.3/18
Tie
Decision rulePublished order
Choose Morpho unless the term Fluid (Instadapp) leads on is the one you are buying.
Fluid (Instadapp) leads Morpho on no published criterion and no score dimension — pick it only if a fact outside the score (country, funding rail, custody) decides for you.
The published order weighs every criterion the same way for everyone. To weigh them your way, run .
From the published order
Next best action
If this isn't your case
Other matchups worth comparing
How you can lose money here, and what the ranking scores
Control failure: a key or vote changes the rules, freezes or mints.
Scored by Who sets your rate — a utilisation curve or a curator? · 24% (Morpho 9/10, Fluid (Instadapp) 8/10)
Oracle failure: a wrong price or outcome liquidates or settles a position.
Scored by What price gets you liquidated, and how far can it drift? · 32% (Morpho 7/10, Fluid (Instadapp) 6/10)
Insolvency failure: the firm or issuer that owes you cannot pay.
Scored by If one market goes bad, how much of yours goes with it? · 24% (Morpho 9/10, Fluid (Instadapp) 8/10)
Scored by Has it lost lender money before, and did it publish it? · 20% (Morpho 7/10, Fluid (Instadapp) 7/10)
Not assessed by this ranking: Contract failure, Regulatory failure, Execution failure, Exit failure. A high place says nothing about these; the Methodology tab says what each means.
Questions
Frequently asked questions
Morpho scores 5 points above Fluid (Instadapp), led by oracle liquidation price, blast radius, and rate authorship. Published scores, out of 100: Morpho 78 (rank 3 of 8 lending & borrowing), Fluid (Instadapp) 73 (rank 7 of 8).
Reviewed means both products compared here was read against its sources on or after that date; every ranked category is re-read at least every 45 days. Models research, extract and parse. A deterministic engine ranks. Every quote passes an adversarial refute pass.
Answer a few quick questions and get one clear recommendation based on how you actually plan to use crypto — with rationale, tradeoffs, and a path to monitor the decision.
No signup·Free first pass · Private·No spam · No account
Not financial advice · Independent · Always do your own research
Not financial advice · For informational purposes only · Always do your own research
