// BLOOM PROTOCOL · DOCUMENTATION · v0.1.7

BLOOM DOCS

AGENT-ASSISTED YIELD · BASE L2 · NON-CUSTODIAL

// WHAT'S NEW

BLOOM FOR CLAUDE — Connect Bloom to Claude as a custom MCP connector: research Base assets, read your linked portfolio, and prepare reviewed buy/sell drafts inside the conversation. Claude never signs or executes — you always confirm in Bloom.

Read the connector docs →

2026-06-02 — Agent Wallet execution is now live in beta. You can route Morpho deposits and redeems through an isolated agent wallet instead of signing strategy transactions from your main wallet directly: Main wallet → Agent wallet → Yield strategy → Withdraw. Shielded Yield is live in beta; full private routing is next.

■AGENT WALLET EXECUTION (BETA) — Morpho deposits/redeems can route through the isolated agent wallet, which signs and is the vault's on-chain counterparty (use “Deposit via Agent Wallet” on the Morpho Vaults page).

■EMBEDDED EOA TODAY — The agent wallet is a Privy embedded wallet (EOA), not an ERC-4337 smart account yet; the ERC-4337 upgrade is on the roadmap.

■YOU STILL SIGN EACH ACTION — This is not unattended or autonomous execution; you confirm and sign every transaction.

■FUND THE AGENT FIRST — The agent wallet needs the asset you're depositing plus a small ETH balance for gas before it can route a deposit.

■FULL PRIVATE ROUTING IS ROADMAP — Intent-based routing and private-mempool submission are not yet live.

// OVERVIEW

Bloom is privacy-preserving yield infrastructure on Base. You deposit assets, shield balances, and earn yield through an isolated agent wallet — reducing wallet exposure and keeping your portfolio activity from becoming public intelligence by separating execution from identity.

The agent wallet is an isolated execution environment between your identity and your yield activity: your main wallet owns it and authorizes setup, but is never the on-chain counterparty for strategy transactions. Yield is currently powered by Morpho (the current yield engine), and the architecture is built so additional yield sources can be plugged in over time. One tap exits and returns funds.

// HOW IT WORKS

01DEPLOY — Bloom provisions an isolated agent wallet on Base (today a Privy embedded wallet / EOA; an ERC-4337 smart-account upgrade is on the roadmap). Your main wallet funds it and authorizes withdrawals but never signs day-to-day strategy transactions.

02FUND — Transfer the capital you want to put to work. Your main wallet never signs strategy transactions.

03ACTIVATE — Choose a strategy. The agent evaluates triggers and surfaces recommendations; you confirm and sign each transaction (fully autonomous execution is on the roadmap, not yet live).

04MONITOR — Watch positions, health factors, and yield in the dashboard. Receive alerts if thresholds are hit.

05EXIT — Withdraw at any time: redeem your Morpho positions back to the agent wallet and return funds to your main wallet, all user-signed. (A one-tap kill switch is in preview.)

// STRATEGIES

MORPHO_LOOP_v1RISK · LOW

Preview — not yet live. Recursive supply/borrow loop on Morpho Blue. (Simple, non-leveraged Morpho vault deposits are live today on the Morpho Vaults page.)

AAVE_LOOP_v2RISK · LOW

Preview — not yet live. Same loop structure on Aave V3. Deeper liquidity, slightly lower yield. Preferred for larger positions where depth matters.

GEARBOX_LEV_3XRISK · MED

Preview — not yet live. 3x leveraged yield position via Gearbox Credit Accounts. Higher yield, higher liquidation risk. Agent tightens loop on volatility.

0X_SWAPRISK · NONE

Planned. Best-execution token swaps routed through the 0x API for gas-efficient rebalancing within strategies.

// SECURITY MODEL

■NON-CUSTODIAL — Bloom never holds or controls your keys. The agent wallet is a Privy embedded wallet (EOA) you own.

■ISOLATED WALLET — Strategies run in a dedicated wallet. Your main address is never exposed to protocol risk.

■EXIT ANY TIME — Withdraw your positions whenever you want: no lock-ups, no exit queue. (A one-tap emergency kill switch is in preview.)

■AUDITED YIELD ENGINE — Yield currently runs through Morpho Blue, audited by Spearbit and verified on-chain. Bloom adds no custody on top.

■HEALTH MONITORING — Agent continuously checks health factors. Positions are tightened before they approach liquidation.

■NO DASHBOARDS TO BABYSIT — Alerts fire before issues occur. You don't need to watch 24/7.

// PROTOCOLS

MORPHOCURRENT YIELD ENGINE (LIVE). Non-custodial lending protocol; Morpho Blue enables isolated, curator-managed markets. Deposits and withdrawals work on Base today. Morpho is the current engine, not the final architecture — Bloom is built so additional yield sources can be plugged in.

AAVE V3Planned yield source. Battle-tested money market on Base for loop strategies and deep liquidity.

GEARBOXPlanned yield source. On-chain leverage via Credit Accounts for leveraged positions without a centralised intermediary.

0x APIPlanned routing layer. DEX aggregator routing swaps across Base liquidity for best-execution rebalancing.

// FAQ

> Do I need to leave anything running?

No. Live Morpho positions accrue yield on-chain with nothing running on your side. Autonomous agent strategies are in preview.

> What happens if I get liquidated?

Bloom is designed to monitor health factors and rebalance before liquidation thresholds. Leveraged strategies are still in preview; the live Morpho vault deposits are not leveraged and are not subject to liquidation.

> Can I use my hardware wallet?

Yes. The agent wallet is a Privy embedded wallet (EOA) owned by you; your main/hardware wallet authorizes setup and withdrawals and never signs day-to-day strategy transactions.

> What are the fees?

Bloom charges a performance fee on yield only. No management fees. No fees on principal.

> Is the code open source?

Yield runs through Morpho's audited, open, on-chain contracts. Bloom's own agent/execution code is in development and will be open-sourced as it ships.

> Which tokens can I deposit?

USDC, ETH, cbETH. More assets coming as strategies expand.

>BACK TO HOME >LAUNCH APP_X · @usebloom_base