Skip to content

Morpho Integration for Firms That Put Morpho Vaults Behind Their Own App

Protofire builds the parts Morpho leaves to a firm that puts Morpho vaults behind its own app. Vault roles go on the firm's keys, curator changes are watched, and client shares and losses are booked. We are a Chainlink core contributor, and in 2025 we built Somnia's Chainlink-compatible oracle stack.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. Curator changes and bad debt
  3. Morpho facts
  4. What you get
  5. Roles and timelocks
  6. Liquidation losses
  7. Our oracle record
  8. Deposit to booked share
  9. How work starts
  10. Not the right fit
  11. Related guides and services
  12. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

Who holds what in a Morpho integration

In a Morpho integration, Morpho's contracts keep the positions, and your firm keeps the clients, wallets and records. Morpho's Disclaimer says the Morpho Association and its contributors "do not hold, custody, manage, or control users' digital assets at any time".

For example, your app takes client deposits into a Morpho vault. A curator then queues a risk change that you did not see. A liquidation leaves bad debt that lowers the vault's share price. Your ledger holds no entry for either event.

Who owns each part, from the firm's app to Morpho's vaults

The firm's wallet signs each deposit. Services that Protofire builds read shares, losses and pending curator changes back into the firm's records.

The firm

Client app

The app shows the screens, the Powered by Morpho badge and the acknowledgment.

Wallets and signer

The firm holds omnibus or per-client wallets and the signer.

Ledger and statements

The ledger records client shares, share-value marks, losses and the close.
Morpho's contracts

Blue markets

Each market's oracle and liquidation LTV are fixed at creation.

Vault V2

The vault has adapters, caps, per-function timelocks and an in-kind exit.
Curator and vault roles

Owner and sentinels

The owner appoints the curator, and sentinels cancel changes and cut caps.

Curator and allocators

The curator submits risk changes, and allocators allocate within caps.
Protofire builds

Transaction service and booking

The service prepares unsigned transactions for the firm's wallet and books shares and losses.

Change watcher

The watcher sends pending curator changes as alerts.

Curator changes and bad debt reach your ledger late

A curator's change and a liquidation loss both change a client's Morpho position.Each event needs a ledger entry and a line the client can read.

A curator's queued change takes effect once its timelock ends, and anyone can execute the change. Timelocks are set per function. Morpho's docs say a timelock "can be set to zero at deployment", and the default is 0. With a zero timelock, a change can arrive with no wait.

A liquidation that leaves bad debt lowers a Vault V2 share price, and the vault's shareholders bear the loss (Vault V2 bad debt).

What Protofire builds in a Morpho integration

Vault roles assigned to your own keys

You know who can change a client's vault. Protofire maps the owner, curator, sentinel and allocator roles to your Safe, MPC wallet or bot key. We plan each function's timelock and prepare the deployment transactions for your keys to sign.

Alerts to your risk owner on each curator change

Your risk owner gets an alert for each pending submission with its executable time, and for each revocation, cap cut and gate change. Protofire builds the change watcher, which checks the oracle and LLTV of each new market that an adapter can reach. In a curator's vault, the way out of a change you reject is a withdrawal before the change's timelock ends.

Deposits checked against the vault's limit and signed by your wallet

A client request is checked against the vault's limit before a transaction exists. Protofire builds the transaction service, which prepares unsigned deposits, withdrawals and borrows for your wallet to sign.

Client shares and losses that match the chain

Statements show each client's shares, their value at your cut-off and each liquidation loss. Protofire builds the booking service, which matches an omnibus wallet's shares to a client subledger each day.

The Powered by Morpho badge and the user notice

Morpho's docs require a "Powered by Morpho" badge where users act on Morpho. The docs also require a notice that each user acknowledges before first use (UX rules). Protofire builds the screens and stores each acknowledgment with the client ID, the notice version and the time.

Market data that keeps working after the GraphQL shutdown

Dashboards read the REST API through a cache that keeps requests under Morpho's rate limit. If you need a private key, you request it, and the key is kept in your vault.

Who can change a Morpho vault's risk or cancel a pending change

On a Vault V2, the curator submits risk changes, and each change waits out its timelock.The curator or a sentinel can revoke a pending change before it executes (emergency guide). Protofire holds none of these roles after launch.

Owner

What it can do, and its delay: Appoints the curator and sentinels and transfers ownership. No timelock is listed.

Holder in a firm's own vault: The firm, on a multisig such as 4-of-6 or an MPC wallet (roles)

Curator

What it can do, and its delay: Adds adapters, raises caps, sets fees, gates and the exit penalty, and changes timelocks. Each function has its own timelock, and cap cuts are instant.

Holder in a firm's own vault: The firm's risk team or a curator it appoints, on a multisig or MPC wallet

Allocator

What it can do, and its delay: Moves assets between enabled adapters within caps. It acts at once.

Holder in a firm's own vault: A bot key or a fast multisig the firm controls

Sentinel

What it can do, and its delay: Revokes pending curator actions, cuts caps and pulls assets back to idle. It acts at once.

Holder in a firm's own vault: The firm, or a third party it names

Anyone

What it can do, and its delay: Executes a curator change after its timelock, and triggers forceDeallocate with the penalty.

Holder in a firm's own vault: The firm's own service can do both.

A regulator should aim to identify the persons and entities of a purported DeFi arrangement that could be subject to its applicable regulatory framework (Responsible Person(s)).
International Organization of Securities Commissions (IOSCO), Final report with policy recommendations, International body of securities regulators · Final Report with Policy Recommendations for Decentralized Finance (DeFi), FR/14/2023, Recommendation 2, December 2023

