Veda is the vault infrastructure platform behind Kraken DeFi Earn, Ether.fi Liquid Vaults, and Lido Earn. It raised $18 million in June 2025 led by CoinFund, with participation from Coinbase Ventures, BitGo, and GSR. Its BoringVault framework has over $3.7 billion in TVL and powers roughly 55% of the EVM vault market. Veda's pitch is infrastructure: it gives financial apps, asset issuers, and exchanges the technical stack to launch branded vault products without building vault architecture from scratch.

Lucidly is a different kind of product. The syToken vaults at app.lucidly.finance (syUSD, syETH, and syBTC) are direct-access institutional yield vaults with defined strategies, Pashov-audited execution constraints, and a real-time Transparency Dashboard. Lucidly is not vault infrastructure for other applications to white-label. It's a vault product that institutional allocators use directly.

Comparing Lucidly and Veda directly is a category clarification as much as a feature comparison. One is infrastructure. The other is a product built on infrastructure. Understanding the distinction is the starting point for evaluating which one a hedge fund, family office, or institutional treasury should actually care about.

What Veda actually is

The infrastructure layer

Veda's BoringVault is a modular vault contract framework that other platforms use to build their own yield products. Kraken integrated Veda to launch DeFi Earn without building vault smart contracts internally. Ether.fi uses Veda infrastructure for its Liquid BTC and Liquid ETH vaults. Lido Earn runs on Veda's stack. The value proposition is developer-facing: launch new vaults in as little as 48 hours, deploy across EVM chains, SVM, and MoveVM from a single integration, configure address whitelists and compliance controls, and use Merkle-verified calldata to constrain permitted actions.

This is a legitimate and well-executed institutional-infrastructure product. The Merkle-verified constraint architecture in Veda's BoringVault is the same architectural concept Lucidly's Manager contract uses: whitelisted calldata that limits what any operator can do regardless of who holds the key. Veda's $3.7 billion TVL represents real capital managed through its vault framework. The security record is clean. The audit history is substantial.

But Veda itself is not the yield product an institutional allocator deposits into. The yield product is whatever application has built on top of Veda's infrastructure. Kraken DeFi Earn is the product. Ether.fi Liquid is the product. In terms of strategy clarity, reporting quality, and execution transparency, the allocator's counterparty is the platform that built on Veda, not Veda itself.

What Veda-powered products look like for end investors

Kraken DeFi Earn advertises up to 8% APY on stablecoins through Veda-powered vaults. The strategy runs through Sentora, Chaos Labs, and Veda's risk management layer into Morpho, Aave, and Sky. The underlying risk managers (Sentora, Chaos Labs) make allocation decisions across those protocols. For an institutional allocator using Kraken as their access point, the due diligence chain is: Kraken interface, Veda infrastructure, Sentora/Chaos Labs strategy decisions, underlying protocol positions.

For a fund running institutional due diligence on this chain, the strategy opacity is the challenge. Sentora and Chaos Labs make dynamic allocation decisions across multiple protocols. The allocation at any given moment is not fixed; it follows the risk managers' judgment. The due diligence question "what is this vault currently deployed into" has a time-varying answer that depends on external teams' current positions across multiple protocols and chains.

What Lucidly actually is

The direct-access institutional yield product

The syToken vaults at app.lucidly.finance are the product an institutional allocator deposits into directly. syUSD is a leveraged Morpho Blue USDC lending strategy. syETH is a leveraged wstETH strategy capturing ETH staking economics. syBTC is a leveraged WBTC or cbBTC strategy generating BTC-denominated yield. Each strategy is defined, fixed, and audited, not dynamically allocated across protocols by a human team.

The institutional due diligence chain is shorter: the Pashov audit on the Details tab documents what the Manager contract can and cannot do, the Allocations tab shows current deployment and health factor in real time, the Returns Attribution shows yield by source, and the 45-day APY history on the Flagship tab shows how the strategy has performed across different market conditions. The counterparty is the smart contract architecture, not a team's dynamic allocation decisions.

Why the shorter chain matters

