YieldSeeker

YieldSeeker gives an autonomous agent delegated control of a Base smart account and lets Autoseek move USDC among Morpho, Euler, Spark, Yo, Tokemak, Fluid and other vaults after deposit. The user retains withdrawal rights but cannot enforce Ketju’s approved-venue allowlist and caps while the agent selects and rebalances the live portfolio. That continuing allocation authority is more fundamental than the approximately $1.26M TVL observed on 2026-08-16, so the version-1 delegated-allocation dossier rejects it at zero.

Review triggers: events that reopen the verdict
• Enforces an immutable client-specific allowlist and client-specific venue constraints covering only mandate-approved strategies, with agent permissions, holdings, debt and realized losses independently observable
• Demonstrates a proposed-size stressed USDC withdrawal through every active vault without new subscriptions, venue substitution or discretionary override

Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.

The research file

Mechanism and class applicability

A user deposits USDC into an isolated Base smart account controlled through agent permissions. YieldSeeker states that its autonomous Autoseek strategy scans rates, incentives, protocol risk and liquidity, then reallocates across multiple vaults, swaps rewards back to USDC and compounds without a new user transaction. The DefiLlama adapter enumerates dozens of Morpho, Euler, Spark, Yo, Tokemak, 40 Acres, Avantis and Fluid vault receipts held by agent wallets. This is continuing venue selection after deposit and directly satisfies the shared delegated-allocation dossier.

Current observation and perimeter

The DefiLlama protocol API read on 2026-08-16 classified YieldSeeker as a Yield Aggregator and reported approximately $1.26M entirely on Base. Its adapter obtains agent-wallet addresses and token lists from the YieldSeeker API, reads balances onchain and unwraps ERC-4626 shares; it marks the balance double-counted because underlying venues also report those assets. The record therefore covers the aggregate agent portfolios, not a fixed vault or independent pool of exit liquidity.

Control, loss and exit applicability

YieldSeeker describes the platform as custodial smart-contract infrastructure even though accounts are isolated and only the owner may withdraw. Agent execution relies on EIP-7702 delegation, Coinbase TEE key infrastructure and platform-selected vault integrations. The account inherits contract, oracle, liquidity, curator, reward-swap and incident risk from every active underlying venue. A withdrawal instruction remains user-controlled, but executable proceeds depend on the agent unwinding each live vault and any queue or loss inside it.

Why the class rule decides

Personal risk preferences and visibility into current allocations do not give the advisor an immutable allowlist or client-specific venue constraint matching the mandate. The agent can replace one underlying claim with another between reviews, including a curator-controlled or otherwise rejected vault. The version-1 delegated-allocation dossier therefore controls regardless of size. Reopen only if a client-specific immutable policy limits activity to currently approved venues and caps, holdings, debt, realized losses and delegation changes are independently verifiable, and a proposed-size stressed withdrawal clears every active venue; compare with direct positions governed by those client constraints in those venues.

Class rule

The delegated allocation class is outside the approved structures, so every protocol in it is not approved until the rule changes. The rule is about the structure, not an adverse finding about this protocol, and it is not a client instruction. The events that would reopen it are listed with the memo.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• YieldSeeker — autonomous allocation overview · primary · accessed 2026-08-16
  Supports: autonomous agent, protocol selection, risk preferences, rebalancing, strategy execution
• YieldSeeker — Autoseek and multi-vault operation · primary · accessed 2026-08-16
  Supports: Base, USDC, agent wallet, multi-vault, reward conversion, withdrawal
• YieldSeeker — infrastructure and live allocation controls · primary · accessed 2026-08-16
  Supports: custodial infrastructure, isolated account, continuous reallocation, transaction history, withdrawal control
• YieldSeeker — security and delegated execution · primary · accessed 2026-08-16
  Supports: EIP-7702, Coinbase TEE, agent permissions, audit, recovery
• DefiLlama adapter — YieldSeeker agent and vault look-through · secondary · accessed 2026-08-16
  Supports: agent API, wallet balances, ERC-4626 vault list, underlying conversion, double counting
• DefiLlama — YieldSeeker survey record · secondary · accessed 2026-08-16
  Supports: current TVL, Base, Yield Aggregator category, survey observation

Inherited controls

The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.