FypherX Docs
Product and Operating Guide
This documentation reflects the current FypherX implementation: wallet-linked subaccounts, perpetual markets, admin controls, risk automation, settlement relays, and treasury rails. It avoids product claims that do not exist in the code.
Live references pendingWalletConnect not configuredUpdated Not synced yet
Live Markets
0No market data loaded
Core Services
CheckDashboard not loaded
Oracle
DisabledOracle status not loaded
Settlement
OffSettlement overview not loaded
Collateral Tokens
0Registry not loaded
WalletConnect
DisabledThis deployment needs a WalletConnect project ID
Introduction
FypherX is a wallet-connected perpetual DEX built around offchain matching, subaccount-based cross-margin, automated risk operations, and an operator-facing control plane. This page is written against the current codebase and live frontend, not against an aspirational roadmap.
Quick Start
Step 1
Connect a wallet from the top navigation.
Step 2
Create a subaccount from the wallet flow.
Step 3
Deposit margin into that subaccount.
Step 4
Place a limit or market order on the Perps screen.
Step 5
Verify balance, reserved margin, and positions in Portfolio.
Step 6
Use /admin manually for operator-only monitoring and controls.
What FypherX Includes Today
Trading Surface
The live trading path is the Perps terminal. Orders route through the gateway, enter the matching engine, reserve margin in risk, and generate settlement work after fills.
Account Model
Wallets map to one or more subaccounts. Each subaccount tracks balance, available balance, equity, reserved margin, open positions, and PnL independently.
Operations
Admin APIs and the hidden
/admin screen expose engine mode, kill switch, market blocking, oracle freshness, funding jobs, liquidation jobs, insurance fund state, and settlement relayer status.Onchain Rail
Settlement and insurance fund vault rails are scaffolded and wired into the current backend. They are operational rails, not end-user yield products.