For a hedge fund whose LP agreement describes a specific strategy mandate, the due diligence chain length is a practical compliance issue. Describing a Kraken DeFi Earn position to LPs requires explaining Kraken's interface, Veda's infrastructure, Sentora's allocation methodology, and the underlying protocol positions across Morpho, Aave, and Sky, all of which can change. Describing a syUSD position at app.lucidly.finance requires explaining a single defined strategy: leveraged Morpho Blue USDC lending, audited execution constraints, 29.5% instant-redemption buffer, returns from lending income and strategy spread only.

The second description is stable over time. The first requires updating as allocation decisions change. For funds with LP reporting obligations on a quarterly basis, stability of strategy description is not a minor convenience; it's a material compliance factor.

Head-to-head comparison across what institutions actually care about

Strategy clarity

Veda provides infrastructure. The strategy clarity of any Veda-powered product depends entirely on who built on top of Veda and how transparently they communicate their allocation decisions. Kraken DeFi Earn's strategy description involves multiple protocol integrations and dynamic risk manager decisions. Lucidly's syUSD strategy at app.lucidly.finance is a fixed leveraged Morpho Blue position with no dynamic protocol switching.

On strategy clarity, Lucidly wins for institutional allocators who need a stable, auditable description of what the vault does for LP reporting purposes.

Execution constraints

Both Veda's BoringVault and Lucidly's Manager contract use Merkle-verified whitelisted calldata as the execution constraint mechanism. This is a genuine architectural similarity. The difference is in how those constraints are applied. Veda's constraints are configurable by whichever platform deploys a vault on its infrastructure, meaning the constraint quality depends on how carefully the builder configured the whitelist. Lucidly's Pashov audit documents the specific constraints applied to the syToken vaults, independently of any builder decision; the audit covers what these vaults specifically can and cannot do.

For institutional due diligence, what matters is having an independent audit that covers the specific vault's constraint configuration, not the infrastructure's general capability for constraints. The Pashov audit on the Details tab at app.lucidly.finance provides this. A Veda-powered vault's constraint quality depends on whether the platform that built on Veda commissioned an equivalent audit of their specific configuration.

Reporting and transparency

Veda provides standardised pricing and accounting at the infrastructure level. Individual Veda-powered products provide their own user-facing reporting. Kraken DeFi Earn shows a yield rate and account balance. It does not show current allocation breakdown by protocol, health factor on leveraged positions, or yield attribution by source.

The Transparency Dashboard at app.lucidly.finance provides all of these: live allocation on the Allocations tab, current health factor, Returns Attribution showing yield breakdown by source, and 45-day APY history. For an institutional allocator that needs quarterly position data that an auditor can independently verify onchain, Lucidly's reporting is built specifically for that use case. Veda's infrastructure supports it but doesn't require or standardise it across platforms that build on top. For the full evaluation framework on DeFi vault reporting standards, see the article on evaluating DeFi yield beyond APY.

Access model

Veda is accessed by building on it: it's a B2B infrastructure product. An institutional allocator doesn't use Veda directly; they use Kraken DeFi Earn or Ether.fi Liquid or another product built on Veda. The allocator's access experience, reporting quality, and compliance controls are determined by the distribution partner, not by Veda.

Lucidly's syToken vaults at app.lucidly.finance are accessed directly. No intermediary distribution partner. Connect a wallet, deposit, receive vault shares. The Transparency Dashboard and all reporting are available immediately without an enterprise agreement or a relationship with a distribution partner. A fund can open a position and begin monitoring it in real time the same day.

Multi-asset coverage

Veda's infrastructure supports arbitrary asset coverage across any chain and protocol, which is the point of modular infrastructure. Any Veda-powered product can theoretically support any asset.

Lucidly's three native syToken vaults cover the core institutional crypto allocation universe: stablecoins (syUSD), ETH (syETH), and Bitcoin (syBTC). A hedge fund running all three has a unified dashboard at app.lucidly.finance showing consolidated position data across all three vault strategies. That consolidation doesn't exist when deploying across multiple Veda-powered products from different distribution partners. For the institutional multi-vault context, see the article on hedge fund vault strategies and Lucidly's RWA yield playbook.

