Trust center

Veda Security

Veda’s embedded earn products are powered by heavily-audited smart contracts featuring enterprise-grade admin, compliance and risk controls.

Capital held within a boundary: concentric tracks around a single sphere
12+
third-party audits
$32B+
volume handled
$1M
bug bounty
Audited by
Certora
0x Macro
Spearbit
Sigma Prime
01 — Controls

Security overview

Four security pillars: the vault contract, access controls, monitoring, and 3rd party audits.

Smart contract security

The core vault contract, BoringVault, is deliberately minimal. Onchain permissions restrict strategy actions to approved contracts, functions, and parameters (enforced via Merkle proofs). Exchange-rate updates are bounded to limit abnormal accounting changes.

Access & change controls

Role-based permissions, MFA, segregated production environments, and secure key management protect privileged access. Vault-configuration signing is cryptographically attested from development to execution.

Monitoring & response

Veda monitors onchain activity and supporting infrastructure 24/7, with automated health checks and documented incident response. Third-party blockchain threat detection complements internal monitoring.

Independent review

In addition to a robust internal security reviews, over 60 audits, as well as formal verification specialists continuously review and battle-test the architecture. Ongoing fuzzing and code reviews provide continuous scrutiny.

02 — Authority

Roles and permissions

Who can do what, what happens when systems fail, and what an enterprise can verify.

CapabilityWho can actPrimary guardrail
Arbitrary transfer of customer funds Nobody Vault permissions do not allow arbitrary withdrawals by Veda or the enterprise.
Strategy execution & rebalancing Authorized strategy operator Every action must match the vault’s pre-approved onchain permissions for destination, function, and parameters.
Exchange-rate updates Designated rate updater Rate updates are limited in how often and how far they can move; out-of-bounds changes can automatically pause updates.
Sensitive configuration changes Authorized administrators Sensitive roles are timelocked; vault-configuration signing requires direct confirmation through secure channels.
Emergency pause Authorized emergency operators Can pause affected activity but cannot redirect customer funds.
03 — Resources

Operational security & diligence

Platform security

Production and non-production environments are segregated; vulnerability management and peer-reviewed infrastructure changes reduce operational risk.