arrows-up-down-left-rightScope & Positioning

Purpose of SAFV

SAFV is designed to:

  • abstract the complexity of Supra AutoVault primitives

  • standardize vault construction, interfaces, and lifecycle

  • improve composability, auditability, and developer ergonomics

  • enable rapid deployment of fully automated financial strategies

SAFV does not redefine AutoVaults. It provides a canonical construction layer for building consistently on top of Supra’s native execution environment.

Position in the Supra AutoFi Stack

SAFV operates strictly as a middleware layer.

Layer—Responsibility

  • Supra AutoFi—MoveVM execution, native automation, oracles, and risk primitives.

  • SAFV—Vault construction framework, standards, templates, abstractions.

  • Applications — Strategy vaults, index products, delta-neutral systems, trading strategies.

This separation is intentional and foundational to the long-term scalability of the ecosystem.

  • Supra AutoFi defines what is possible

  • SAFV defines how it is built

  • Applications define what users interact with

What SAFV Is — and Is Not

SAFV Defines

  • a standardized framework for constructing strategy-driven vaults

  • reusable abstractions for strategy execution and asset issuance

  • design principles informed by DeFi practice and structured finance theory

SAFV Does Not Define

  • a consumer-facing product specification

  • a no-code strategy studio

  • governance, incentives, or token economics

These are downstream layers that can be built on top of SAFV without modifying the framework itself.

Relationship to AutoVault, AutoRisk, and AutoFi

  • AutoFi provides the execution environment

  • AutoVaults provide trustless execution containers

  • AutoRisk provides protocol-level risk primitives

SAFV sits above these primitives.

It does not replace or compete with them. Instead, it captures their capabilities into a repeatable construction model that developers can rely on across products.

Terminology Note

Throughout SAFV documentation, the term “asset” refers specifically to tokenised claims on strategy-driven vaults.

It does not refer to:

  • standalone speculative tokens

  • discretionary financial instruments

  • governance representations

Asset value in SAFV is derived exclusively from deterministic, on-chain execution enforced by vault and strategy logic.

Last updated