---
type: Mechanism
title: MSV outflow limit (explanation and verification)
description: Ensuro's explanation of the 100k USDC net-outflow cap on the Multi-Strategy Vault, checked line by line against OutflowLimitedAMMSV.sol and an on-chain read.
resource: https://etherscan.io/address/0x55bAe6690d46EA94D7F05DF7c80A85E322421fB6#readProxyContract
tags: [liquidity, exit, msv, outflow-limit]
claim_basis: [code, onchain, ensuro-statement]
status: draft
generated: { by: grok-bot/lp-bundle-v0.2, at: 2026-11-17T15:30:00-03:00 }
verified:
  - { by: grok-bot/code-check, at: 2026-11-17T13:47:59-03:00 }
  - { by: grok-bot/onchain-check, at: 2026-11-17T13:47:59-03:00 }
stale_after: 2026-12-17T00:00:00-03:00
sources:
  - id: devteam
    resource: Explanation by Ensuro's development team, 2026-11-17
    title: Ensuro statement on the outflow limit
    author: team:ensuro
  - id: ensuro-1117
    resource: Ensuro team answers to LP due-diligence questions, 2026-11-17
    title: Ensuro team statements (unverified)
    author: team:ensuro
  - id: vaults
    resource: https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol
    title: OutflowLimitedAMMSV.sol at commit eefde276 (unchanged since v1.5.0)
  - id: snap0
    resource: Ethereum mainnet eth_call at block 26,436,058 (2026-11-17 13:47:59 America/Buenos_Aires) via ethereum-rpc.publicnode.com
    title: On-chain read of the MSV and AccessManager
---

# Ensuro's explanation (Ensuro statement)

Provided by Ensuro's development team on 2026-11-17 and reproduced verbatim except for typography. It is an Ensuro statement; the next section checks it against the contract.[^devteam]

The MSV is a vault where most of Ensuro's reserves (Sr. Pool, Jr. Pools and premiums accounts) invest their USDC to diversify investments across curated DeFi strategies. This vault has a net outflow limit, currently set at 100k USDC / day, meaning that no more than 100k USDC can exit the Ensuro protocol each day.

Why a 100k limit

The limit is a speed limit, not a lock-up. It protects the reserves' liquidity by:
1. Protecting claims capacity. The same USDC that earns yield also pays claims. A large claim could leave the reserves short of liquid funds.
2. Preventing a first-mover run. Without a limit, the fastest LPs in a stress event could take the liquid assets and leave the rest exposed. The outflow limit spreads exits over time.
3. Mitigating security breaches. A compromised key or mistaken transaction cannot drain the vault in one go, and, coupled with a good monitoring and alerting strategy, gives the team time to react.

How it works
- The vault tracks net flows per day: deposits add, withdrawals subtract.
- Before a withdrawal, it checks the current and previous day. If the two-day net outflow would exceed 100k, the withdrawal is rejected. The two-day window stops a withdrawal being split across midnight.
- Deposits offset withdrawals. With no prior withdrawals, 200k deposited today allows up to 300k to be withdrawn today, because the net outflow is still 100k. A deposit counts for the day it is made and the next day, then drops out.
- The cap is vault-wide, not per LP or per reserve.

# Verification against code and chain[^vaults][^snap0]

