Veda: The Vault Infrastructure Behind DeFi Yield Products
How Veda separates vault infrastructure, strategy curation, and user-facing applications across Hyperliquid DeFi.
Veda is vault infrastructure rather than a single lending or trading strategy. Applications can use its vault system to accept deposits, issue receipt tokens, and allocate capital across one or more DeFi protocols under a defined strategy.
DefiLlama attributes about $59.6 million of Veda TVL to Hyperliquid L1 as of August 31, 2026.
Separate the vault from the curator
A vault is the smart-contract container that holds and routes assets. A curator or strategy manager decides how capital should be allocated within permitted constraints.
These are different risk layers. Secure vault code does not guarantee that the selected strategy is economically safe, while a strong curator cannot eliminate smart-contract or integration risk.
Guardrails constrain what the strategy can do
Veda's architecture uses a BoringVault-based model with controls that restrict operations to approved actions. This reduces the attack surface compared with giving an automation system unrestricted permission over all possible contracts and assets.
The exact permission set still matters. An institutional review should inspect who can change strategy configuration, what delays or governance controls apply, and how emergency actions work.
Why Veda shows up inside Hyperliquid products
A protocol can outsource part of its vault infrastructure while retaining its own frontend and product positioning. Kinetiq Earn, for example, uses Veda infrastructure for automated kHYPE strategies.
This means TVL can appear under several product relationships depending on how an analytics provider attributes the underlying assets. Readers should avoid adding headline TVL figures across wrappers without checking for double counting.
The institutional lesson
Veda represents a broader shift from users manually assembling DeFi positions toward onchain asset-management infrastructure. The user sees one deposit product, while the backend can diversify across several venues and rebalance as conditions change.
That improves usability, but due diligence must follow the full dependency graph from frontend to vault, curator, underlying protocols, bridges, oracles, and permissions.