Featured guide
Security model for wallet-native approvals
Understand what FlowVault stores, what the wallet owns, where simulation happens, and how policy decisions become a record trail.
Documentation hub
FlowVault turns prepared Raydium and Solana actions into review cards: plain-language route evidence, wallet-native signing boundaries, policy checks, and a receipt trail your team can inspect later.
review-card.json
The minimum context before signing
{ route: 'USDC -> Raydium CLMM -> SOL', simulation: 'USDC -1,240 / SOL +7.82', policy: 'review_required', wallet: 'signer remains external', receipt: 'saved after decision'}Raydium route facts
FlowVault does not ask a reviewer to infer route risk from raw transaction data. The review surface carries the details that change the decision.
Concepts
Start with review cards, then move outward to policies, Raydium route data, wallet boundaries, and receipts.
A compact packet of route data, simulation output, policy state, and the exact wallet action being requested.
FlowVault prepares and explains. The connected wallet remains the signer and private-key boundary.
Pools, quote age, price impact, token mints, expected receive amount, and route hops are shown before approval.
Workspace rules decide whether an action passes, requires review, or is blocked before it reaches signing.
Every decision keeps the human-readable context beside the transaction signature or rejection reason.
Review card anatomy
policy.flow
A policy is readable before it is enforceable
policy balanced { max_quote_age: 30s review_if_slippage_above: 0.30% block_unknown_mints: true record: route + simulation + signature}raydium.inspect
Route context is carried into the receipt
route.raydium.inspect({ spend: '1240 USDC', receive: '7.82 SOL', quoteAge: '18s', priceImpact: '0.31%',})Next guide
The focused guide covers wallet-native signing, simulation, policy checks, and the record trail in the order a transaction moves through FlowVault.