edgeX exchange profile

edgeX is an order-book trading platform whose current V2 environment differs materially from its earlier StarkEx product. V2 separates matching and risk processing from settlement, and its technical documentation describes an Arbitrum-based transitional rollup framework. The current profile therefore treats V2 as the main product and labels older USDT, margin and withdrawal guidance as V1 information. A familiar brand name does not make those operating rules interchangeable.[2]

The current V2 API exposes spot/perpetual asset movements, order management, account state and separate market-data connections. Its documentation explicitly distinguishes the complete platform API from the narrower coverage of a particular SDK. A function appearing in an architectural overview should therefore be checked against the current API and interface before it is treated as a usable customer feature.[19]

The older general order guide describes a four-week default good-till-time limit. Its TP/SL tutorial describes reduce-only market exits attached after a position opens and triggered by last traded price. V2 supports a wider instruction and trigger set. Those older tutorials are useful for understanding the legacy interface, but they do not justify a universal four-week expiry or last-price-only statement for current V2 orders.[10][11]

Current V2 account endpoints allow a contract’s margin mode to be changed between cross and isolated, with an additional signed action. Contract-specific leverage settings can override the account default. This differs from the older guide’s use of separate USDT sub-accounts to isolate exposure. Moving collateral away or changing leverage can alter liquidation risk; choosing isolated margin does not make a position immune from liquidation.[22]

Funding is a transfer between long and short positions held at the relevant assessment time: positive rates charge longs, while negative rates charge shorts. The rate can change, and closing before an assessment differs from holding through it. Read the live contract interval and funding estimate instead of assuming one exchange-wide schedule. The general guide’s displayed calculation mixes position value and price, so this profile does not reuse that ambiguous formula.[15]

The sampled BTCUSDC, ETHUSDC and SOLUSDC contracts also configure a 1% liquidation fee.[24]

Execution cost also depends on the spread, available depth, slippage and liquidation events. The old fee page’s statement that edgeX covers settlement gas is specifically about V1; it does not establish free V2 bridging or free wallet transactions. A zero percentage in a withdrawal configuration also does not remove a minimum fee, network gas or route-specific charge.[14][25]

The current unified-asset API separates quoting, signing and submission. A withdrawal first obtains its fee, then constructs the net amount and typed-data payload, obtains the wallet signature and submits the asset flow. Retrieving deposit transaction data does not itself transfer funds. The route uses a separate asset API host, spot.edgex.exchange, and an explicit spot or perpv2 account destination. Confirm the asset, network, account, amount and fee in the actual signed request.[23]

Older onboarding permits an external EVM wallet or an email-based MPC wallet, with a six-digit email code in the illustrated flow. The guide’s USDT/Arbitrum deposit instructions belong to that older product. Email access and possession of a trading signer are different controls: users need to know which wallet owns the assets and what recovery arrangements their wallet provider actually supplies.[6]

For an uncertain deposit or withdrawal, check the asset-flow record and transaction hash before submitting another signed request. The V2 flow includes a customer withdrawal identifier to support idempotent processing. A balance displayed in the interface, a submitted flow and a confirmed destination-chain receipt are different stages; the reviewed V2 guide does not promise a single completion time for every network and route.[23]

V2 documentation describes assets held in smart contracts and trade/asset actions authorised cryptographically, with execution batched for settlement. It also claims direct contract access if the ordinary interface fails. However, the reviewed V2 custody page does not provide a complete user-run emergency procedure, required proof package or processing deadline. That gap limits how precisely an outage exit can be planned from the public guide alone.[3]

Legacy V1 assets use Ethereum/StarkEx contracts and their corresponding forced-operation framework. This is a separate architecture from current V2 and should be identified before using an old recovery guide. The platform’s audit directory likewise links Rigsec and SlowMist reports alongside a separate StarkEx audit; the presence of those links does not establish that every current V2 component and bridge is covered by the same examination.[5][26]

