Phoenix: Solana perpetuals, collateral and withdrawal controls

Phoenix offers leveraged perpetual futures on Solana. Positions provide long or short exposure to a reference asset and settle through collateral and profit-and-loss accounting; buying a perpetual does not deliver the underlying coin, share or commodity. This profile concerns the current perpetuals service. Phoenix Legacy, the older order-book programme maintained in a separate Ellipsis Labs repository, has its own code and audit history. Those materials should not be treated as a security assessment of the current derivatives deployment.[2][27]

Its matching engine combines ordinary resting limit orders with spline liquidity, a quoting mechanism available to authorised market makers. Price takes priority across both sources. Within the ordinary book, earlier orders at the same price have priority; where spline and ordinary liquidity quote the same price, the spline fills first. A displayed order book therefore contains more than a queue of conventional limit orders. Actual depth, price bands and the incoming order’s execution budget determine the obtainable fill.[3]

Traditional-asset pricing needs an additional check. Equity reference prices use an external 24/5 window, Sunday 8 p.m. to Friday 8 p.m. Eastern Time. When that window closes, Phoenix uses internal order-book-based pricing. Commodity markets also switch to internal pricing during closures. An available trading screen does not mean that the underlying cash market is open or supplying fresh prices. Phoenix states that these USD reference prices receive no USDC/USD spot correction, leaving a separate stablecoin denomination consideration.[23]

A stop is an execution instruction, not a guaranteed exit price. Phoenix’s conditional orders are reduce-only, but trigger choice, allowed slippage and remaining liquidity still matter. Cancelling a parent limit order cancels its attached children; already independent conditionals require their own management.[5]

The account documentation allows up to 64 resting bids and 64 resting asks per market and 128 active positions in the cross account. These capacity limits do not assure sufficient margin for every permitted order.[8]

Illustrative fee calculation: a 20,000 USDC notional entry executed as taker costs 7 USDC, because 20,000 × 0.00035 = 7. An equal-notional maker exit costs 1 USDC, giving 8 USDC in base trading charges. Two taker fills would cost 14 USDC. These examples assume unchanged notional, no referral discount and no builder fee; they exclude funding, price movement, spread, slippage and network costs. Leverage changes the collateral supporting that notional, not the notional on which these trading fees are calculated.[6]

Funding transfers value between the two sides of a market: a positive rate generally charges longs and credits shorts, with the direction reversing when the rate is negative. Pending funding already enters account health before settlement. The rate displayed for one observation should not be projected as a fixed overnight tariff. A holding-cost comparison needs the actual market, position size, time interval and sequence of funding accruals.[10]

Referral pricing is distinct from the builder surcharge. The published referral programme gives an eligible new user a 10% trading-fee reduction during the first 100 million dollars of referred volume. Referrers need 10,000 dollars of lifetime volume to generate a code; rewards update weekly, with a 1 USDC minimum claim. The documents describe claimed rewards as USDC credited to the referrer’s spot balance. This is not evidence that an unrelated points balance or an advertised future reward is withdrawable cash.[20]

USDC deposits pass through Ember, which wraps the token one-for-one into the protocol’s collateral representation; the withdrawal flow reverses the wrapper. A wallet balance and a Phoenix trading balance are separate steps. SDK operations build transactions for the authorised wallet to sign rather than converting an unsigned request into permission to move funds. The wallet must retain sufficient SOL for relevant network costs and account creation.[15]

Native SOL support has a dated integration notice for 16 September 2026. SOL remains in the trader account as lamports, without first becoming wrapped SOL or USDC. A third-party screen that still calculates margin using only USDC may consequently understate collateral and misreport health. SOL adds collateral without changing an existing position’s direction, entry price or size. Its changing price can nevertheless alter the account’s available margin.[14]

For a margin illustration, suppose 10 SOL has an index value of 150 USDC each and the applicable margin credit is 80%. Its 1,500 USDC market value contributes 1,200 USDC to margin: 10 × 150 × 0.80. The remaining 300 USDC is a risk haircut, not a charge paid to Phoenix. This example assumes those prices and settings; it does not calculate a position’s liquidation price or its withdrawable USDC.[7]

Cash settlement can create a different constraint from market losses. Realised losses, fees or funding may leave a negative cross-account USDC balance even while SOL remains in the account. The FAQ says such a balance blocks withdrawals until repaired. Automatic SOL conversion can occur when projected cross-account USDC debt exceeds half of discounted SOL value; an isolated account may also convert SOL after its position closes. Unrealised losses alone are not the conversion trigger. Selling collateral and closing a perpetual are separate events.[13]

