VaultVision Manager OS

Multi-market vault infrastructure

Managers trade. Depositors hold shares. VaultVision supplies the rails.

Not a VaultVision-managed vault. The bigger product is infrastructure for managers who want Hyperliquid-style vaults across crypto perps, HIP-3 markets, and eventually outcome markets.

The wedge starts with proof, grows into rails

Product stack

Now

proof

Public vault reads, manager context, risk cards, allocator diligence.

console

Manager UI for positions, limits, policy headroom, and market whitelist.

Then

rails

Policy-checked order routing into crypto perps and HIP-3 markets.

Later

vaults

HyperEVM accounting, shares, withdrawals, and protocol-level fee split.

Architecture the small version

Core modules

VaultFactory

Creates/registers vaults. Manager wallet, market universe, fee schedule, risk policy, profile slug.

Accounting

Deposits, shares, NAV, high-water mark, fees, and withdrawals. Frontend numbers are never canonical.

Policy

Allowed markets, leverage, exposure, concentration, drawdown brakes, manager skin, max order size.

ExecutionRouter

Validates order intent, signer, builder fee approval, nonce isolation, and routes to HyperCore/HIP-3 rails.

NAV Engine

Reads official state, prices, balances, and positions. Fails closed when critical state is stale.

WithdrawalQueue

Instant when liquidity exists; queued/unwound when positions must be closed. Status is public to the depositor.

FeeSplitter

Manager fee, VaultVision software/order-routing fee, and depositor priority rules in one auditable schedule.

Security invariants before any real deposit

Non-negotiable

Manager can trade, not steal.

The manager gets execution control inside policy limits. They do not get raw withdrawal power over depositor principal.

VaultVision can earn, not custody.

Setup, SaaS, builder-code routing, and future fee splits are allowed. Unilateral movement of user funds is not.

NAV fails closed.

If price, position, or balance state is stale, the system should stop new risk and mark the vault as needing review.

Withdrawals are explicit.

A cross-market vault cannot pretend every withdrawal is instant. Liquidity and unwind rules need to be visible before deposit.

Build path without pretending contracts are ready

MVP ladder

Proof pages

Manager profiles, public reads, and weekly cards that close trust gaps now.

Paper vault

Multi-market simulator with shares, NAV, fees, and withdrawal queue.

Console

Read-only then paper manager UI for crypto perps and HIP-3 markets.

Private rails

Restricted agent wallets, policy checks, and builder-code fee tests.

HyperEVM vault

Audited accounting, tokenized shares, CoreWriter integration, public beta.

Revenue model clean and honest

Fee loop

setup_feemanager onboarding, profile, proof surface, policy setup

saasmanager console, risk monitor, proof cards, allocator reporting

builder_codeorder-routing fee where Hyperliquid approvals support the exact flow

future_splitcontract-level management/performance fee split after audit and legal review