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.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
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.
Client app
Wallets and signer
Ledger and statements
Blue markets
Vault V2
Owner and sentinels
Curator and allocators
Transaction service and booking
Change watcher
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).
Morpho's legal entity, markets, vaults and API
- Who stands behind Morpho
- The Morpho Association. Its Disclaimer of 17 March 2026 says the Association, its subsidiaries and contributors "do not operate a financial service, exchange, brokerage, or crypto-asset service provider within the meaning of applicable regulations".
- Markets
- Variable Rate Markets (Blue) pair one collateral asset with one loan asset. Each market's oracle and LLTV are fixed at creation (Blue).
- Vaults
- Vault V2 is "the recommended vault surface" for new integrations. Vaults V1 "are now legacy".
- Data
- The REST API at api.morpho.org allows 750 requests a minute per IP. Morpho set 29 January 2027 as the shutdown date of its GraphQL API (API).
Checked November 2026 against Morpho's documentation and the Morpho Association's Disclaimer. Protofire integrates Morpho for firms that have chosen it. The Morpho Association has not reviewed this page.
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)).
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.
Our record: Chainlink core contribution and Somnia's oracle stack
Each Morpho market fixes its oracle permanently, so Protofire's oracle work applies to a Morpho integration.
Chainlink core contributor
Protofire is a Chainlink core contributor. Morpho's docs name Chainlink among the price feeds that a market oracle can use. The docs also tell users to verify a market's oracle (oracle).
Somnia's Chainlink-compatible oracle stack, 2025
In 2025 Protofire built Somnia's Chainlink-compatible oracle stack. Five oracle nodes in OCR consensus backed three mainnet price feeds and VRF. We operated the stack until the engagement ended in late 2025. The Somnia oracle case and our oracle integration page give the details.
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.
- A Fireblocks customer wants Morpho vaults. Fireblocks offers select Morpho vaults through its Earn product. Our Fireblocks integration page covers the custody side.
- An app lends USDC on Base. Coinbase's developer platform wraps an approved curated vault, and the platform's docs name Morpho as the sole supported protocol.
- You want a lending market of your own, or on your own chain. Then you need white-label lending, which is a separate job.
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?
Who can build a Morpho integration for a fintech, a wallet or a fund?
Which Vault V2 roles should a multisig hold?
What can a client do when a Morpho vault has no idle liquidity?
Can a firm limit a Morpho vault to verified clients?
Does a firm need Morpho's permission to use the contracts?
What happens to integrations built on Morpho's GraphQL API?
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.
