Protocol Architecture
Understanding the modular components that create Vantum's stealth environment
Overview
The Vantum Protocol is composed of several modular components that together create a stealth environment on Solana. Each component serves a specific purpose in maintaining privacy while ensuring security and usability.
A centralized pool smart contract that holds deposited SOL/USDC
Non-minted, protocol-tracked token balances representing user deposits
User-specific secondary wallet addresses used exclusively for vToken actions
Jupiter-based router with optional output redirection
A security layer that analyzes token behavior & smart contract metadata
Tracks internal balances & transfer logic without exposing public txs
Transaction Flow: Deposit → Transfer → Withdraw
User sends SOL/USDC to a Vault
In return, they receive an internal v/SOL or v/USDC balance (not an SPL token)
The user interface reflects this in "Vantum Protocol Mode"
User selects another Vantum address to send vTokens to (e.g. VantumXa4L...)
The transfer is processed off-chain (ledger) or via PDA updates
No SPL token movement happens on-chain → zero trace
The recipient withdraws vTokens from their stealth balance
Vantum Vault releases equivalent amount of real SOL/USDC to their public address
Stealth Address System
Each Vantum user is assigned a ghost-style address upon switching to Protocol Mode. This is not a standard Solana wallet but a virtual account controlled via the protocol.
Properties:
- Not discoverable via block explorers
- Not tied to public Solana address
- Cannot receive SPL tokens from outside
- Only interacts within the Vantum system
Internal Balance System
Balances are tracked in two possible ways, offering flexibility between speed and decentralization:
All vToken balances are held in a backend server (verifiable and open-source)
Offers best privacy but requires backend infrastructure
Each stealth address has a Program Derived Address (PDA)
PDA stores the internal balance, updated only via the protocol's instructions
Note: Both options are modular and may co-exist depending on the deployment configuration.