Non-custodial access still exposes deposited collateral to programme rules. The owner authority controls funding and signer assignment; a position authority can trade without receiving withdrawal permission. A separate trading signer therefore limits direct transfer authority, but it can still create losses through trading. Different portfolios have separate risk; within one cross portfolio, gains, losses, funding and order reservations interact.[8]

Initial margin is calculated using a position-size tier. Crossing into a lower-leverage tier can increase the requirement for the whole position, including size already open. Risk-increasing resting orders also reserve capacity. A new order may consequently fail even when its standalone size appears small, because the existing position and other orders have already used the account’s margin budget.[11]

The terms reserve administrative powers, including upgrades, pauses, parameter changes and emergency actions, to the company or its designees. Wallet ownership therefore coexists with protocol and interface controls. No customer insurance entitlement was established from the security material reviewed.[25][30]

The interface terms require adult, lawful users and exclude US, Canadian and UK persons under their specified location, residence, citizenship and incorporation tests, alongside sanctions restrictions. Connecting a compatible wallet does not establish eligibility.[25]

The privacy policy says core wallet access does not require conventional identity information such as a name or government ID. It nevertheless describes processing wallet addresses, IP-derived location, device details and public blockchain activity. Email-based embedded-wallet onboarding is a separate route described in the getting-started guide. Neither the privacy policy nor successful wallet connection is evidence of permission to offer derivatives in every country.[26][1]

Trade and funding records answer different questions. Fill history identifies executions and realised results; funding history accounts for transfers while positions stay open. Preserve the relevant wallet, portfolio and subaccount identifiers when reconciling them with blockchain transfers. The reviewed history endpoints are evidence of retrievable records, not a promise of a jurisdiction-specific tax statement or a fully reconciled tax calculation.[28][29]

Network congestion can delay an instruction after it is submitted. An interface refresh or closed browser is not evidence that an order was cancelled or a position closed. Confirm the transaction and account state before submitting replacement instructions. The risk warning documents potential loss of access during Solana outages; no telephone dealing facility or guaranteed emergency manual exit was established.[22]

Formal notices go to [email protected]. The terms provide a 15-day response period and a 30-day informal-resolution stage before the specified Panama arbitration process, subject to the agreement and applicable law.[25]

A named Panamanian interface company and non-custodial architecture do not themselves establish a derivatives licence. No positive regulatory permission is recorded here; the reviewed terms allocate jurisdictional compliance to users.[25]

Operator

Solstice Technologies S. de RL.

Exchange model

Decentralised

Service scope

Current Solana perpetuals; Phoenix Legacy is a separate programme.

Client types

Retail clients; Professional clients; Institutional clients

Pricing publication

Public pricing

Funding scope

Solana USDC and native SOL; documented Relay routes; withdrawal health and capacity controls.

Custody and asset handling

Wallet access with protocol-held collateral, delegated trading authority and administrative controls.

Client eligibility

Adult lawful users; geographic and sanctions restrictions apply.

Support

Documentation, official Discord, history APIs and contractual notices route.

Authorisation and registration scope

No independently verified derivatives permission entered.

Exchange metadata checked 21 Oct 2026Source 26Source 2Source 8Source 7Source 9Source 25

The Rise SDK separates API authentication from transaction authority. Session tokens support authenticated services; they do not replace the Solana signature required to submit a trading or collateral operation. Logging out of an API session is consequently a different action from revoking a trading signer or cancelling resting orders. An integration should identify whether it holds only data access, a position authority, or the owner’s broader signing capability.[16]

The documented CLI supports macOS and Linux and includes agent integrations. Its MCP interface is read-only by default; live-capable operation requires explicit enablement and an unlocked wallet. That is a material authority boundary: an AI assistant answering questions is different from an agent connected to a process that can sign transactions. The documentation states that private keys remain in the local process, but the trader still has to manage the permissions granted to that process.[17]

Strategy runners include TWAP, grid and technical-analysis workflows. Paper mode simulates; dry-run builds without submission; confirm-each prompts for live steps; automatic execution can submit without a prompt for each trade. The local runner can enforce per-step or per-run notional limits, exposure limits and price-drift checks, pausing when a guardrail is breached. These tools require an operating runner and monitoring. A simulation result does not demonstrate that the same orders would fill in a live market.[18]

The separate Flight Club page describes a four-week reward period from 27 July to 23 August. That published schedule is historical by this profile’s 21 October 2026 check date; it is not presented as an open promotion. The page describes distributed USDC rewards without vesting, but publication of a programme is not proof that a particular account has received an allocation.[21]