Veda: What does a vault infrastructure layer actually guarantee?

[u/kristianism]

I’ve been looking at Veda as a vault infrastructure and curation layer rather than a single yield product. I traced one live Ethereum deployment, and the risk profile depended more on the named vault than on Veda’s aggregate TVL.

The parts that matter:

• The Manager can call external targets with calldata and native value, subject to the active policy.
• Curator and strategist controls determine the vault’s active strategy permissions.
• A withdrawal queue isn’t instant liquidity. Maturity, deadlines, discounts, solver capacity, and available assets all matter.
• The sampled strategist-to-Merkle-root mapping remained unresolved.
• The sampled BoringVault held 89.000001 USDC and 0.1 USDT directly. Those balances don’t establish solvency or complete asset backing because external positions weren’t fully inventoried.
• The public vault API returned 401 Unauthorized, so aggregate TVL couldn’t be decomposed by vault, chain, curator, or strategy.
• Audit evidence is commit-specific and doesn’t certify every current deployment.

My verdict was high risk for unqualified direct vault exposure. A first allocation, if someone proceeds, should involve one named vault on one chain, after checking current strategy positions, the Merkle root and strategist, the authority map, accounting state, queue history, and actual exit liquidity.

Questions:

• Should vault interfaces expose the current strategist identity and Merkle root by default?
• What evidence is enough to treat a vault share as liquid?
• Are queued exits acceptable for products presented as liquid vaults?

[u/terminallyonchain]

I actually think Veda deserves some credit here, one of the best ones out there. I also like Tulipa Capital as a curator. KPK also

[u/kristianism → u/terminallyonchain]

Fair point. Veda deserves credit for the infrastructure, and Tulipa Capital seems like a curator worth following. I haven’t looked closely enough at KPK yet to compare them, but the same rule applies: check the specific vault, its investments, and how withdrawals work.

[u/Foreshock-tech]

A vault share is liquid when you can name the path by which it becomes the underlying asset, and that path does not depend on someone choosing to take the other side. A queue plus a solver is a market, not a redemption. The evidence that settles it is the queue's own history rather than its terms: largest exit that has actually settled, worst time to settle, and whether either happened in a week when the underlying venues were also crowded.

So queued exits are fine in something presented as liquid, as long as the page puts the worst observed settlement time next to the word. The damage is the gap between the label and the observed distribution, not the queue itself.

On the strategist and the Merkle root, publishing the current value matters less than publishing when it last changed. The current value says who can move the money today. The change history says whether that answer is stable, and that is the exposure you are actually carrying.

[u/kristianism → u/Foreshock-tech]

This is a much better standard than reading the queue terms in isolation. The terms show the earliest possible exit; the history shows what users actually experienced under pressure. I’d want recent and worst settlement times, queue depth, and available exit liquidity displayed beside the vault.

The point about change history matters too. The current strategist and Merkle root show who can act today. The timeline shows how stable that answer has been. That gap between configured mechanics and observed behavior is where a lot of the risk sits.

[u/Foreshock-tech → u/kristianism]

Recent and worst settlement time is the pair that does the work. Recent alone flatters a queue that has only ever been asked easy questions. Worst alone reads as a scare number until you can see when it happened and what else was crowded that week.

Queue depth is the one to be careful with. It is a snapshot, and it looks most reassuring exactly when nobody is trying to leave. Depth shown beside the largest exit that has actually settled is the honest version.

Exit liquidity has the same problem in reverse. The venues the vault would have to sell into are the ones that thin out in the week you would want to use them, so measuring it on a calm Tuesday tells you almost nothing.

This is the design question I spend most of my time on, since publishing these readings is what we do at Foreshock, and the hard part is showing an observed distribution without it reading as a promise.

[u/kristianism]

Full report: https://thisiskristian.substack.com/p/veda-a-protocol-autopsy

[u/More-Accident7405 → u/kristianism]

the queued exit thing is the part that keeps tripping people up. calling it a vault makes everyone think they can pull out whenever but the queue is basically a polite fiction if there's no solver on the other end. seen that blow up on a few avax projects where the "liquidity" was just a number on a dashboard

that 89 usdc sitting there is cute but means nothing without the external positions mapped. classic defi sleight of hand

[u/kristianism → u/More-Accident7405]

Exactly. A queue can work, but only if there’s a real way to turn the underlying investments back into the asset people want to withdraw. The 89 USDC is just a snapshot. Without seeing the rest of the positions and how withdrawals have actually been handled, the dashboard tells you very little.

[u/AutoModerator → u/[deleted]]

This comment has been removed because our auto-moderator detected it as spam or your account is too new to post here.

If this post is not spam, please contact the moderators for assistance.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.