Veda: BoringVault DeFi engine — architecture, API, and chain map for builders

Veda: BoringVault DeFi engine — architecture, API, and chain map for builders. Official docs: docs.veda.tech. Marketing home: veda.tech.

Click to zoom

What Veda is

Veda positions itself as a DeFi vault primitive — a mechanism for pricing, accounting, securing, optimizing, and automating capital — sitting above lending markets, DEXs, and staking. Partners (fintechs, asset issuers, exchanges, wallets) white-label Earn products without rebuilding vault + ops infrastructure. Public claims on the marketing site include large lifetime volume and deployments such as Kraken DeFi Earn, EtherFi Liquid Vaults, Lido Earn, and wallet distribution (verify current logos on veda.tech).

BoringVault architecture

Docs describe a modular stack with a intentionally thin core (~100 lines of “boring” custody logic) and external modules:

Source map: Architecture & flow of funds.

Curation vs DIY

Veda Curation Services is the managed path: Veda acts as strategist (monitor protocols, rebalance, liquidity risk). Partners who want in-house strategy still use the same vault + API surface; curation is optional ops, not a different product category.

Partner API

Base URL https://api.veda.tech. Auth: Bearer API key from console.veda.tech. OpenAPI: api.veda.tech/docs. Doc index also ships llms.txt.

# Health check (requires Console API key — never commit keys)
export VEDA_API_KEY="veda_user_live_…"

curl -sS "https://api.veda.tech/v1/tx-builder/health" \
  -H "Authorization: Bearer $VEDA_API_KEY"

# Further surfaces (see docs paths):
# - Vaults listing / roots
# - Policy manager + Merkle trees by root
# - Transaction builder for rebalance calldata
# Full reference: https://docs.veda.tech/api/api-reference

const BASE = "https://api.veda.tech"

export async function vedaHealth(apiKey: string) {
  const res = await fetch(`${BASE}/v1/tx-builder/health`, {
    headers: { Authorization: `Bearer ${apiKey}` },
  })
  if (!res.ok) throw new Error(`veda health ${res.status}`)
  return res.json()
}

// Chain slug is lowercase path param on chain-scoped endpoints
// (see docs chain-support). Example shape only — confirm path in OpenAPI.
export async function vedaVaults(apiKey: string, chainSlug: string) {
  const res = await fetch(`${BASE}/v1/${chainSlug}/vaults`, {
    headers: { Authorization: `Bearer ${apiKey}` },
  })
  // If 404, use the exact paths from api.veda.tech/docs for your tenant.
  return { status: res.status, body: await res.text() }
}

Docs pages to bookend integration: Quick start, Vaults, Policy / Merkle, Transaction builder.

Chain support (honest)

Published mainnet slugs (as of docs scrape) are not Solana: ethereum, arbitrum, base, optimism, linea, bnb, scroll, unichain, ink, berachain, sonic, flare, katana, hyperevm, plasma, sei, monad — see chain support. For Solana builders this is still useful as:

• a reference architecture for institutional Earn / vault products;
• a multi-chain vault API pattern (Merkle policy + tx builder);
• a corridor note when users hold EVM vault shares and want Solana primary liquidity (bridge/stack is outside Veda’s listed chains today).

Do not claim “Veda on Solana” until the chain table includes it.

Security posture (docs framing)

Docs split risk into smart-contract vs economic, and point at smart contract security + audits pages. Treat audits and “zero incidents” marketing as claims to verify on the security pages and third-party reports — not as a substitute for your own integration review.

When to open the docs

1. Designing a white-label Earn / yield product on EVM L2s.
2. Automating rebalance / strategist ops via API + Merkle policy.
3. Comparing vault standards (BoringVault) to in-house vault designs.
4. Mapping chain IDs for multi-chain dashboards (slug table).

Links