Veda

Veda provides partner-branded vaults whose curators can move assets among lending, staking, DEX and other strategies. DefiLlama recorded about $1.40B on 2026-08-14, so the earlier claim that it was too small was false. The right judgment is delegated allocation: Merkle allowlists limit what a strategist may call, but the depositor still accepts future allocation choices and every permitted underlying venue. This applies the class rule and does not mean Veda is unsafe.

Review triggers: events that reopen the verdict
• A named vault publishes a static mandate with complete exposure caps, authorities, loss accounting and stressed-exit evidence suitable for individual review

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

A depositor receives BoringVault shares through a Teller at an exchange rate published by an Accountant. A curator proposes changes, and a strategist makes them through a Manager. Merkle proofs and decoder contracts limit calls to pre-authorized targets and parameters. Veda lists allocations to venues such as Aave, Morpho and Euler and says assets remain onchain.

Control and operating record

The curator chooses strategy and exposure within the allowlist, the strategist runs the vault, and configurable modules govern accounting, locks and exits. Veda publishes a long audit list for the core vault, Teller, Accountant, queue, solver and integrations. It says the system has run at billion-dollar scale without a security incident. That claim comes from the issuer and is not an independently verified finding of no loss.

Exit consequences

Some deployments keep a buffer for instant withdrawals. Otherwise, a holder sends shares to BoringQueue, waits through a configurable maturity period, and relies on a third-party solver to deliver the requested asset. The holder can cancel an unfilled request and recover the shares. Exit timing and value thus depend on the current strategy mix, unwind liquidity, queue settings and reported exchange rate.

Why the class rule decides

Veda is built to let a curator change allocations after deposit. Onchain custody and call limits reduce operating risk, but they do not let this advisory program control which approved strategy is live or stop the vault from adding an underlying venue we reject. Review reopens for a named vault with a static mandate whose complete allowlist, caps, authorities, loss accounting and stressed exit can each be assessed.

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.

• Veda Docs — architecture and flow of funds · primary · accessed 2026-08-14
  Supports: vault share mechanism, curator-directed rebalancing, onchain assets, withdrawal queue
• Veda Docs — core components and Manager constraints · primary · accessed 2026-08-14
  Supports: strategist authority, Manager controls, withdrawal queue
• Veda Docs — audits · primary · accessed 2026-08-14
  Supports: published security reviews, audit scope, integration reviews
• DefiLlama — Veda survey record · secondary · accessed 2026-08-14
  Supports: survey TVL, chains, protocol category

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.