Liquidity depth per major asset
Veda (BoringVault)'s assessment for RD-F-065 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Veda uses a solver-based BoringQueue for withdrawals — no AMM pool or instant liquidity. Withdrawal maturity delay + solver capital determine exit throughput. No public data on maximum daily withdrawal capacity or solver depth. The $5.07B TVL decline from Aug 2025 to May 2026 was absorbed without a documented withdrawal crisis, which is mild evidence that the queue mechanism handled the unwind. However, a rapid coordinated exit could create queue backlog. Yellow due to absence of published solver-depth metrics.
Sources #
- InternalVeda data cache — rekt incidents and TVL trend00-data-cache.json: rekt.incidents=[], no withdrawal crisis documented; TVL drawdown from $6.145B peak absorbed without incidentretrieved 2026-05-17
- Veda Architecture & Flow of Fundsdocs.veda.tech architecture: BoringQueue solver-based withdrawal — time-delayed maturity, third-party solvers fulfill requests by delivering underlying assetsretrieved 2026-05-17
Methodology #
Measure on-chain liquidity depth for protocol-held assets at 2% and 5% price impact in USD.
See the full factor methodology and distribution across all protocols →