1. Overview:
Offboard the legacy Arks that are already at deposit cap 0 across the dao-risk-managed Fleets, and re-open those Fleets for withdrawals. Each Fleet is handled in its own sub-SIP and its own Governance vote (SIP7.3.1–2).
2. Motivation:
As a follow-up to the July 6th incident I propose winding down the old Ark set. Many legacy Arks have already had their deposit caps set to 0, but remain registered on their FleetCommanders and are still counted in NAV; precisely the state the exploit abused. Following the incident, deposit caps on the DAO-managed Fleets were set to 0 and the Fleets were paused.
Only Arks currently at cap 0 are in scope. An Ark cannot have its cap set to 0 while paused, so paused/non-zero Arks are deliberately excluded and will be handled in a later round if the community wishes to continue. Removing the zero-cap Arks and unpausing the Fleets restores withdrawal access for depositors while cleaning up the Fleet configuration.
Connected RFC: [RFC] Offboard legacy Arks and re-open paused Fleets for withdrawals. The equivalent operation for the ba-risk-managed Fleets is covered in SIP2.59.
3. Specification:
Each sub-SIP, per Fleet, executes: unpause() the Fleet → removeArk() for each listed legacy Ark → setTipRate(0). Proposals originate on the Base governor and relay via LayerZero to the mainnet timelock. Per-Fleet details, addresses and Ark lists are in the sub-SIPs below.
4. Risk Assessment:
Mechanical/low-change. These are the DAO-managed Fleets, so risk curation sits with Governance rather than an external risk curator. Key points: the listed Arks are already at cap 0, so their removal creates no new deposit exposure; removing them takes them out of the Fleet’s active set and out of NAV, closing the donation/price-manipulation vector identified in the post-mortem; unpausing only re-enables withdrawals. No user funds are moved by these votes beyond making them withdrawable.
5. Voting:
Each sub-SIP is voted independently.
If YES - execute that Fleet’s cleanup.
If NO - leave that Fleet unchanged.
Sub-SIPs DAO-managed (SIP7.3.X)
[SIP7.3.1] Offboard legacy DAO_LazyVault_USDC_1 Arks (Mainnet)
| Parameter | Value |
|---|---|
| Fleet | DAO_LazyVault_USDC_1 |
| Network | Mainnet |
| FleetCommander | 0xd77F9a9F2b0C160dB3e9dC2Cce370c1a740C76fc |
| Arks removed | 10 |
| Unpause fleet | Yes |
| Set tip rate | 0 |
| Risk mgmt | dao-risk-managed |
| Execution | Base governor → LayerZero → mainnet timelock |
Actions (in order):
unpause() the fleet (re-enables withdrawals); removeArk() × 10; setTipRate(0).
Arks removed:
MorphoV2Vault-usdc-Re_Ecosystem_Vault_USDC-1, MorphoV2Vault-usdc-Alpha_USDC_Enhanced-1, MorphoV2Vault-usdc-Hyperithm_USDC_Degen-1, MorphoV2Vault-usdc-Gauntlet_USDC_Frontier-1, MorphoV2Vault-usdc-KPK_USDC_Yield_V2-1, MorphoV2Vault-usdc-August_USDC_V2-1, ERC4626-Fluid-usdc-1, MorphoVault-usdc-Hyperithm_USDC-1, MorphoVault-usdc-Clearstar_High_Yield_USDC-1, MorphoVault-usdc-Alpha_USDC_Core-1
Voting:
If YES - execute the above for DAO_LazyVault_USDC_1 on Mainnet (unpause + remove the listed zero-cap Arks + zero tip rate).
If NO - leave the fleet unchanged.
[SIP7.3.2] Offboard legacy DAO_LazyVault_WETH_1 Arks (Mainnet)
| Parameter | Value |
|---|---|
| Fleet | DAO_LazyVault_WETH_1 |
| Network | Mainnet |
| FleetCommander | 0x0C1FBCCC019320032D9acD193447560C8C632114 |
| Arks removed | 5 |
| Unpause fleet | Yes |
| Set tip rate | 0 |
| Risk mgmt | dao-risk-managed |
| Execution | Base governor → LayerZero → mainnet timelock |
Actions (in order):
unpause() the fleet (re-enables withdrawals); removeArk() × 5; setTipRate(0).
Arks removed:
MorphoVault-weth-Alpha_WETH_Core-1, MorphoVault-weth-SingularV_WETH-1, MorphoV2Vault-weth-KPK_WETH_Yield_v2-1, MorphoV2Vault-weth-KPK_ETH_Prime_v2-1, FluidLite-weth-1
Voting:
If YES - execute the above for DAO_LazyVault_WETH_1 on Mainnet (unpause + remove the listed zero-cap Arks + zero tip rate).
If NO - leave the fleet unchanged.