TL;DR
- After depositing into a curated vault, an institutional allocator can constrain the curator’s actions only through rights or controls that remain enforceable after deposit. The vault’s authorized role holders retain their powers unless an enforceable arrangement constrains the relevant actions.
- In Morpho Vault V2 (opens in a new tab), the Owner appoints the Curator, and the Curator sets allocation strategy and risk caps. The onchain Allocator role is distinct from an institution that deposits capital.
- An institutional allocator must check who can amend limits, approve exceptions, or revoke pending changes. A timelock does not give every depositor a veto.
- Native caps (opens in a new tab) block allocations above configured limits when assets are allocated. They do not continuously cap later exposure.
- Where an authorization workflow requires an Inherence (opens in a new tab) policy check, Inherence can evaluate covered curator actions against the applicable approved mandate before authorization. An allocator can independently verify the resulting evidence without viewing protected inputs encoded in the proof. A failed check blocks the covered route only if the proposed integration makes the check mandatory.
What authority remains after deposit
Depositing into a curated vault does not, by itself, give an institutional allocator authority to amend or veto its investment mandate. An institution may approve an exposure limit before deposit. The vault’s authorized roles still govern changes to its onchain limits. The allocator must establish who can alter the limit while its capital remains in the vault.
Morpho Vault V2 provides one example of this authority structure, not a model for every vault. Its role documentation (opens in a new tab) gives the Curator authority over strategy and risk caps, while the Owner can replace the Curator. An institution does not receive either role simply by depositing.
A notice period gives an allocator time to assess a proposed change, not authority to approve it. Morpho Vault V2 applies per-action timelocks (opens in a new tab) to certain changes, but those delays can initially be zero. An allocator needs to know whether a change requires its consent, whether another party can stop it, and whether it can exit before the change takes effect.
Who holds mandate authority in Morpho Vault V2
Morpho Vault V2 assigns strategy and permission changes to designated onchain roles, not to depositors by default.
Morpho’s role definitions (opens in a new tab) give the Owner power to appoint or replace the Curator and Sentinels. The Curator chooses the allocation strategy and sets risk caps. The Curator also selects approved adapters, fees, and holders of the onchain Allocator role. Those onchain Allocators move assets among approved adapters within the Curator’s caps. Depositing funds does not confer that onchain Allocator authority on the institution.
Sentinels can deallocate assets, lower caps, and revoke pending Curator actions. A depositor does not automatically become a Sentinel or gain a veto over proposed changes. Unlike a Morpho Vault V2 Sentinel, a depositor has no revocation authority unless appointed to an eligible role.
An institution’s signed mandate does not, by itself, change the Curator’s onchain authority. Exposure or counterparty limits in that mandate need a separate enforceable arrangement if they are to constrain vault actions after deposit. Before relying on that arrangement, an institutional allocator needs to identify the vault’s role holders. It also needs to identify which limits apply to covered actions and who can amend them.
How mandate changes and exceptions get approved
In Morpho Vault V2, the applicable delay depends on the proposed action. A Curator must queue cap increases and adapter additions, while a Curator or Sentinel can lower caps immediately (opens in a new tab). An applicable delay can initially be zero and may later increase. An allocator should inspect the vault’s current delays and pending proposals rather than assume a standard waiting period. Once a proposal’s delay expires, anyone can execute it. Proposal visibility (opens in a new tab) gives depositors notice, not an approval right.
An allocator must also review who can act immediately during an emergency. In Morpho Vault V2, the Owner can replace the Curator immediately, while a Curator or Sentinel can take certain immediate de-risking actions. An allocator should identify who approves an exception to its agreed mandate, which actions the exception permits, and how that approval is recorded. If the mandate requires the institution’s consent, the allocator should confirm how that requirement constrains the relevant role holder or covered execution route.
A timelock gives an allocator time to respond. It does not guarantee that the allocator can exit before a change takes effect. Withdrawal gates (opens in a new tab) can restrict redemptions, and available liquidity may limit them. An allocator should test its practical exit route against the shortest applicable delay. Morpho Vault V2 Sentinels can revoke pending actions, but depositors do not automatically hold that role. Aragon Guardians V2 (opens in a new tab) offers an optional depositor-voting veto mechanism. An allocator should verify whether a vault uses it and what voting rights the institution actually holds.
What independent evidence an allocator can verify pre-execution
A proposed Inherence arrangement would require covered curator actions to pass a policy check before authorization. The curator would retain the investment and execution role. A failed check would block the covered route only if the integration made that check mandatory.
An Inherence cryptographic receipt would let the allocator independently verify that a covered proposed action was evaluated against the applicable approved policy version and committed or attested inputs. The proof would not disclose protected inputs encoded in it. The cumulative-limits guide (opens in a new tab) addresses limits that span multiple actions.
A policy receipt establishes neither the action’s full history nor its eventual settlement. A valid policy evaluation does not establish who approved the policy version. It also does not establish whether a broker supplied every relevant offchain position. The allocator needs separate records for approval provenance, input completeness, execution, and settlement. Authenticated external inputs identify the data submitted for the policy check. The check does not independently establish the accuracy or completeness of that data.
Inherence provides evidence for covered actions routed through the defined enforcement path and evaluated against committed or attested inputs. It does not independently establish the truth of every external input or cover actions executed outside that path. Before relying on the evidence for a particular vault, an allocator should have coverage of normal and emergency routes confirmed separately. Any claim that a live integration binds policy receipts to executed transactions and settlement records also needs separate confirmation.
What each control can establish
Native vault controls can block actions that violate rules encoded in the vault. Their coverage depends on which actions trigger a check. Chamber’s Guard System (opens in a new tab) restricts managers to approved assets and protocols and applies fee caps. Chamber states that these rules do not judge how well a manager trades within them. Morpho Vault V2 caps (opens in a new tab) block allocations above configured limits when assets are allocated, but later changes in exposure do not necessarily trigger another cap check.
Post-trade monitoring gives an allocator a record of activity to review after it occurs. An alert can prompt an investigation or a request to reduce exposure. It cannot prevent a trade that has already settled.
A signed policy decision associates an approval or rejection with a signing key. The signature alone does not establish the allocator’s approval of the policy version. It also does not show that the curator used the decision before executing. The allocator must check who controls the signing key and whether every relevant execution route requires an accepted decision.
Independently verifiable pre-execution evidence can show whether a covered proposed action passed a policy check against committed or attested inputs. A verifier need not view protected positions encoded in the proof. Preventive enforcement additionally requires a mandatory check on the covered route.
The evidence does not establish external-input accuracy or settlement. It does not cover actions outside that route. The vault risk tools comparison (opens in a new tab) compares the broader set of tools by scope.
Questions to ask before and after depositing
The curator due-diligence checklist (opens in a new tab) covers broader pre-deposit review. These questions focus on who can change the mandate after capital enters the vault.
- Who sets the vault’s exposure and counterparty limits? Which limits belong to a separate allocator-approved mandate?
- Who can appoint or replace the role holders authorized to change those limits? In Morpho Vault V2, the Owner appoints the Curator (opens in a new tab). A depositor receives no automatic approval right.
- Which changes take effect immediately, and which face a delay? What are the current delays and pending proposals (opens in a new tab) for this vault?
- Who must approve a mandate amendment or exception before it takes effect? Can the allocator veto it or exit before activation, given the vault’s liquidity and withdrawal rules?
- Which actions must pass a pre-execution policy check? Who can authorize an exception or bypass that check during an emergency?
- Who attests the offchain positions and counterparty identities used in those checks? Who supplies prices? Who can correct an inaccurate input?
- What record identifies the approved mandate version, the authority that approved it, and the committed or attested inputs used for each covered action? What separate evidence establishes execution and settlement?
Conclusion
An institutional allocator should establish who may change its mandate after deposit and how its agreed limits constrain covered curator actions. If pre-execution enforcement is required, the allocator should confirm that the policy check is mandatory on the relevant route, including any emergency route. Governance rights and independently verifiable evidence answer different parts of that diligence question.