Where Veda has advantages

Veda's infrastructure scale is a real institutional signal. $3.7 billion in TVL across Kraken, Ether.fi, Lido, and other major platforms represents a security track record that Lucidly, as a more focused product, cannot match on pure duration and capital volume. For a compliance team evaluating infrastructure track record, Veda's deployments at major centralised exchanges are a credibility anchor that matters.

Veda also offers something Lucidly doesn't: the ability for an institution to build its own branded vault product on Veda's infrastructure. For a large asset manager that wants to launch its own yield product under its own brand with its own strategy configuration, Veda is the infrastructure layer. That's not a use case Lucidly serves; Lucidly serves institutional allocators who want a defined, audited yield product, not institutions that want to build their own.

The bottom line for institutional allocators

If a hedge fund's question is "which platform should I use to allocate institutional capital into a defined DeFi yield strategy with audited execution constraints and real-time reporting," the answer is Lucidly's syToken vaults at app.lucidly.finance. If the question is "which infrastructure platform should we use to build our own branded DeFi yield product," the answer involves Veda.

The Lucidly vs Veda question resolves quickly once the use case is clear. Veda and Lucidly are not competing for the same allocation decision. For the full competitive context across the institutional vault category, see the article on Lucidly's vault report versus the competition.

Frequently asked questions

Is Veda a competitor to Lucidly?

Not directly. Veda is vault infrastructure that other platforms (Kraken, Ether.fi, Lido) build yield products on top of. Lucidly is a direct-access institutional yield product with defined strategies and an institutional-grade Transparency Dashboard. An institutional allocator choosing between "using Kraken DeFi Earn" (which runs on Veda) and "using Lucidly syUSD directly" is making a product comparison. An institution choosing between "building our own vault product" and "using Lucidly's existing vault" is making a different decision, and for the build decision, Veda is the relevant infrastructure consideration. The syToken vaults at app.lucidly.finance are for the first category: direct institutional allocation into a defined, audited yield strategy.

What does Veda's BoringVault actually do?

Veda's BoringVault is a modular smart contract framework that handles vault share issuance, pricing and accounting, adaptive capital allocation across integrated protocols, and Merkle-verified permission constraints on permitted actions. It's the technical foundation that platforms like Kraken and Ether.fi use to offer yield products without building vault smart contracts internally. The BoringVault has $3.7 billion in TVL and multiple completed audits. For an institutional allocator, the BoringVault is infrastructure they interact with indirectly through whichever distribution partner has built on top of it, not a product they access directly.

How does Lucidly's execution constraint compare to Veda's Merkle-verified system?

Both use Merkle-verified whitelisted calldata as the architectural mechanism for constraining what execution engines can do. The difference is in what the audit covers. Veda's audit covers its general BoringVault infrastructure. The Pashov audit linked from the Details tab at app.lucidly.finance covers the specific constraints applied to Lucidly's syToken vaults: what these specific vaults can and cannot do, what happens in edge cases like key compromise, and how health factor monitoring prevents unauthorised leverage increases. For institutional due diligence, the specific vault audit is the document that matters, not the infrastructure audit; both Veda-powered and Lucidly vaults depend on their specific configuration and audit, not just their underlying architecture.

Can an institution use both Veda-powered products and Lucidly simultaneously?

Yes, and for many institutions with broad DeFi allocations, using both makes sense. A fund might hold Ether.fi Liquid BTC (a Veda-powered product from a branded platform) alongside syUSD and syETH at app.lucidly.finance for unified institutional reporting on the stablecoin and ETH portions of its allocation. The Lucidly Transparency Dashboard covers the syToken vaults; the Ether.fi interface covers its own positions. There's no protocol-level conflict between holding both. Lucidly's dashboard covers its own vaults only, not positions in external platforms. For a fund that wants truly consolidated multi-platform reporting, building a custom aggregation layer is the institutional solution.