[SIP2.25] Update ARKs from core protocols on Base fleets (USDC/WETH)

Overview

Onboard additional strategies (ARKs) to the USDC and WETH (ETH) fleets on Base to expand diversification and keep yield sources current.

Motivation

  • Expand yield sources: Add newly available Morpho Blue vaults and Euler markets on Base.
  • Stay current: Keep the fleet aligned with high-quality, recently launched opportunities.
  • Deliver core value: Maintain access to the highest-quality yields in DeFi via curated, diversified ARKs.

Specification

USDC Fleet (Base)

New Ark Fleet Network Risk Level
Morpho Steakhouse High Yield USDC USDC Base Pending @BlockAnalitica classification
Morpho Extrafi XLend USDC USDC Base Pending @BlockAnalitica classification
Morpho Universal USDC USDC Base Pending @BlockAnalitica classification
Morpho High Yield Clearstar USDC USDC Base Pending @BlockAnalitica classification
Morpho Clearstar Reactor (OpenEden Boosted) USDC USDC Base Pending @BlockAnalitica classification
Morpho Gauntlet USDC Frontier USDC Base Pending @BlockAnalitica classification
Morpho Re7 USDC USDC Base Pending @BlockAnalitica classification
Euler USDC (Base) USDC Base Pending @BlockAnalitica classification

WETH (ETH) Fleet (Base)

New Ark Fleet Network Risk Level
Morpho Extrafi XLend WETH WETH (ETH) Base Pending @BlockAnalitica classification
Morpho Yearn OG WETH WETH (ETH) Base Pending @BlockAnalitica classification
Euler WETH (Base) WETH (ETH) Base Pending @BlockAnalitica classification

Risk Assessment

Minilmal new protocol risks as all are supported currently. Risk caps will need to determined on a per ARK basis by @BlockAnalitica

Voting

  • YES: Add each listed Ark to the specified fleet on Base, subject to @BlockAnalitica classification and standard caps/parameters.
  • NO: Make no changes; fleets remain as currently configured.
3 Likes

Another great refresh, now for the Base Fleet @samehueasyou good to see Base getting the same treatment with a mix of Morpho and Euler ARKs.

Given the more concentrated asset base on Base, I m curious to see @BlockAnalitica cap recommendations to ensure we avoid overexposure to any single protocol or yield source.

1 Like

Votes are now live! Going forward I would kindly ask all proposers to split SIPs and their numbering for each of the Fleet according to SIP template (SIPX.Y.Z).

VOTE SIP2.25.1 {USDC Fleet}:

VOTE SIP2.25.2 {WETH Fleet}:

1 Like

VOTE SIP2.25.3 {WETH Fleet}:

Repair of SIP2.25.2 (SIP2.25) with MorphoVaultArk excluded. Previous proposal fails to execute due to existing deployment of that strategy in the Fleet. This proposals addresses that.

Numbering is incorrect and the script used for deployment of these proposals will be fixed going forward (@0xtucks, @halaprix).

1 Like

Mention of the network of the fleets that are getting additions to would also be great moving forward (have seen this being done more, though). The naming of the proposals was confusing at the time, had to jump back to the forum to be sure.

1 Like

100%, I have updated the SIP Template topic to now include guide for numbering e.g.: SIPX.Y.Z

Usually, I help with editing the topic title on the forum, but it has happened before that onchain proposals were posted with a script that has led to a confusion.

I would like to ask @halaprix and @0xtucks to review the script previously used. If I can be of any help in this process, do let me know!

I would also like to ask all @Recognized_Delegates and the community to check the templates before posting, as well as this calendar regarding the latest SIP numbering <3

1 Like