The same lending engine is now running behind three different logos
Coinbase, Uniswap and Crypto.com each ship a lending or borrowing button with their own branding on it. The documented integrations keep pointing at one shared backend, and that is a risk question.
By Staff, Lend Ledger
Deposited assets can be lost entirely — to a counterparty failure, to a liquidation, or to a smart contract behaving in a way nobody intended. Which of those three is the live risk depends on what is actually holding the money. On a growing number of consumer apps, that is no longer the company whose name is on the button.
The documented integrations
Three are on the record, and they are worth reading together.
Coinbase. Reporting published on 20 April 2026 states that Coinbase’s crypto-backed borrowing rolled out to UK users with loans issued through Morpho on Base, accepting bitcoin, ether and cbETH as collateral. The same report puts total originations through the US product on Morpho above $2.17 billion in USDC as of 14 April 2026 — a dated figure, not a running total.
Uniswap. Earn launched on 31 July 2026, routing USDC, USDT and ETH deposits into Morpho vaults curated by Gauntlet, in a separate crypto.news report published that day.
Crypto.com. Morpho’s own case study says Crypto.com embedded Cronos USDC Vaults curated by Steakhouse directly into its DeFi Lending product. Read it with the dates in mind. The page marks that vault integration as live, and separately sets out a further Cronos expansion — Morpho-powered lending and borrowing — as a Q4 2025 plan, with Ketat Sarakune, quoted there as head of yield and asset growth, saying USDC Earn is live today and that expanding to Cronos comes next. That plan is dated well before this piece and the page has not been updated since, so only the vault integration should be read as running today.
The page’s term for what Crypto.com set out to build is a “DeFi mullet”: a sleek fintech interface in the front, decentralised infrastructure in the back.
What the arrangement changes
Not the mechanics of any individual product. What it changes is the answer to a question a user in these apps is unlikely to ask: who is the counterparty?
We would not assert that this constitutes systemic risk, and nobody should. The exposures here are related rather than identical: different curators set different allocation policies, the deployments sit on different chains, and the collateral sets differ. But a shared contract layer is a shared upgrade surface, and a class of failure in it would not respect the branding on the screens above it.
What a user ought to establish before depositing: which protocol holds the position, who curates the allocation, on which chain, and what triggers a liquidation. In a custodial arrangement none of that is visible; here it is, if anyone thinks to look.
None of the above is a comment on the soundness of any firm named, and none of it is financial advice.