StarkWare’s V1-relevant forced-transaction procedure requires the appropriate Stark key and may require a forced trade to turn synthetic exposure into collateral before withdrawal. Forced requests cannot be cancelled. The framework’s default freeze grace period is seven days, but a deployed configuration must be checked. It is not sound to turn that generic default into either an edgeX V2 withdrawal promise or a guarantee of immediate liquidity during an outage.[29]

A protocol backstop, an audit and a self-custody claim address different issues. The reviewed ADL rules expressly allow profitable positions to absorb the consequences of another position’s bankruptcy. They do not establish a customer insurance policy or an insured per-person limit. Holding signing authority does not remove market, oracle, bridge, code or settlement risk.[17]

The terms bar US persons, Ontario residents/citizens/entities and restricted sanctions jurisdictions; physical location also matters. They prohibit using technical means to conceal an excluded location. Other users must still establish that leveraged trading is lawful for them. Wallet connection is not evidence of universal permission or a no-identification guarantee.[28]

V2 account settings expose per-account and per-contract trading controls, margin information and balances. The older guide allows up to twenty independent trading accounts under one wallet, but that legacy maximum is not presented here as the verified V2 account limit. The appropriate product and account identifier should be established before transferring collateral or attaching automation.[9]

For API incidents, preserve the request time, account and contract identifiers, client order ID, response and traceId. Public and private WebSocket services are separate from REST; reconnecting a display does not demonstrate that a pending order was cancelled. No reviewed official source established emergency voice dealing authority or a guaranteed support-resolution time.[19]

edgeX Infra Corporation provides the interface. A financial licence or statutory compensation scheme was not established. Terms select England and Wales law and individual HKIAC arbitration in Hong Kong after informal dispute handling.[28]

The terms distinguish the interface provider from the trading protocol. Its incorporation jurisdiction was not independently established, so no entity/register mapping is asserted here.[28]

Operator

edgeX Infra Corporation (interface provider)

Exchange model

Decentralised

Service scope

Current V2 order-book trading; legacy V1 conditions remain separately documented.

Client types

Retail clients; Professional clients

Pricing publication

Public pricing

Pricing scope

Public contract defaults; account adjustments and asset-flow quotes apply.

Funding scope

V2 USDC routes; V1 USDT instructions are legacy.

Custody and asset handling

Contract-based asset control with separate execution and settlement dependencies.

Client eligibility

US, Ontario and sanctions restrictions; local derivative eligibility required.

Support

Official Discord and written dispute notice at [email protected].

Authorisation and registration scope

Provider identified; no financial authorisation or compensation scheme established.

Exchange metadata checked 20 Oct 2026Source 28Source 27Source 24Source 2Source 30Source 1Source 3Source 14

Stopping an external bot requires disabling further submissions and revoking or replacing its credentials, followed by separate checks of live orders, positions and collateral. The API supports order and fill histories, including liquidation and deleveraging records. A cancel request that is still pending or a credential that has been removed does not erase a previously executed position.[21]

Account records expose position and asset transactions, funding events and leverage state. These are useful reconciliation inputs, but the reviewed documentation did not establish a universal tax-ready statement or a complete consumer CSV export window. Reconcile each sub-account and the external wallet/bridge movements; a single PnL number will not capture every off-platform transfer or reporting obligation.[22]

eStrategy’s initial eLP model makes depositors counterparties to traders through an AMM strategy. Returns can come from market-making results, liquidation fees and a share of trading fees, and can be negative. The published redemption process can take up to forty-eight hours; it describes no return accrual during that redemption period. Withdrawals can cause proportional position reductions or cancellation of orders if margin becomes insufficient. Requesting withdrawal from the strategy, rather than disconnecting the wallet, initiates the exit.[18]

XP is revocable, non-transferable and has no inherent cash value or future-asset entitlement.[28]

The V2 architecture is intended to support algorithmic and agent-driven integrations. That establishes a programmable trading surface, not an independently verified AI adviser or a mandate to manage a customer’s account. Users granting execution credentials remain responsible for the strategy’s order, leverage and collateral decisions.[1]