Protocols Overview

Strategy universe, role of each protocol, and current implementation status.

Protocols Overview

The strategy universe is intentionally small in the MVP.

Each strategy has a role in the portfolio, not just an APY target.

Strategy map

Strategy ID	Protocol	Role in portfolio	Liquidity profile	Status in repo
drift-reserve	Drift	Liquid reserve and low-complexity carry	instant	Real SDK path
kamino-stable-carry	Kamino	Main carry sleeve	same_day	Real SDK path
marginfi-canary	MarginFi	Small capped canary sleeve	same_day	Manifest or static
perena-exotic	Perena	Exotic / RWA sleeve	batched	Manifest or static

Why these four

• Drift gives the vault a liquid sleeve that is easier to unwind
• Kamino is the main carry engine of the MVP
• MarginFi is intentionally constrained as a canary
• Perena is the bridge into the exotic / RWA sleeve of the thesis

Integration modes

Real SDK adapters

Used when the protocol SDK is integrated and the runtime can construct bundles directly.

Current examples:

• Drift
• Kamino

Manifest adapters

Used when the protocol is not yet wrapped in a first-class SDK adapter but operators already know the instruction bundle shape.

Current examples:

• MarginFi
• Perena

Static fallback

Used for deterministic demos, tests, and placeholders while a live integration is incomplete.