How a Morpho liquidation loss reaches a client's statement

A Morpho liquidation becomes a lender's loss when it leaves debt with no collateral behind it.The market then cuts its supplied assets by that amount, and the market's suppliers share the loss.

Anyone can liquidate a Blue position at the oracle price once its loan-to-value exceeds the market's LLTV (liquidation). The Liquidate event includes badDebtAssets and badDebtShares (bad debt). Protofire's booking service reads these two fields as the loss record.

In a Vault V2, the adapter reports lower realAssets, and the vault marks its total down at the next accrual. No shares are burned, and "all shareholders absorb the loss equally". Bad debt counts at full value until a liquidation realizes it (Vault V2 bad debt).

Legacy Vault V1.1 works differently. Its share price holds, and "The last vault users will face the bad debt unless action is taken". A Vault V2 can allocate into a legacy V1.1 vault. In that case, the V2 share price does not show the V1.1 vault's bad debt until the V1.1 vault itself accounts for it.

A borrowing client's loan-to-value is read at the market's own oracle price. Morpho says "Market curators (not Morpho)" choose each oracle, and the oracle cannot be replaced after the market's creation (oracle). The market's suppliers and the vault's shareholders bear the loss.

How a deposit request becomes a booked share

  1. Step 1

    The service computes the deposit limit from vault state

    Vault V2's maxDeposit view returns zero by design, so the view cannot size a deposit (Vault V2 reference). Protofire's service computes the limit from vault state with the Morpho SDK. When a request exceeds the limit, the client sees a full-vault message.
  2. Step 2

    The service builds the transaction unsigned, and your wallet signs it

    The Morpho SDK routes vault writes through Morpho's Bundles. Your wallet signs the transaction and sends it.
  3. Step 3

    Each share is booked once and marked at your close

    The service books each share once, identified by chain ID, transaction hash and log index. After a timeout, the service reads the receipt and the wallet's nonce before a resend, because a blind resend could deposit twice. Each day, the service reads convertToAssets at the last block before your local cut-off. A drop from a realized loss posts as a loss, apart from interest accrual.
  4. Step 4

    The services run in your environment, on your keys

    The transaction service runs in your environment, and so does an allocator bot if you run one. The allocator key is kept in your key store, and both services act on rules that your firm signed. If you ask, Protofire's managed onchain operations service runs the watcher, position reads and booking feeds after launch. It works under a written scope that stops at reading Morpho.

How a Morpho project with Protofire starts

You send the vault model you plan, your wallet structure and the ledger that books client positions.Protofire's first written proposal maps each vault role to a key holder. The proposal also sets out the booking design and the watcher's alerts. The terms in this section apply to each phase, as set out on how we work.

Proposal
In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
Price
Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
Ownership
Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
After launch
Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
Access
Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
Licenses
Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.

How we work shows a worked proposal.

Three cases where another service gives you Morpho access

Another service, or a different project, fits better in three cases.

Protofire holds no financial or crypto-asset license. Licenses and client disclosures are matters for your firm and its advisers. So are curator choice, risk limits and legal opinions. The change watcher alerts you to a change but does not reverse it.

FAQ

What is a Morpho integration?
A Morpho integration connects a firm's app, wallets and ledger to Morpho's Blue markets and Vault V2 vaults. The app builds deposits as unsigned transactions for the firm's own signer. Services read shares, losses and pending curator changes back into the firm's books. Protofire builds the integration, and the firm or its curator holds the vault roles.
Who can build a Morpho integration for a fintech, a wallet or a fund?
Protofire, an engineering firm, builds the firm's own side of a Morpho integration. Protofire sets up the vault roles and builds the transaction service. Protofire also builds the change watcher and the booking service. The firm and its advisers choose the curator and set the risk limits, and Protofire holds no role in the vault after launch.
Which Vault V2 roles should a multisig hold?
Morpho's role guidance puts the owner and the curator on a multisig. For the owner, the guidance names a multisig such as 4-of-6 or an MPC wallet. For the curator, it names a 2-of-4 or 3-of-5 multisig. Morpho's docs call a single EOA "highly discouraged for production vaults" (roles).
What can a client do when a Morpho vault has no idle liquidity?
The client can still leave the vault through in-kind redemption. A normal withdrawal needs idle assets or free market liquidity. But when the vault is illiquid, "Users can still exit through in-kind redemption, with no action from the curator or allocator" (liquidity). The redemption runs through forceDeallocate, net of a penalty that the curator sets and the contract caps at 2% (Vault V2 reference). The client then holds a supply position in the underlying market and withdraws it once liquidity returns. A gate can block this path.
Can a firm limit a Morpho vault to verified clients?
Yes. A Vault V2 curator can set gate contracts on shares and assets, under a timelock (gates). The KYC rule behind the gate and the gate's administrator belong to the firm.
Does a firm need Morpho's permission to use the contracts?
No. Creating a Blue market is permissionless, and anyone can lend or borrow on one (Blue). The Morpho Association's Disclaimer applies to all Morpho interfaces that the Association does not own. A firm's own app is one of those interfaces (Disclaimer).
What happens to integrations built on Morpho's GraphQL API?
Integrations built on Morpho's GraphQL API stop working when Morpho shuts that API down. Morpho set the shutdown date as 29 January 2027 (API). The REST API replaces the GraphQL API. The REST API no longer lists Blue position health across a whole market (data guide). So a health monitor keeps its own list of client addresses.

Get a proposal

Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.