Pinned source: [`OutflowLimitedAMMSV.sol`](https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol) at `ensuro/vaults` commit [`eefde2769eb6a713d35848b0f75b1cd7a3854aad`](https://github.com/ensuro/vaults/commit/eefde2769eb6a713d35848b0f75b1cd7a3854aad) (main as reviewed on 17 Nov 2026). The file's content is unchanged since tag [`v1.5.0`](https://github.com/ensuro/vaults/blob/v1.5.0/contracts/OutflowLimitedAMMSV.sol) (`30e2ff131e1b419820dcfeebb7e6c22b6ce0e0a5`).

Deployed vault (proxy): [Ensuro MultiStrategy Vault (eMSV)](https://etherscan.io/address/0x55bAe6690d46EA94D7F05DF7c80A85E322421fB6#readProxyContract) `0x55bAe6690d46EA94D7F05DF7c80A85E322421fB6` on Ethereum, asset USDC (6 decimals). Implementation [`0x167107Ec321f723c5A412968E19731cfcd16B823`](https://etherscan.io/address/0x167107Ec321f723c5A412968E19731cfcd16B823#code) is a Sourcify exact match for `contracts/OutflowLimitedAMMSV.sol:OutflowLimitedAMMSV`. Access manager: `0x367A03aCD2f4dF96871B891c0bad32b9F2f3A9D4`.

On-chain values below are from `eth_call` at block **26436058**, timestamp 2026-11-17 16:47:59 UTC (**13:47:59 America/Buenos_Aires**), via `https://ethereum-rpc.publicnode.com`.

## Mechanical claims

| Claim (Ensuro) | Verdict | Evidence |
|---|---|---|
| Most Ensuro reserves (Senior, Juniors, premiums accounts) invest USDC in the MSV | **Confirmed** (config + Senior on-chain) | Senior eToken `0xa551285B49A29cBDBAE7fC5C6a61fadC918Ad224` `yieldVault()` returns the MSV. `deploy-scripts/chains/mainnet.yaml` sets `yield_vault: MSV` on the Senior, Junior eTokens, premiums accounts and the cash-flow lender. |
| Net outflow limit currently 100k USDC / day, meaning no more than 100k can exit the Ensuro protocol each day | **Confirmed, with window detail** | The stored limit is 100,000 USDC and `slotSize` is 86,400 seconds (one UTC calendar day), both confirmed on-chain (`getOutflowLimit()`, `getOutflowLimitSlotSize()`). The check in [`_withdraw` L140–146](https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol#L140-L146) sums the current and the previous slot, so the 100k applies to net outflow over two consecutive UTC days (as Ensuro's own 'How it works' notes). The cap applies to withdrawals from the MSV, not to USDC a reserve already holds uninvested (the Senior held $9,973.93 liquid USDC at the snapshot). Deposits offset outflows. |
| The limit is a speed limit, not a lock-up; it protects claims capacity, prevents a first-mover run, and slows a compromised-key drain | **Not verifiable** (design intent) | The contract only stores a numeric cap and enforces it on ERC-4626 deposit/withdraw. It does not encode these reasons. The mechanics are consistent with a speed limit (exits are delayed, not forbidden). |
| The vault tracks net flows per day: deposits add, withdrawals subtract | **Confirmed** | [`_deposit` L155–163](https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol#L155-L163) adds `assets` to `assetsDelta[current slot]`; [`_withdraw` L149](https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol#L149) subtracts. Slot index is `(slotSize << 128) + block.timestamp / slotSize` ([L123–126](https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol#L123-L126)). With `slotSize = 86400`, a "day" is a **UTC** calendar day (Unix epoch). The slot boundary is 00:00 UTC (21:00 America/Buenos_Aires the previous evening), not midnight ART. |
| Before a withdrawal, it checks the current and previous day; if two-day net outflow would exceed 100k, it reverts; the two-day window stops a split across midnight | **Confirmed** | [`_withdraw` L140–146](https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol#L140-L146): `deltaLastTwoSlots = -assets + assetsDelta[slot] + assetsDelta[prevSlot]`; reverts `LimitReached` if this is negative and its absolute value is **strictly greater** than `limit`. Exactly 100k over the two-slot window is allowed. Tests in `test/test-limit-outflow.js` withdraw 1000 (the test limit) on day 1, then show a further withdrawal still reverts after advancing one day, and only succeeds after two days. Midnight in this sense is 00:00 UTC. |
| With no prior withdrawals, 200k deposited today allows up to 300k withdrawn today, because net outflow is still 100k | **Confirmed** (under the stated assumption) | `deltaLastTwoSlots = -300k + 200k + 0 = -100k`, which is not strictly greater than the 100k limit. The assumption "no prior withdrawals" must include the **previous** UTC day: if yesterday's net outflow was already 100k, today's 200k deposit would allow only 200k out (net two-day outflow still 100k), not 300k. |
| A deposit counts for the day it is made and the next day, then drops out | **Confirmed** | The withdrawal check reads only the current and previous slot. A deposit on day D sits in `assetsDelta[D]` and still offsets withdrawals on day D+1; on day D+2 it is no longer in the window. |
| The cap is vault-wide, not per LP or per reserve | **Confirmed** | One `limit` and one `assetsDelta` mapping for the whole vault ([L32–35](https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol#L32-L35)). Any MSV withdraw/redeem — Senior or Junior deinvest, premiums-account claim funding, cash-flow lender, or a direct eMSV exit — consumes the same cap. |

## Measurement window (code-verified)

Ensuro describes the cap as 100k per day. In the code, the check sums the current and the previous UTC-day slot, so absent offsetting deposits or a `changeDelta` reset the 100,000 USDC net-outflow limit applies over **two consecutive UTC calendar days**. If the previous UTC day already recorded 100k of net outflow, the current day has no room until a deposit or a Guardian reset adds it.
- Deposits raise the room: net outflow, not gross withdrawals, is what is capped. At the 17 Nov 2026 13:47 ART snapshot, today's net was **+$33,001.19** and yesterday's **+$500.20**, so the MSV could have released up to **$133,501.39** at that moment (shared across all reserves, and still subject to strategy liquidity).
- `setupOutflowLimit` with a new `slotSize` starts a new slot key and so clears recorded deltas ([L56–57](https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol#L56-L57)). `slotSize = 0` disables the check ([L60](https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol#L59-L61)).

## Who can change the limit or reset the delta

The implementation itself has no access-control modifiers; the proxy is an `AccessManagedProxy` and the on-chain AccessManager assigns the roles (confirmed with `getTargetFunctionRole` / `hasRole` / `canCall` at the same block).

| Function | Role (on-chain) | Who holds it | Delay |
|---|---|---|---|
| `setupOutflowLimit(slotSize, limit)` ([L63–68](https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol#L63-L68)) — change the cap or the period, or disable it | `LEVEL1_ROLE` | Admin Safe `ADMINS_V3` [`0xB809C75914c62DA604B1f6F1C4300bAc91797Aa1`](https://etherscan.io/address/0xB809C75914c62DA604B1f6F1C4300bAc91797Aa1) — **3-of-4** (`getThreshold()` / `getOwners()`) | **4 days** (345,600 seconds). `canCall` is not immediate. |
| `changeDelta(slot, deltaChange)` ([L117–121](https://github.com/ensuro/vaults/blob/eefde2769eb6a713d35848b0f75b1cd7a3854aad/contracts/OutflowLimitedAMMSV.sol#L117-L121)) — credit or debit a slot's recorded flow, which can unblock a further withdrawal or tighten the remaining room | `GUARDIAN_ROLE` | Guardian Safe `LOW_RISK_V3` [`0x5848A5a692373CAd6FAAbB7b96EF43Ec1a386867`](https://etherscan.io/address/0x5848A5a692373CAd6FAAbB7b96EF43Ec1a386867) — **2-of-4**, same four owners as the Admin Safe | **None**. `canCall` is immediate. |

## Does an eUSDSr withdrawal go through this limit?

**Yes, when the Senior eToken has to pull USDC out of the MSV; no, when it already holds enough uninvested USDC.**

`EToken.withdraw` ([v3.2.2 L514–551](https://github.com/ensuro/ensuro/blob/v3.2.2/contracts/EToken.sol#L514-L551)) burns shares and calls `Reserve._transferTo`. If the eToken's own USDC balance is short, `_transferTo` ([v3.2.2 L99–111](https://github.com/ensuro/ensuro/blob/v3.2.2/contracts/Reserve.sol#L99-L111)) calls `_deinvest`, which is `yieldVault.withdraw(...)` ([L201–202](https://github.com/ensuro/ensuro/blob/v3.2.2/contracts/Reserve.sol#L201-L202)). The Senior's `yieldVault()` is the MSV, so that path is subject to the outflow cap.

The cap is **not** a parameter of `EToken.withdraw` itself. `totalWithdrawable()` only reflects locked SCR. `MSV.maxWithdraw(Senior)` at the snapshot was the Senior's full MSV balance ($1,410,695.91) and does **not** subtract the outflow cap (`OutflowLimitedAMMSV` does not override `maxWithdraw`). A withdrawal that looks padded on those views can still revert `LimitReached`.

At the snapshot: Senior liquid USDC outside the MSV = **$9,973.93** (can leave without hitting the cap); Senior assets in the MSV = **$1,410,695.91**; MSV TVL = **$2,345,298.67**; MSV idle USDC = $0.

## Exit capacity for a large Senior LP

This is only the MSV outflow constraint. Locked SCR (`totalWithdrawable`) and strategy liquidity are separate, and for capital bound by current Spot/Ikon policies they are the tighter constraint until those policies expire (18 Jan 2027).

- A withdrawal larger than the remaining room cannot leave the MSV in one transaction under the current limit; it proceeds in tranches, and the room is shared with any other reserve that deinvests (claims, Junior exits, premiums-account payouts).
- The Guardian Safe (2-of-4, no delay) can reset the recorded outflow (`changeDelta`) immediately; the Admin Safe (3-of-4) can raise the limit with a 4-day timelock (`setupOutflowLimit`). Ensuro states it would use these after checking that the requests are legitimate.[^ensuro-1117] These are discretionary actions, not on-chain commitments to an LP.

## Ensuro's stated exit process (added 2026-11-17)

Ensuro states:[^ensuro-1117]
- LPs notify Ensuro **by 10 January 2027** of the amount they will withdraw.
- Ensuro states full withdrawal will be possible **by 20 January 2027**, with the 100k cap kept in place.
- Ensuro may raise the cap or reset the outflow delta at its discretion, after checking that all requests are legitimate, and prefers not to change the cap until close to maturity.
- Ensuro notes that the outflow window logic (slot size and limit) is a modifiable parameter (`setupOutflowLimit`, Admin Safe with 4-day timelock).

These are Ensuro statements, not enforced on-chain. See [liquidity and exit](/02-senior-pool/liquidity-and-exit.md).

[^devteam]: Ensuro statement on the outflow limit
[^ensuro-1117]: Ensuro team statements, 2026-11-17 (unverified)
[^vaults]: OutflowLimitedAMMSV.sol at commit eefde276
[^snap0]: On-chain read at block 26,436,058
