Summary: Veda is a DeFi infrastructure platform centered on its BoringVault architecture, aimed at helping fintechs, exchanges, wallets, chains, and asset issuers package multichain DeFi strategies into branded yield products. The official docs and repositories make it look less like a single vault frontend and more like a reusable control plane for pricing, accounting, permissions, risk controls, withdrawals, and strategy execution.
What it does:
Provides the BoringVault contract as the asset-holding vault layer where shares are minted, burned, and managed
Uses modular surrounding components such as a Teller for deposits/withdrawals, an Accountant for exchange-rate publication, a Manager for strategy authorization, and queue/solver flows for delayed withdrawals
Restricts strategist actions through Merkle-tree-based authorization, with protocol-specific decoder/sanitizer components validating allowed calldata and parameters
Supports multi-asset deposits, share-lock periods, permissioned refund/remediation flows, and queue-based withdrawal mechanics intended to reduce MEV and operational risk
Markets configurable compliance controls, white-label deployment support, and broad integrations for institutions and consumer-facing financial products
Key claims:
Official docs position Veda as a “DeFi vault primitive” that packages lending, DEX, and staking strategies into non-custodial, trust-minimized, composable products for partners
The public docs and docs repo claim Veda powers products such as Kraken DeFi Earn, EtherFi Liquid Vaults, and Lido Earn, and is distributed through Binance Web3 Wallet and Bybit Web3 Wallet
The Boring Vault repo explains that strategy permissions are enforced through Merkle-tree leaves encoding allowed targets, selectors, and sensitive arguments, which is a stronger and more concrete control model than the homepage alone suggests
The Accountant design in official docs and repo materials relies on offchain exchange-rate calculation with rate limits and bound limits, plus pause behavior when updates move outside permitted bounds
Veda publishes a substantial first-party audits table covering the core architecture plus repeated component/integration updates, which makes the protocol easier to evaluate as production vault infrastructure rather than as generic yield marketing
One cataloging nuance is that the homepage makes large market-leadership claims, but the most reliable primary-source detail comes from the docs, audit tables, and public Boring Vault repository rather than from the homepage copy alone
Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were the official docs, the public Boring Vault repository, the GitHub organization, and the first-party audits index; see ../whitepapers/veda-primary-sources-2026-04-25.md.