Connected RFC: https://forum.summer.fi/t/rfc-revoke-curator-roles-across-all-fleets/905
Related: https://forum.summer.fi/t/ba-labs-stepping-down-as-risk-curator-for-the-lazy-summer-protocol/899
1. Overview:
Revoke CURATOR_ROLE from BA Labs (0xa16f07b4dd32250dec69c63ecd0aef6cd6096d3d) on every Fleet across all networks, following BA Labs' announcement that it is stepping down as risk curator. Executed as revokeCuratorRole(fleetCommander, account) calls on each chain's ProtocolAccessManager.
2. Motivation:
Per the connected RFC: with all Arks removed under SIP2.60, a Fleet has nothing to allocate between, so the curator mandate has no remaining function. It is a live permission that nothing is actively watching, on a protocol whose risk-management capacity is winding down and whose front-end sunsets on 31 August 2026.
Two developments since the RFC make this concrete:
- BA Labs has publicly announced it is stepping down as risk curator. Revoking the onchain role is the corresponding onchain act.
- The role holder enumeration is now published (thanks @halaprix for the role-decoding interface), so the call list below is complete rather than indicative.
3. Specification:
| Parameter | Value |
|---|
| Action | revokeCuratorRole(fleetCommanderAddress, account) |
| Account revoked | BA Labs curator: 0xa16f07B4Dd32250DEc69C63eCd0aef6CD6096d3d |
| Revocations | 14 (Ethereum 5, Base 3, Arbitrum 3, HyperEVM 2, Sonic 1) |
| Networks | Ethereum, Base, Arbitrum, Sonic, HyperEVM |
| Contract | ProtocolAccessManager per chain |
| Selector | 0xe9296665 |
| Authority | onlyGovernor → executes via the Timelock |
| Execution | Base governor → LayerZero → destination timelock |
| Risk level | Low (permission removal; no funds move; no role grants) |
3.1 Calls
Ethereum: ProtocolAccessManager 0xf389BCEa078acD9516414F5dabE3dDd5f7e39694
| # | Fleet | Fleet address |
|---|
| 1 | LazyVault_HigherRisk_WETH | 0x2E6abcbCCeD9Af05bc3B8a4908e0c98c29A88e10 |
| 2 | LazyVault_LowerRisk_WETH | 0x67e536797570b3d8919Df052484273815A0aB506 |
| 3 | LazyVault_LowerRisk_USDC (exploited) | 0x98C49e13bf99D7CAd8069faa2A370933EC9EcF17 |
| 4 | LazyVault_LowerRisk_USDT | 0x17Ee2D03e88b55E762c66C76ec99C3A28A54AD8d |
| 5 | LazyVault_HigherRisk_USDC (exploited) | 0xE9cDA459bED6dcfb8AC61CD8cE08E2D52370cB06 |
Arbitrum: ProtocolAccessManager 0xf389BCEa078acD9516414F5dabE3dDd5f7e39694
| # | Fleet | Fleet address |
|---|
| 6 | LazyVault_LowerRisk_USDC_2 | 0x71d77C39dB0eB5d086611a2e950198E3077cf58A |
| 7 | LazyVault_LowerRisk_USDC | 0x4F63cfEa7458221CB3a0EEE2F31F7424Ad34bb58 |
| 8 | LazyVault_LowerRisk_USDT | 0x98C49e13bf99D7CAd8069faa2A370933EC9EcF17 |
Sonic: ProtocolAccessManager 0xAFb8a8beA8F7CdB4b65437b0c5963dc7Cd270bC6
| # | Fleet | Fleet address |
|---|
| 9 | LazyVault_LowerRisk_USDCe | 0x507A2D9E87DBD3076e65992049C41270b47964f8 |
HyperEVM: ProtocolAccessManager 0x38fB5a7fa70103dCd9e8A969f3975A77E0fE755f
| # | Fleet | Fleet address |
|---|
| 10 | LazyVault_LowerRisk_USDC | 0x252E5Aa42c1804b85b2ce6712cd418A0561232Ba |
| 11 | LazyVault_LowerRisk_USDT | 0x2cC190fb654141DfBEaC4c0f718F4d511674D346 |
Base: ProtocolAccessManager 0xf389BCEa078acD9516414F5dabE3dDd5f7e39694
| # | Fleet | Fleet address |
|---|
| 12 | LazyVault_LowerRisk_EURC | 0x64Db8f51f1bf7064BB5A361a7265F602d348E0f0 |
| 13 | LazyVault_LowerRisk_USDC | 0x98C49e13bf99D7CAd8069faa2A370933EC9EcF17 |
| 14 | LazyVault_LowerRisk_WETH | 0x2bb9ad69FEBA5547b7cD57aAfe8457D40bF834af |
4. Risk Assessment:
- Technical. Permission removal only. No funds move, no approvals, no role grants. Verify each chain's
ProtocolAccessManager on its explorer before encoding a wrong AccessManager silently targets the wrong surface. Note Ethereum/Base/Arbitrum share 0xf389BCEa… while Sonic and HyperEVM differ.
- Operational sequencing.
removeArk is onlyGovernor and runs through the Timelock, not the curator, so SIP2.60 does not depend on BA's curator role. But any curator-gated divestment or rebalance would.
- Governance/security. Single-purpose, reduces privileged surface, grants nothing. Explicitly does not touch the Guardian module (being renewed under SIP0.3),
SUPER_KEEPER_ROLE, COMMANDER_ROLE, or ADMIRALS_QUARTERS_ROLE a wider role teardown is a separate discussion.
- Reinstatement. Re-granting
CURATOR_ROLE requires a fresh onchain-approved SIP.
5. Voting:
If YES - revoke CURATOR_ROLE from BA Labs (0xa16f07B4Dd32250DEc69C63eCd0aef6CD6096d3d) on all 14 listed Fleets across Ethereum, Base, Arbitrum, Sonic and HyperEVM.
If NO - leave the roles granted.
