edgeX

edgeX V1 combined a central limit order book with StarkEx. Users signed with Ethereum and STARK keys; an operator ordered trades, StarkEx batched state transitions, SHARP produced proofs, and Ethereum contracts accepted proved roots. Funds sat in contracts rather than an exchange omnibus wallet, with forced withdrawals as an operator-failure route.

That structure reduced custody risk without removing the operator. Matching availability, order sequencing, oracle marks, liquidations and the interface still shaped a trader’s outcome. The terms even say edgeX Trading Inc. supplies software rather than execution, clearing or settlement, while retaining the ability to restrict the interface.

The 3 August 2026 notice reported that V2 was already trading and asked users to transfer V1 assets by 14 August at 08:00 UTC. It scheduled suspension of V1 fund operations and settlement of remaining positions at the oracle price then in effect, with transfers expected to resume on 16 August at 08:00 UTC. This is evidence of a live V2 product and an announced migration schedule, not confirmation that each later action occurred. Nor does it establish that every V1 escape path survived unchanged in V2.

The newer EDGE Stack paper proposes a sequencer feeding parallel edgeVM markets, an edgeEVM for general contracts, FlashLane soft confirmations and state roots anchored to settlement and data-availability layers. It also describes future settlement choices and sequencer decentralization as research. Architecture claims must therefore be divided into deployed product, current operator dependency and roadmap.

Before TGE, XP measured campaign activity; it was not a transferable token or legal claim. The season reserved up to 5% of supply and scheduled TGE no later than 31 March 2026. The Ethereum token then initialized one billion EDGE at 18 decimals. Its address, 0xb007…a241, excludes the unrelated Edge Network token and similarly named AI projects.

The allocation is unusually legible: 30% airdrop, 5% liquidity, 5% Foundation, 25% team and investors, 30% future reserve, and 5% ecosystem. Yet 65% sits in Foundation-directed or contributor-linked locked pools. Unlock contracts make time visible; they do not decide how reserve grants, liquidity or future campaigns are governed.

The verified implementation minted the full billion at initialization, exposes no later mint function and allows holders to burn. But the address is a UUPS proxy. The initializing address 0x25e3…239a received default-admin and upgrader roles, so authorized upgrades can replace token logic. Public pages reviewed here do not map the current role holder to named people, multisig threshold or Foundation process.

The dashboard reports revenue-funded buyback burns. That is a dated program outcome, not a dividend: the percentage changes as purchases and burns occur, and a holder cannot force edgeX Trading Inc. or the Foundation to buy, distribute profit or redeem EDGE. Burned supply and circulating supply are also different measures.

EDGE can be transferred, burned and used in participation or incentive systems described by the project. A perpetual position is a leveraged contract settled under exchange rules; it is not ownership of its underlying asset. Likewise, an EDGE balance is not ownership of the matching engine, sequencer, Foundation reserves or edgeX Trading Inc.

The terms apply California law, block the interface for US and Canadian persons, permit service restriction or discontinuation and deny fiduciary duties. Self-custody remains valuable because keys and contracts constrain asset movement, but it does not guarantee interface access, oracle continuity, favorable liquidation, an upgrade-free token or a legal share of revenue.