Current System Guide

The app opens with wallet sign-in and invite access checks. If your wallet is not admitted for a feature, use the access request screen from that feature page.

Common wallets include Phantom, Solflare, Backpack, Coinbase Wallet, and compatible WalletConnect flows. Futures and bot-key management require a wallet that can sign messages and versioned transactions.

Gated products: Futures, Auto, and Lending can be enabled per wallet. Their pages may render an access request gate before the product UI.

Every landed transaction pays the normal Solana network fee in SOL. Keep a small SOL buffer even when the trade itself uses other tokens.

Some routes can include priority fees. These are paid only by the transaction that lands and are shown as part of the wallet or transaction flow when applicable.

Protected can ask the wallet to sign a Jito primary transaction and an RPC fallback. If the Jito variant lands, it can include a Jito tip. If the RPC fallback lands, the Jito tip is not paid. Private required requires Jito and fails instead of falling back to public RPC.

First-time actions can also require rent or account creation costs. Common examples include token accounts, futures isolated-margin accounts, collateral accounts, LP permission or position accounts, and other product-specific on-chain records.

/exchange is router-backed. The UI does not call legacy AMM pool bindings directly. The router quotes, builds a transaction plan, your wallet signs, and the signed plan is submitted through Jito, RPC, or both.

Settings can show route preferences such as Dart, RFQ, and External. The route label before review tells you whether the quote is using a Dart route, External routing, or RFQ. Review route, fee, price impact, slippage, and minimum received before signing.

If router pricing is degraded, the swap card shows fallback pricing status and can tighten spreads or maximum size. Connected wallets can also view private spot trade history and receipts from the exchange UI.

/futures is a gated perps terminal. The first-time flow initializes an isolated-margin account, deposits collateral, then requests and accepts exact-fill quotes.

Production perps execution uses signed exact-fill quotes accepted by the on-chain Percolator fork through AcceptFirmQuote. A valid accept fills the full quoted size at the full quoted price or the instruction fails atomically.

Risk checks, account state, collateral accounting, fees, funding snapshots, quote nonce updates, and settlement effects are enforced on-chain when the signed transaction lands. Quote generation, routing, keeper cranks, schedulers, hedgers, and trigger monitoring are off-chain services.

The quote panel shows price, size, fee, inventory charge, funding, estimated liquidation, request id, and slots remaining. The action button can block while the keeper is syncing, quotes are paused, or the connected wallet cannot complete the required signatures.

Futures supports take-profit and stop-loss triggers when trigger support and the trigger delegate are available for the selected market.

Enabling automation configures the delegate used by the trigger worker. Triggers can close the full position, reduce by percent, or reduce by base size. They move through armed, fired, failed, and cancelled states.

Trigger execution still uses the exact-fill perps flow. Trigger failures can happen when the market is paused, the keeper is stale, a quote expires, the position changes, or the delegate is no longer configured.

/pro is an advanced trading workspace with chart styles, drawing tools, price alerts, webhook URLs, local alert history, staged chart orders, and ticket handoff.

Chart drawings, alerts, webhook URLs, and staged orders are stored locally in the browser unless synced by the specific feature. A staged chart order is planning state until you send it to a ticket and complete the wallet-signing flow.

/auto is gated automation for bounded cross-venue strategies. It supports templates such as Accumulate + Earn, Protected Long, and Cash Manager.

Strategies have explicit objectives, venues, guardrails, permissions, control modes, simulations, action logs, and webhook destinations. A strategy should be simulated before activation, and changes that require reapproval must be reviewed before going live again.

Advisory mode records recommended actions. Guarded Auto is bounded by wallet-scoped permission caps such as max notional per order, daily notional, max leverage, and allowed markets.

/liquidity exposes the current router-backed liquidity surfaces. Public spot swaps currently route through Dart liquidity where the relevant market is live.

LP deposit and withdraw drafts can require an on-chain lp_permission record for the wallet. RFQ routes quote against managed market-maker inventory and do not expose public LP shares.

The legacy strongtower LP surface remains hidden unless its configured pool is explicitly enabled, deployed, and verified on mainnet.

Invite codes admit wallets into early access. If your wallet is not admitted, the access screen can ask you to redeem a code or submit an access request.

Signed-in wallets can create a public referral username from settings when the username is available. The referral link uses that username, not a wallet address.

If someone opens a referral link before signing in, the app can remember that referral locally. When the referred user later signs in, the referral can be bound to that wallet.

Users can copy and share their referral link from settings. If a referral link is disabled or a username is unavailable, the UI shows that state before saving or sharing.

Invited users can create per-wallet bot API keys at /settings/api-keys. The default scopes are quotes:read and swap:build; relay requires relay:send and Auto access.

Bot auth headers are x-dex-key-id, x-dex-timestamp, x-dex-nonce, and x-dex-signature. The HMAC message includes method, path with query, timestamp, nonce, and SHA-256 body hash.

The secret is shown once when the key is created. Store it in a password manager or bot secret store, and revoke the key if the secret may have been copied or exposed.

Scope meanings: quotes:read can request quotes, swap:build can build swap plans, and relay:send can relay signed transactions for wallets with the required feature access.

Public bot endpoints include POST /api/bot/quotes, POST /api/bot/swap, POST /api/bot/relay, GET /api/bot/ready. Bot requests are bound to the wallet that created the key.

Perps integrations should use the router-backed perps proxy family for account init, collateral, quote, accept, submit, receipts, funding, triggers, and delegate setup. The retired futures cosign path is not the current integration path.

For deeper request signing and integration details, use the repo API reference and integration quick start.